Tagged: enfold
-
AuthorPosts
-
January 31, 2018 at 10:02 pm #905840
After the latest updates the sidebar is shown below, not any more on the right side.
Would you please help me solving the Problem.
Thank you in advance,
Regards,
MichaelJanuary 31, 2018 at 10:50 pm #905860Hey zwachm,
If you are using full width elements on the page, like Color Sections or full width sliders, then the sidebar will display under them. Please use for instance a 1/1 element instead of a Color Section if you want the side bar to display to the right or left of your content.
Best regards,
Jordan ShannonFebruary 1, 2018 at 12:16 am #905911I am not tracking with the proposed solution. I am using 1/3 element layout and my “Left Sidebar” is showing up at the bottom of the page. Please help.
February 1, 2018 at 12:33 am #905915Hi,
If possible, please provide admin info so we can log in and look into this issue further.
Best regards,
Jordan ShannonFebruary 1, 2018 at 12:40 am #905921Please see Private Content. If there is anything else you need, please let me know.
February 1, 2018 at 8:43 am #906040Hi Jordan,
it is clear, that if I am using a color section (e.g. in the middle of the page) the
sidebar is moved below that section. That’s ok for me and I am used to it.Since I am aboslutely sure, that the sidebar worked in September last year I activated
a backup version.
Voila: it Looks good and the sidebar appears below the color-section on the right side. Not on the very bottom of the page.Whithin HTML code I can see the difference:
in the working (old Enfold) code the sidebar element “<aside class=”sidebar…”
is located IN the “<div class=”container”>….</div>
<!– close content main div –>
<!– section close by builder template –>”
section.In the current ENFOLD Theme the “<aside” Element is located WITHIN this “<div class=”container”>”
section.To me it seems that the Variable $cm in template-builder.php causes the <div> to be
closed before the sidebear is inserted.
If I move the output of $cm after the get_sidebar(); function, it works!!Original Code of template-builder.php
//only close divs if the user didnt add fullwidth slider elements at the end. also skip sidebar if the last element is if(!$last_el || !in_array($last_el['tag'], AviaBuilder::$full_el_no_section ) ) { $cm = avia_section_close_markup(); echo "</div>"; echo "</div>$cm <!-- section close by builder template -->"; //get the sidebar if (is_singular('post')) { $avia_config['currently_viewing'] = 'blog'; }else{ $avia_config['currently_viewing'] = 'page'; } get_sidebar();
Im am very sure, that I did not modify the code for that.
Would you please look into it again.
Thank you,
Best Regards,
MichaelFebruary 1, 2018 at 10:51 am #906157Hi,
one additional note:
the $cm should not be inserted before calling the sidebar-function if $cm contains:
</main><!-- close content main element -->
Otherwise other layouts are having side effects!
Regards,
Michael- This reply was modified 6 years, 10 months ago by zwachm.
February 1, 2018 at 10:34 pm #906494“should only not be” -> can you translate into proper grammar, so we can understand? Please.
February 2, 2018 at 5:14 am #906606Hi,
The color section will occupy the whole space, for the sidebar to appear left or right, just drag down content elements without using Color Section. Hope this helps.
Best regards,
NikkoFebruary 2, 2018 at 2:54 pm #906855Hi Nikko,
I am not sure whether we are talking about the same.
I want to Point to the issue, that below of a Color section the (right) sidebar is not shown on the right side.
Instead the sidebar is put to the very bottom of the page. So it is no sidebar any more!Would you try to re-create the Situation on your test Environment, since I have the code-Change in place already!
Best Regards,
MichaelFebruary 2, 2018 at 2:57 pm #906859@dp012011: sorry, I did correct the original post. Hopefully now it is better to understand?
February 5, 2018 at 4:35 am #907666Hi,
The sidebar looks ok when I checked the pages above. Is this fixed? If not, you can disable the pages’ sidebar and then use the Widget Area element instead.
Best regards,
IsmaelFebruary 5, 2018 at 7:29 am #907780Hi Ismael,
as I mentioned, I did a fix in source code.
The original behaviour is still there. Please see the private links to my test site.The work around with the sidebar as Widget is no Option, since it worked before as it is supposed to.
Regards,
MichaelFebruary 7, 2018 at 12:43 pm #909079Hi,
Thank you for the update. Please provide the login details to the test site. We would like to check the structure. Please note that the test site is using an old version of the theme, 4.1.2. Can you reproduce the issue on 4.2.2?
Best regards,
IsmaelFebruary 12, 2018 at 8:39 am #910948Hi Ismael,
ok. Now the productive page is copied to the test site without my mentioned source code correction.
Version is now 4.2.2You can find the Login in private section.
Thank you,
Best Regards
MichaelFebruary 13, 2018 at 4:10 am #911471Hi,
Thank you for the info.
There’s an extra div after the title container, wrapping the sidebar and the content. It’s not there if the plugins are deactivated. Please activate the plugins one at a time to find the cause of the issue.
Best regards,
IsmaelFebruary 13, 2018 at 7:51 am #911560Good Morning Ismael,
thank you very much for your anlaysis!!
With your hint I have found that the plugin Blocky! was causing this issue.
Although this plugin was only activated for a special post-type, it caused this additional <div> for all post types, so also pages were altered.I appreciate your help!
Best regards,
MichaelFebruary 13, 2018 at 11:27 am #911622Hi Michael,
Glad we could help and you got it working for you! :)
If you need further assistance please let us know.
Best regards,
Victoria -
AuthorPosts
- You must be logged in to reply to this topic.