-
AuthorPosts
-
November 2, 2019 at 11:01 am #1153216
Hello. On my page is an H1 element. It has a font-size of 40px specified, and that assignment has come from this entry in the file wp-content/uploads/dynamic_avia/enfold_child.css:
#top #wrap_all .all_colors h1{color:#000000;font-size:40px;font-family: 'halisr black', 'HelveticaNeue', 'Helvetica Neue', 'Helvetica-Neue', Helvetica, Arial, sans-serif;}
How exactly has that entry been added to enfold-child.css?
To be clear, I’m not asking how to change the font size of this element. I know how to do that. That is not what I am asking. I am asking how this assignment of
font-size: 40px
has been assigned to the element#top #wrap_all .all_colors h1
in the file enfold-child.css. Has it come from some page in Theme Options? If so, what page?Thanks in advance.
Edit: Actually, hold off on answering that question. Let me do some more troubleshooting on my end. I will get back to you here.
Edit 2: OK I did some more troubleshooting. Here is the real question :-) On all my pages there seems to be an element with ID ofwrap-all
(screenshot). Should I expect all my page content to be inside this element?- This topic was modified 5 years, 1 month ago by FeedXL2019.
November 2, 2019 at 5:31 pm #1153319Hey FeedXL2019,
Yes, all the content should be in the container with the id of wrap-all.
The code you’re asking about is generated based on the settings in the Quick css.
Best regards,
VictoriaNovember 3, 2019 at 9:48 am #1153475>> Yes, all the content should be in the container with the id of wrap-all.
OK thanks for that info. In that case I have a weird issue, and I’m not sure how to resolve it. On my live site, and staging site, on my home page, all my content is indeed inside
#wrap-all
. But when I cloned my live site to my local site, my local site was different in that respect. On my local site, only the top couple elements are inside#wrap-all
. The rest of the elements are outside#wrap-all
, at the same level in the DOM (screenshots). Any ideas how that would even occur, much less how to fix it? I guess some custom JavaScript could accomplish that, but I am using the unmodified parent theme, so there should be none of that.This issue is causing problems with styling. Certain CSS rules that should be applied are not, because of the incorrect DOM structure.
November 8, 2019 at 10:20 am #1154896Hi,
Thank you for the update.
The rest of the elements are outside #wrap-all, at the same level in the DOM (screenshots).
Did you add any html tags in the page? You have to make sure that all tags are closed properly, otherwise they will break the layout of the site. You can also set the builder to debug mode and enable the shortcode parser to automatically repair the shortcodes on update. Please check the documentation for more info.
// https://kriesi.at/documentation/enfold/intro-to-layout-builder/#shortcode-parser
Best regards,
IsmaelNovember 8, 2019 at 11:56 am #1154943>> Did you add any html tags in the page? You have to make sure that all tags are closed properly, otherwise they will break the layout of the site.
OK good point. I personally haven’t added any custom HTML to the page, but I also did not build the page. Is there an automated tool I can use to check a page for unclosed/incorrect HTML tags?
>> You can also set the builder to debug mode and enable the shortcode parser to automatically repair the shortcodes on update.
Let’s say I had added custom HTML to the page, and accidentally included an unclosed HTML tag. Would the shortcode parser be able to find/fix that?
November 11, 2019 at 1:44 am #1155440Hi,
Thank you for the update.
You can use the following tool to check for unclosed tags in the page. Enable the debug mode, copy the content or shortcodes from the debug field and paste it in the tool. It should be able to detect unclosed html tags.
// https://www.aliciaramirez.com/closing-tags-checker/
The shortcode parser can only repair shortcodes, so it won’t be able to detect and repair unclosed html tags. You will have to do it manually.
Best regards,
IsmaelNovember 11, 2019 at 8:34 am #1155507I have an update. I used that site (https://www.aliciaramirez.com/closing-tags-checker/) to check for unclosed tags. I ran it twice:
1. I first enabled debug mode. Then I opened my page for editing, and located the debug field. I copied the text in that field and pasted it into the tag checker. It reported no unclosed tags. But as you know, the debug field does not contain all the HTML on the page–there are many shortcodes. Here is the full text of the debug field.
2. In the second test, I opened the front-end of my page, and viewed the source code. I copied it and pasted it into the tag checker. It reported several unclosed tags:
Line 743: <li class="news-content post-format-standard"> Line 743: <a class='news-link' title='Is Forage All a Horse Needs?' href='https://feedxldev.local/is-forage-all-a-horse-needs/'> Line 743: <span class='news-thumb '> Line 743: <a class='news-link' title='Don’t Forget the Milk!' href='https://feedxldev.local/dont-forget-the-milk/'> Line 743: <a class='news-link' title='How to Make Sense of Pasture Analysis Results' href='https://feedxldev.local/how-to-make-sense-of-pasture-analysis-results/'> Line 959: <form action="https://feedxldev.local/" method="get" id="adminbarsearch"> Line 959: <a class='ab-item' aria-haspopup="true" href='https://feedxldev.local/wp-admin/profile.php'>
Again, there is no custom HTML added to the page.
In light of the second test, how do you think I should proceed? Do you think I run the shortcode parser?
November 13, 2019 at 12:26 pm #1156366Hi,
Thank you for the update.
Can we access the site with the broken layout? We would like to inspect the content of the page. Please provide the login details in the private field.
Do you think I run the shortcode parser?
Yes, you should run the parser and see if it fixes the issue.
Best regards,
IsmaelNovember 13, 2019 at 12:52 pm #1156378>> Can we access the site with the broken layout? We would like to inspect the content of the page. Please provide the login details in the private field.
Actually no, that’s one of the issues here. I have three sites: a live site, an online staging site, and a local dev site. This issue exists *only* on the local dev site–the only site you cannot access :-(
>> Yes, you should run the parser and see it fixes the issue.
OK. But can you give me clear instructions on what exactly I should do? The page you linked isn’t clear. It just says,
>> Below ALB debug window you have a section Enfold Shortcode parser with a select box
>> You have to update the page to check the contentIt also refers to the feature as “Enfold shortcode Preser .” I see a select box in the “Enfold Shortcode Parser” section. In it is an option for “Auto Repair Function enabled – Repairs errors in shortcode structure during update” (screenshot). Should I select this? If so, what should I do after? Please be clear about any and all steps I should take–I have never used this tool, nor do I know what to expect.
Thanks.
November 18, 2019 at 3:05 am #1157710Hi,
Sorry for the delay. Yes, you should select the “repair” option in the shortcode parser dropdown, then update the page. The parser will automatically detect the existing shortcodes and repair them if necessary.
Best regards,
IsmaelNovember 18, 2019 at 11:59 am #1157820OK I ran the shortcode parser repair. After updating the page, it indicated
>> 0 warning(s), 5 error(s), 0 fatal error(s) were detected parsing the shortcodes. Necessary changes were applied to fix all found problems
But when I checked my HTML, the issue was still present. What can I do now to troubleshoot?
When I used that tool to check for unclosed tags, and entered the full HTML source code of the page, it found several unclosed tags:
Line 743: <li class="news-content post-format-standard"> Line 743: <a class='news-link' title='Is Forage All a Horse Needs?' href='https://feedxldev.local/is-forage-all-a-horse-needs/'> Line 743: <span class='news-thumb '> Line 743: <a class='news-link' title='Don’t Forget the Milk!' href='https://feedxldev.local/dont-forget-the-milk/'> Line 743: <a class='news-link' title='How to Make Sense of Pasture Analysis Results' href='https://feedxldev.local/how-to-make-sense-of-pasture-analysis-results/'> Line 959: <form action="https://feedxldev.local/" method="get" id="adminbarsearch"> Line 959: <a class='ab-item' aria-haspopup="true" href='https://feedxldev.local/wp-admin/profile.php'>
Do you think I should try to fix each of these? If so, how–how can I properly edit the HTML source code of this page? Do I have to first switch to ‘Default Editor’ and edit the source code via the text editor? Or can I edit the HTML source code from within the Avia page builder?
November 21, 2019 at 9:38 am #1158758Hi,
Thank you for the update.
Looks like the tags are within the news widget. Did you add that widget in the page? We added the same widget on our installation, but the tool didn’t return the same results — all tags are closed properly. Please try to clone the local site on a live domain so that we can actually check the issue.
Or can I edit the HTML source code from within the Avia page builder?
The builder uses shortcodes, so you can’t edit the markup there directly, unless you added the html tags manually using a text or code block element.
Best regards,
IsmaelNovember 23, 2019 at 3:35 pm #1159433>> Looks like the tags are within the news widget. Did you add that widget in the page?
No I did not.
>> Please try to clone the local site on a live domain so that we can actually check the issue.
Unfortunately I cannot do this. The site does existing on my online server. But this issue is not present there–the issue is present only on my local site for some reason.
>> The builder uses shortcodes, so you can’t edit the markup there directly, unless you added the html tags manually using a text or code block element.
OK too bad. So are the shortcodes generating incorrectly structured HTML? If so, how and why?
November 25, 2019 at 4:05 am #1159752Hi,
OK too bad. So are the shortcodes generating incorrectly structured HTML? If so, how and why?
We can’t be sure unless we have access to the site and able to inspect the issue. Did you add any custom shortcodes in the page using a text or code block? If so, adding the following filter in the functions.php file might help.
Best regards,
IsmaelNovember 25, 2019 at 9:15 am #1159765>> Did you add any custom shortcodes in the page using a text or code block?
I don’t see any code blocks on the page. And I looked through all the text blocks and don’t see any shortcodes added.
>> If so, adding the following filter in the functions.php file might help.
Can you describe what exactly that code will do? I see in the header it indicates:
>> * Allow to force execution of shortcodes e.g. for plugins who call shortcode via an ajax call.
>> * Enfold uses this to execute the shortcode for modal popup preview in backendI’m not sure what that means. Does this mean that after I add this code to my site, a modal window will display when I load the ‘edit page’ screen for my home page?
November 26, 2019 at 3:05 am #1160160Hi,
The filter will allow execution of shortcodes that are not directly added using the advance layout builder — those that were added via custom shortcode or plugin for example. It will also work for shortcodes that are manually added in the advance layout builder using a code block or text block.
Best regards,
IsmaelNovember 26, 2019 at 1:37 pm #1160318OK. So after adding the custom code to functions.php, what exactly should I do? Can you list the steps I should execut, what output I should expect to see (and where), and what kind of analysis I should carry out?
November 28, 2019 at 8:00 am #1160877Hi,
Thank you for the update.
You don’t have to do anything. The filter will just allow the execution of shortcodes that are not added directly in the builder. It may or may not be related to the issue. Unfortunately, we can’t help you any further if we can’t access the site.
Best regards,
IsmaelNovember 28, 2019 at 10:46 am #1160899So are you saying I should add this custom PHP code, then open my home page–the front-end–and see if the issue has been resolved? If not, please spell out the specific steps I should take after adding the PHP code.
November 29, 2019 at 10:58 am #1161173Hi,
Yes, that’s all you need to do — update the page and check it again. If it’s not fixed, then the issue is probably not related to the shortcodes. Please update us again once a development site is accessible so that we can actually check the issue.
Thank you for understanding.
Best regards,
IsmaelNovember 29, 2019 at 11:41 am #1161189OK thanks for confirming. I added that code, then updated the page, but the issue was still there.
I then did some more checking. I told you earlier that my local site is identical to both my dev site, and my live site. But I looked closer, and found out that is not 100% identical. There is one element on the page–a Full Width Slider Revolution element. On the dev site and live site this is an Avia ‘Full Width Slider Rev’ element (screenshot). But on my local site (the site experiencing the issue in-question), this was not an Avia ‘Full Width Slider Rev’ element. It was instead an Avia Text Box element, and inside was a Slider Rev shortcode: [av_revolutionslider id=’2′ av_uid=’av-3crm4p’]. When I deleted that text box element and replaced it with the Avia ‘Full Width Slider Rev’ element, the issue went away. So for some reason, that shortcode was causing issues.
December 2, 2019 at 8:59 am #1161771December 5, 2019 at 10:10 am #1162854We can consider this resolved.
December 5, 2019 at 11:23 am #1162887 -
AuthorPosts
- The topic ‘Question about #wrap-all’ is closed to new replies.