kouku
Forum Replies Created
-
Thank you for confirming the issue.
In my environment, the editor shows a fatal memory error when the PHP memory limit is 1 GB, but the post editor opens successfully when the limit is set to 2 GB.
For clarification, the live post currently uses the Cocoon theme’s built-in table of contents, and Easy Table of Contents is deactivated.
However, even with Easy Table of Contents deactivated, the Gutenberg editor still runs out of memory with a 1 GB PHP memory limit. The editor opens successfully with a 2 GB memory limit.
Therefore, issue #910 may be related, but it may not be the only cause of the memory exhaustion in this post.
I will wait for the fix and test the large post again when the updated version is released. I will report the results afterward.
Thank you for your support.
- This reply was modified 1 week ago by kouku.
Thank you for the update.
I updated Converter for Media to version 6.6.3 and confirmed that the fatal error has been resolved on my server with cURL 7.29.0.
The plugin settings page and media optimization page now work correctly.
Thank you very much for fixing this issue.
Hi Mateusz,
Thank you for your detailed explanation and for addressing this issue in version 6.6.3.
I have already contacted my hosting provider regarding the outdated cURL version and am currently waiting for their response.
I will test the plugin again after version 6.6.3 becomes available.
Thank you for your support.
Hi,
Thank you for your reply.
Here is a screenshot of the error log provided by my hosting company:
https://snipboard.io/kpnfoU.jpg
The error occurred when opening the affected post in the WordPress block editor.
With the PHP memory limit set to 2048M, the same post editor opened normally.
Please let me know if you need any other information.
Thank you.