Hi, last weekend we migrate to production the site, from hidden link to hidden link. com. Everything works fine but the Divi library. When we just click in Divi library option, instead of loading it throws a critical error: "There has been a critical error on this site. Please check your site administrator's email inbox for instructions."
First of all I contacted Elegant Themes support team and they asked me to deactivate all plugins and check if the issue is still happening. When I did that Divi library loads fine. Then I activate the plugins one by one and when I activate both Toolset Types and Toolset Blocks, Divi library stopped working, so that's the reason why I'm contacting you now.
In development Divi library works fine with both Toolset plugins active. Can you help me? Thanks in advance.
Link to a page where the issue can be seen: hidden link
In order for us to take a closer look at this issue, I'd like your help creating a package of your website and sending it to us.
Please use the plugin Duplicator(hidden link) to create a full copy of your website so we can take a look at it and see what's causing the issue with the large table.
If you come across problems while creating it, please feel free to ignore(exclude from the backup) both uploads and cache folders.
I'm enabling the proper field for your to share this copy, you'll see it on your next response.
Alternatively, you may use any file sharing service that you prefer and share the link in the ticket(your next response is being marked as private, only you and I have access to it).
What about providing us with the access? Then we could try to do the backup and install it in another server. I'm marking your next answer as private again.
Upon further inspection, we could check that the following error was being generated when reproducing the issue:
PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in \mundoexplora\wp-includes\class-wpdb.php on line 3124
By increasing the memory limit to 1024M (through the wp-config.php file), the problem is not occurring anymore. Could you please review it and confirm if it is fixed now?
