-
AuthorPosts
-
October 11, 2016 at 8:47 am #697675
on most of the enfold sites there are at the end of footer section some closing p tags which have no opening tag.
i think it is only if using socket and the widgets.f.e on http://kriesi.at/themes/enfold/
No p element in scope but a p end tag seen. From line 322, column 67; to line 322, column 70 </div></p></div>
mostly i can prevent this by disabeling the autop function of wordpress.
remove_filter( 'the_content', 'wpautop' ); remove_filter( 'the_excerpt', 'wpautop' );
what for is this link in the head section of the html? for example:
<link rel='https://api.w.org/' href='http://kriesi.at/wp-json/' />
this is afaik on every enfold generated page.
October 12, 2016 at 4:31 am #698145Hey Guenter!
Thank you for using Enfold.
1.) I’m sorry but I can’t find the paragraph tag in the markup. Could you please provide a screenshot? It should be breaking the layout of the page.
2.) The link is automatically added by WordPress. It’s for the WP Rest API plugin. https://wordpress.org/plugins/rest-api/
Regards,
IsmaelOctober 13, 2016 at 9:03 am #698622well that is not so important – but since it exists now an official w3c html5 validator i’m nosy about enfold and the results.
They only have two “faults” and a lot of advices concerning to role setting (header, footer, navigation do not need the role attribut etc.)
The link i mentioned above and some closing p tags without opening one.
for example on enfold theme demo page line 322
October 13, 2016 at 9:14 am #698630on every enfold page i disable the autop function of wordpress this closing p-tag is gone.
without that little fault (and it is not a fault of enfold i think – Enfold Pages are html5 valideOctober 17, 2016 at 4:34 am #699762Hi,
Thank you for the info. I can see it now but I’m not sure why it renders a closing paragraph tag. Can you reproduce this issue on your installation? And are there any other sections where you see this unwanted p tag?
Best regards,
IsmaelOctober 17, 2016 at 12:58 pm #699941if it is there it is allways in front of : </div></div></div><!– close content main div –>
</p> </div></div></div><!-- close content main div --> Line 178 http://kriesi.at/themes/enfold-one-page-portfolio/ </p> </div></div></div><!-- close content main div --> Line 194 http://kriesi.at/themes/enfold-startup/ </p> </div></div></div><!-- close content main div --> Line 182 http://kriesi.at/themes/enfold-hotel/ </p> </div></div></div><!-- close content main div --> Line 166 http://kriesi.at/themes/enfold-spa/
October 19, 2016 at 4:59 am #700979Hi,
Thank you for the info. That is peculiar, surprisingly, it doesn’t break the page. I will notify Kriesi.
Are you able to reproduce the issue on your own installation?
Best regards,
IsmaelOctober 19, 2016 at 5:16 pm #701436Yes – but as i described above – i can prevent this by removing autop function of WordPress:
remove_filter( 'the_content', 'wpautop' ); remove_filter( 'the_excerpt', 'wpautop' );
btw: there are sometimes some issues with f.e. : “no div tags within h tags”
or on your enfold-creative-studio demo the duplicate ID : team ( in front of team grid and under the last grid)
Edit: if you look to source code via Browser there is only a closing p tag.
and https://validator.w3.org/ too only closing tag
but on firebug :<footer class="entry-footer"></footer> </article> </div> <p></p> </div>
hm ???
- This reply was modified 8 years, 2 months ago by Guenni007.
July 29, 2017 at 4:47 pm #831524Dear Support,
please validate this mentioned topic with the mentioned p-tag.
</div></section></div><div style=’height:50px’ class=’hr hr-invisible avia-builder-el-2 el_after_av_one_full avia-builder-el-last ‘><span class=’hr-inner ‘ ><span class=’hr-inner-style’></span></span></div></p>
Some plugins like tooltip plugins and some another repair misspelling, wrong encapsulated or unclosed tags or don’t work correct, if something is wrong. I have massive problems with such two plugins and enfold. If i use another themes, this error is not there.
This may resulting in following stuff like corrupt footers.
Please fix it, what is mentioned in many threads here and what the w3c validation check is telling to us.“Error: No p element in scope but a p end tag seen.”
Thanks
- This reply was modified 7 years, 4 months ago by Hokuspokus.
July 31, 2017 at 5:49 pm #832301Hi seolotsen,
On the screenshot you have an empty paragraph not an unclosed paragraph tag. That can be disabled, but disabling wpautop https://codex.wordpress.org/Function_Reference/wpautop
Best regards,
VictoriaJuly 31, 2017 at 5:52 pm #832305hey victoria – nice but did you recognize the date of that post ?
can be closedJuly 31, 2017 at 6:00 pm #832310Hi,
the post is actual since 2016, I see the same as you, Guenni007
The paragraph is not created by me.
It comes from an element like hr-line or something else.
If you compare source code and dev tool, than you see what is happen and what the W3C validator say.July 31, 2017 at 6:02 pm #832312Now, it’s a div inside p-tag which is forbidden for my understanding, what the interpreter say
August 2, 2017 at 1:09 pm #833412but i guess in this case the tip of victoria is quiet the best. It comes from the autop function of wordpress.
you can try it via functions.php of your child-theme:remove_filter( 'the_content', 'wpautop' ); remove_filter( 'the_excerpt', 'wpautop' );
or if you only like to avoid autop in textarea element: make your own shortcode of textblock.php
find line: guess on newest version it is line 201
$params['innerHtml'] = "<div class='avia_textblock avia_textblock_style' data-update_with='content'>".stripslashes(wpautop(trim(html_entity_decode( $params['content']) )))."</div>";
replace it by:
$params['innerHtml'] = "<div class='avia_textblock avia_textblock_style' data-update_with='content'>".stripslashes(trim(html_entity_decode( $params['content']) ))."</div>";
- This reply was modified 7 years, 4 months ago by Guenni007.
August 2, 2017 at 2:46 pm #833491I assume that kriesi supplies clean code. I do not use child themes, nor will I change any codes manually at a few tens of clients.
August 7, 2017 at 3:00 pm #835398Hi,
Thanks for pointing out the examples. That was very helpful.
I could narrow down the problem but it needs some deeper investigation what really causes the problem and how to avoid it and/or repair it when it occurs (on already existing pages).
Best regards,
Günter -
AuthorPosts
- You must be logged in to reply to this topic.