Oh damn, can you tell me more about that error? Which version had you used before you’ve updated to the current version 2.0.3?
Which version of WordPress are you using?
Sorry, yes 2.0.3.
I don’t remember the version number before that. I’m guessing it was 4 or 5 months ago I first installed it. I’m using WP 3.9.2
When I tried it now I got this error:
“Fatal error: Allowed memory size of 262144000 bytes exhausted (tried to allocate 71 bytes) in …./wp-includes/taxonomy.php on line 2279”
Does this plugin load taxonomies or member/author lists?
Hi Austin,
I assume that my plugin doesn’t load taxonomies or member/author lists. But I’ve already seen this error in other places. It can be solved with an update of your .htaccess file or so. Google for it.
Regards,
Kevin
This is not a lack of memory issue. This is a problem with your plugin. I have received several other error messages when trying to activate it. The errors change as a result of the bottleneck your plugin causes and whatever is being loaded after it.
My guess is this is an error in the way you are caching oembed objects.
BTW It has been tested with several themes include WP default and of course all other plugins disabled.
I just tried again and got this error:
Fatal error: Allowed memory size of 262144000 bytes exhausted (tried to allocate 78 bytes) in …/wp-includes/cache.php on line 569
I also tried your updated class-meta.php you posted in another thread with no luck.
Still broken. I don’t think this was designed for scale. We have 5000+ posts.
Hey Austin,
thanks for coming back to this thread!
Just to make sure: You’ve already raised the memory limit a lot and the plugin still breaks when you activate it?
Okay, then replace class-register.php with this file:
https://ssl-account.com/cloud.kevinw.de/public.php?service=files&t=6db72dab8fc67c90a1c0c340a690b84e
This should prevent the plugin from clearing the cache on activation.
Can you activate it?
If this works for you, I get certainty and will search for another way to clear caches.
Best regards,
Kevin
Hey Austin,
I found a way to reduce memory usage a lot and published an update right now (v2.0.6). Please tell me if this update solves your issue.
If not, please try to rise your allowed memory size (again) and also try the previously mentioned file.
Best regards,
Kevin
