WordPress.org

Ready to get started?Download WordPress

Forums

podPress
[resolved] Error: Security check failed. (5 posts)

  1. ilikewp
    Member
    Posted 3 years ago #

    Hi,

    Since upgrading to version 8.8.10.8, I can't get the size and length of my podcasts. There comes up a message telling me "Error: Security check failed.".
    What's wrong? :-(

    The podcasts are hosted externally: Same Domain, different subdomain, different server. Was never a problem.

    Thanks in advance.

    Phil

    http://wordpress.org/extend/plugins/podpress/

  2. ntm
    Member
    Plugin Author

    Posted 3 years ago #

    Phil,

    that has nothing to do with externally hosted files. Open the post editor page in your browser (is it Chrome?) and press the reload button. Maybe clear the browser cache before that. This should solve the problem.
    Some browsers reload Javascript scripts only when you press reload or/and clear the cache.

    Regards,
    Tim

  3. ilikewp
    Member
    Posted 3 years ago #

    Hi,

    yepp, it's Chrome. Is there a known issue with Chrome?

    But you're right: I'm using a Firefox 4 Portable right now, sitting in a complete different IT-environment as well (home vs. work ;-) ), but I can get the data now.

    Everything is fine now - did you change the javascript, so Chrome got confused?

    Thanks for your help.
    Phil

  4. ntm
    Member
    Plugin Author

    Posted 3 years ago #

    did you change the javascript, so Chrome got confused?

    Yes and No.

    I have modified the Javascript AJAX request a little bit to increase the security of these requests (e.g. of the duration or file size). That means that these requests need to include a special parameter and if this parameter does not exist or has the wrong content then one gets these security alert messages.
    Only the Javascripts of 8.8.10.8 are sending these parameters. But some browser especially Chrome seems to load new Javascripts only if you click on the reload button of the browser (and maybe under some other circumstances which I don't know).
    Chrome has used simply the old, cached Javascripts and has not checked whether the content of the script file has changed. Other browser behave differently. But maybe there is a setting in Chrome which may help to avoid such effects.

    Regards,
    Tim

  5. ilikewp
    Member
    Posted 3 years ago #

    Well, as long as I know how to handle this error, I can live with a forced reload.

    Thanks for your help and the additional information. It is not usual, that a plugin is supported and maintained so fast and competent.

    Phil

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags