wrong installation

I Googled this error, and found these pages :

https://www.ads-software.com/support/topic/plugin-wp-super-cache-error-zend-on-gandi-hosting?replies=4
https://www.ads-software.com/support/topic/supercache-internal-zend-error-wtf?replies=5
https://www.ads-software.com/support/topic/fatal-error-internal-zend-error-2?replies=5
https://club.orbisius.com/tutorial/wp-super-cache-fatal-error/

https://bugs.php.net/bug.php?id=59298

Can you ask your hosts how you can disable APC (it’s a caching/accelerator service)?

One of your customers should not have to disable the caching system they use to accommodate your plugin. You should ensure your plugin works with server-side caching enabled.

It has absolutely nothing to do with Jomres, if you’ll read those links.

Err. It clearly is because the missing class references a file in your plugin. If they hadn’t have installed your plugin, they wouldn’t have received the error. Sure, it may not be an error in your plugin but it’s a compatibility issue you should resolve – instead, you’ve advised them to disable server-side caching which should never be a solution.

Please read the php.net bug report. In our code we do

if ( ! class_exists( ‘wp_jomres’ ) )
{
class wp_jomres

Which is perfectly valid in regard to checking to see if a class already exists.

I searched again to ensure that I didn’t miss anything last time around, and it’s certainly seems to be an issue with how WP includes files (in fact, it seems to be a uniquely WP issue) and almost unanimously the fix is to disable APC caching.

The other possible solution is to remove the “if ( ! class_exists( ‘wp_jomres’ ) ) ” that wraps the class, however this will impact many more users depending on their CSS version and what there error reporting is set to (potentially) so on balance it seems sensible to keep it in place. Anybody who then receives this error in future can TRY to remove the inclusion wrapping, or disable APC.

*and what their*

Schoolboy typo.

Ah, yes my apologies, it is indeed apparently a bug in the PHP version (I didn’t previously check or look into it). Perhaps a better solution would be to upgrade PHP to 5.4+ rather than to disable APC caching ??

Ideally, people will be using PHP 5.5 as 5.4 is almost EOL now but we both know that’s not going to happen for the majority of users ??

Of course ??