WordPress.org

Ready to get started?Download WordPress

Forums

JW Player for Flash & HTML5 Video
ERROR v1.4.2 of JW player plugin: Editor users get 500 error on edit post page (10 posts)

  1. ppskb
    Member
    Posted 3 years ago #

    Hi,

    We recently upgraded our JW player plugin to the latest version (1.4.2) and some our users (those with editor privileges) are no longer able to access any posts in the wordpress cms, and get 500 server error.

    The only way around this, is to up their privileges to admin, but this isn't practical.

    Disabling this plugin stops the issue, so seems to be an issue with the latest version as we didn't experience this problem prior to upgrade.

    Any advise?

    Cheers
    Keith

  2. JW Player
    Member
    Plugin Author

    Posted 3 years ago #

    @ppskb

    Which version were you using prior to 1.4.2? From there I can review the exact changes that were made and hopefully figure out the issue.

    Thanks.

  3. ppskb
    Member
    Posted 3 years ago #

    Hi LongTail,

    We were previously using version 1.4.1 without a problem.

    Any ideas?

    Cheers,
    Keith

  4. JW Player
    Member
    Plugin Author

    Posted 3 years ago #

    @ppskb,

    The differences between 1.4.1 and 1.4.2 are pretty minimal so it's surprising that you would be seeing an issue.

    The only thing that could potentially affect it are slight tweaks to SSL detection and how the swfobject.js file is queued up. I'm not sure why either of those would cause a 500 error though. Do you have access to your server logs to see what the exact PHP error is?

    Thanks.

  5. ppskb
    Member
    Posted 3 years ago #

    @LongTail Video

    I checked the logs and noticed a memory error:

    "PHP Fatal error: Allowed memory size of 33554432 bytes exhausted"

    I followed this guide to up the PHP memory limit on .htaccess:

    http://crenk.com/how-to-increase-the-php-memory-limit-htaccess-file/

    Its hard to determine if this is an issue with your plugin... it did seem to resolve the problem once we disabled your plugin....

    Worth looking into potential memory issues with your plugin for future versions?

    Thanks

  6. esmi
    Forum Moderator
    Posted 3 years ago #

    It's normally the cumulative effect of all of your plugins (and perhaps your theme) rather than an issue with 1 specific plugin.

  7. ppskb
    Member
    Posted 3 years ago #

    @esmi

    You could be right, but surprising as we haven't got anything too memory intensive installed. I Still think its worth looking into the JW Player Plugin memory footprint to check for potential issues.

  8. esmi
    Forum Moderator
    Posted 3 years ago #

    With the greatest of respect, I know I'm right. I'd guess that you were close to your memory limit when you installed this plugin ("close" doesn't generate any errors or warning). Installing this plugin took you over the limit. You could probably have deactivated any of your active plugins and found that the error disappeared.

  9. ppskb
    Member
    Posted 3 years ago #

    @esmi I am not interested in getting into a discussion on whether your right or wrong. I am just pointing out that the memory footprint should be checked out, more as a precaution for future development of the plugin.

  10. JW Player
    Member
    Plugin Author

    Posted 3 years ago #

    We'll take a look at the memory footprint. There may be an issue with the playlist manager loading too much in the background. However, this typically results in the playlist manager being blank instead of causing a 500 error.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic