PHP Fatal error
-
Dear all,
after latest update to Wordpress Developer, instance is broken and I have
PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in /app/data/public/wp-includes/pomo/mo.php on line 328
Of course, I tried to disable all plugins, delete all themes, increase memory, but nothing happens...
I also tried to restore old backups, but nothing to do... Always same problem.
I suppose that is related to latest Cloudron Wordpres package update... To validate this hypothesis, how I can downgrade from org.wordpress.unmanaged.cloudronapp@3.0.4 to org.wordpress.unmanaged.cloudronapp@3.0.3?
Edit: I restored a backup on org.wordpress.unmanaged.cloudronapp@3.0.3, but nothing happens...
Edit: I restored even an old backup, 5 days ago, but problem is still the same.Can you help me?
-
-
Having the same issue with a previously stable WordPress developer install. Have tried all the same solutions, no luck.
-
Having the same issue with a previously stable WordPress developer install. Have tried all the same solutions, no luck.
@jordanurbs If you still have the app instance, can you contact us at support@cloudron.io , so we can debug this further?
-
This turned out to be a theme issue. The upstream theme author issued a fix and things are working now.
-
This turned out to be a theme issue. The upstream theme author issued a fix and things are working now.
-
I had a similar issue with my WP sites where the page would look all weird (CSS got all f'ed up). I thought it was theme related but narrowed it down to the CDN integration (Bunny). The page loaded fine once I disabled the CDN option in the caching plugins (I use different cache plugins on each of my sites). I did purge the cache in Bunny's dashboard, but that did not fix it. I didn't change anything with the sites before this happened, so it's got to be a broken update somewhere. The two problematic themes are Woodmart and Astra. My third site is using a different theme from Themeforest, but I can't remember its name right now (it's a weird one).
-
@girish said in PHP Fatal error:
This turned out to be a theme issue. The upstream theme author issued a fix and things are working now.
Merely out of curiosity... what was the impacted theme?
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login