ERROR v1.4.2 of JW player plugin: Editor users get 500 error on edit post page

@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.

Hi LongTail,

We were previously using version 1.4.1 without a problem.

Any ideas?

Cheers,
Keith

@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.

@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:

https://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

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

@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.

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.

@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.

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.