WordPress.org

Ready to get started?Download WordPress

Forums

[Plugin: Section Widget] HTML being escaped (4 posts)

  1. airfoil
    Member
    Posted 4 years ago #

    Some of our users (not all) who are accessing the section widget via the admin, are having escape slashes added to any HTML they place into the editing window upon save. Firefox is showing the following error:

    The stylesheet http://mysite.com/wp-admin/widgets.php was not loaded because its MIME type, text/html, is not text/css.

    I've seen references to this issue in other forums, though not specific to the section widget. No one has reported similar issues with other widgets, and some users with Firefox in different location are not having the problem.

    Any ideas?

  2. godfreykfc
    Member
    Posted 4 years ago #

    Hi airfoil:

    The FF error is likey caused by something else and it shouldn't have anything to do with the other problem you are experiencing.

    For the escaping problem, does it occur on al elements or just some of them? For non-admin users, all "dangerous" HTML nodes and attributes will be stripped or escaped (<script />, , etc.)

    Godfrey

  3. airfoil
    Member
    Posted 4 years ago #

    Thanks, Godfrey.

    This situation is happening with site admin users, and has not been reported with other elements. That said, the users in question are working from a location in another state, and I'm only going by reports and what I've seen when I log in and look at the widget after they attempt to add HTML into the section widget.

    I'm not actually suspecting the widget/plugin itself, since I can't replicate the problem from my end - just wondering if anyone had experienced anything similar and had any ideas about where to start looking.

    Thank again - I appreciate your response.

  4. Michelle
    Member
    Posted 4 years ago #

    I'm seeing this too. In my case, I'm having any single-quote or double-quote escaped, by an admin user running Firefox on a Mac. I'm running FF on a PC and it works fine; any idea why it would work on one and not the other?

    This is the code pre- and post-escaping. I am using single quotes here but it has exactly the same behavior with double-quotes around the parameters, which I believe is the correct way to do it:

    PRE:
    [featuredRacker
    name='Joel Walker'
    title='Linux Specialist / Cyclist'
    linktext='View their Racker experience'
    link='/joel-walker/'
    image='/files/2010/02/img-racker1.jpg'
    ]
    
    POST:
    [featuredRacker
    name=\'Joel Walker\'
    title=\'Linux Specialist / Cyclist\'
    linktext=\'View their Racker experience\'
    link=\'/joel-walker/\'
    image=\'/files/2010/02/img-racker1.jpg\'
    ]

Topic Closed

This topic has been closed to new replies.

About this Topic