WordPress.org

Ready to get started?Download WordPress

Forums

Advanced iFrame
[resolved] [Plugin: Advanced iframe] "An invalid security key was specified" (7 posts)

  1. mlapl1
    Member
    Posted 2 years ago #

    Hello,

    I have a page in WordPress using ckeditor as the editor.

    I have inserted the following code:

    [advanced_iframe securitykey="da39a3ee5e6b4b0d3255bfef95601890afd80709" src="http://xyz.com/Alphabetical_Listing_list.php" width="920px" height="920" scrolling="auto"]

    Everything was working properly for weeks.

    I added a few words before the iframe and updated. I now get the following message:

    An invalid security key was specified. Please use at least the following shortcode:
    [advanced_iframe securitykey="<your security key - see settings>"]

    The security key is correct - I have checked it many times.

    I reverted to a previous working version of the page, and the error now appears on that page too.

    I have flushed the cache of the entire site.

    I cannot explain it - I have also tried inserting the advanced_iframe shortcode in the html page rather than the normal wysiwyg part of ckeditor.

    Any help would be greatly appreciated. This is such a smart plugin!!

    Andrew

    http://wordpress.org/extend/plugins/advanced-iframe/

  2. mlapl1
    Member
    Posted 2 years ago #

    SOLVED - the answer may help others.

    ckeditor (probably) added a non-breaking space (the characters:  )after the security key.

    Of course this space was not visible in the editor, but was present in the HTML. It escaped my notice when I looked at the code in HTML mode - but it broke the plugin code. The answer was simple: remove   and everything was working once again.

    All the best
    Andrew

  3. mlapl1
    Member
    Posted 2 years ago #

    non-breaking space= &nbsp;

    It disappeared from my second post

    Andrew

  4. mdempfle
    Member
    Plugin Author

    Posted 2 years ago #

    Thanks for the hint. So it added a non-breaking space after the " or before? Because the one before I can detect - the other one not.

    - Michael

  5. mlapl1
    Member
    Posted 2 years ago #

    Unfortunately, it was after the " - to the naked eye it just looked like an extra space but in fact it was not. People will just have to watch out for this and check the shortcode in html mode - making sure no extra stuff is in there.

    cheers
    andrew

  6. mdempfle
    Member
    Plugin Author

    Posted 2 years ago #

    This is something wordpress itself would have to solve/detect. Because the framework does the parsing of the parameters. The only thing I can do is to improve the error message...

  7. mlapl1
    Member
    Posted 2 years ago #

    SOunds about right...

    cheers and thanks
    andrew

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic