Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Luca Grandicelli

    (@lgrandicelli)

    This is not caused by the plugin itself, but you should look inside the content of that post, which is responsable for producing this unclosed tags. The strange markup infact, is right inside the post content.
    Please do a check and report.

    Thread Starter MightyMikeX

    (@mightymikex)

    Ok, I did some cross-checking and came to a few conclusions:

    1. The garbage markup doesn’t appear in the original posts’ code
    2. The markup also doesn’t appear in any post page’s code
    3. It’s not an issue of language – recreated the bug in English and Hebrew both
    4. The problem only manifests where the posts are displayed by SRP
    5. The problem only happens when there are <p> tags in the post
    6. Not sure why, but now the garbage markup is: <!--<--><!--<--><!--<--><!--<--> , which are comment tags containing just a < sign
    7. Even though the garbage markup is in fact commented, W3C still sees it as an error
    8. W3C also reveals an additional error:
    No p element in scope but a p end tag seen.
    — this error is indeed true in the source code, but isn’t present in the post’s code in TinyMCE – the additional </p> must be added somehow when the page is rendered. This again only happens inside the SRP widget.

    So what I take from all this is that a combination of <p> or </p> tags in a post lead SRP or WP itself to create that markup, and only within SRP’s widget. Any ideas?

    Plugin Author Luca Grandicelli

    (@lgrandicelli)

    What happens if you try to put the <p> tag in the “allowed html tags” option?

    Thread Starter MightyMikeX

    (@mightymikex)

    I forgot to mention – it’s already in the allowed HTML tags list

    Plugin Author Luca Grandicelli

    (@lgrandicelli)

    Ok another test. Have you tried to put wp on debug mode? Is there any particula error related to SRP you can find?

    Thread Starter MightyMikeX

    (@mightymikex)

    No, I don’t see any relevant errors.

    Plugin Author Luca Grandicelli

    (@lgrandicelli)

    I don’t know.. this issue is totally new to me and you’re the first person who is experiencing this. I need to do some test.

    Thread Starter MightyMikeX

    (@mightymikex)

    Well at least it’s a harmless bug. I’ll live with it for now ??

    Plugin Author Luca Grandicelli

    (@lgrandicelli)

    Ok i’ll let you know if i come up with something.

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘[Plugin: Special Recent Posts] Garbage chars in page source code’ is closed to new replies.