Before upgrading our site to WordPress 6.3 everything was good. We always had our WP_MEMORY_LIMIT set to 512MB
After upgrading to WordPress 6.3, with nothing else changed on our site, and just simply clicking on the "Pages" in the backend: .../wp-admin/edit.php?post_type=page
causes this error:
"PHP message: PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 327680 bytes) in /www/.../public/wp-content/plugins/types/vendor/toolset/types/embedded/classes/loader.php on line 91" while reading response header from upstream, client: 96.41.190.214, server: ....org, request: "GET /wp-admin/edit.php?post_type=page HTTP/2.0"
None of the other lists (custom posts, posts, etc.) causes this memory issue with Toolset Type, only when trying to list our pages.
Any ideas on how to fix this would be great. When we deactivate Toolset Types, everything works.
I would like to request temporary access (wp-admin and FTP) to your site to take better look at the issue. You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.
Our Debugging Procedures
I will be checking various settings in the backend to see if the issue can be resolved. Although I won't be making changes that affect the live site, it is still good practice to backup the site before providing us access. In the event that we do need to debug the site further, I will duplicate the site and work in a separate, local development environment to avoid affecting the live site.
- Please make a backup of site files and database before providing us access.
- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this: hidden link
Please, let me know if you need any additional details. Have a nice day.
Thanks, I will push a copy to our staging server on Monday and send you the info. I don't see any box or area to enter the login credentials here though.
Hi, I see the private fields now. But, interestingly, when creating a staging copy, even though everything is identical, the error is not there. It is only there on the live server. I'll try a few more tests and if I can't figure out the cause of this difference, I'll give you access to our live server.
It sounds good. If you need us to debug this in the live site, please give us a heads up and I'll enable the private fields again for you to share the access details.
Please let us know if you still need assistance with this.
Hi Mateus, can you please re-enable the private fields and I'll give you access to the live server. I can't find any reason why the staging server works. All the plugins, WordPress version, and the db is exactly the same.
Thank you for granting access to your website for diagnostics. I've conducted an investigation and here's what I've found:
Memory Allocation: Post the upgrade to WordPress 6.3, it seems there is an increased demand in memory for some specific operations. In my tests when the memory limit was increased from 512MB to 1024MB, the issue you reported was resolved.
Page Listing: I also found that by reducing the number of pages displayed per pagination from the default 20 to 15, the issue can be mitigated without adjusting the memory.
For the time being I kept the memory limit set as 1024MB inside the wp-config.php file, if this amount is too high for your setup, it is possible to decrease the number of displayed items per page from 20 to 15 in the screen options at the pages listing and return the memory limit to the previous value 512MB.
Additional Insights: WordPress memory usage can be influenced by a myriad of factors. It's essential to understand that server capacity, the active theme, other plugins, and even specific settings can contribute to increased memory consumption. While we identified the Toolset Types plugin in conjunction with the new WordPress update as a potential combination causing the strain, it doesn't implicitly indicate a fault within the Toolset plugin. Often, interactions between various components of a site can lead to unexpected behaviors.
I recommend regularly monitoring the site's performance, especially after updates or adding new plugins. This proactive approach ensures that any potential hitches can be promptly addressed.
Please don't hesitate to get in touch if you have further concerns or require any more insights. I'm here to help!
Thanks for trying, but that is not a viable solution. It's weird to need 1GB of memory just to list pages. When it was set to 512MB, I only had 10 items showing on my page list and it still ran out of memory. I guess I'll continue to look into the issue and resolve it myself.
