Passer la navigation

[Attente de la confirmation de l'utilisateur] Critical Errors when editing custom posts

This support ticket is created Il y a 5 days, 19 hours. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Fuseau horaire du supporter : Asia/Kolkata (GMT+05:30)

Ce sujet contient 4 réponses, a 1 voix.

Dernière mise à jour par Minesh Il y a 4 days, 2 hours.

Assisté par: Minesh.

Auteur
Publications
#2861626

I am trying to: Edit custom posts of the post type "Company Profile".

Link to a page where the issue can be seen:

I expected to see: no errors

Instead, I got: when clicking to edit the post I get "There has been a critical error on this website. Please check your site admin email inbox for instructions. If you continue to have problems, please try the support forums."

This was a very regular intermittent problem which went away if I reloaded the page until I got WPEngine's helpdesk to have a look at it today and after that I was only able to edit posts if I deactivate toolset Blocks. but now after doing nothing more than mirroring the site to a staging site for the purposes of getting assistance from Toolset, I am unable to access the listing of posts in WP Admin OR edit the posts. From a user's perspective they can view everything without issues.

WP Engine dug out this from the error logs on my production site available here: lien caché

Can you please help me fix this.

Peter

PLEASE NOTE I CANNOT PROVIDE DUPLICATOR PACKAGE AS WPENGINE does not allow this

#2861683

Minesh
Supporter

Les langues: Anglais (English )

Fuseau horaire: Asia/Kolkata (GMT+05:30)

Hello. Thank you for contacting the Toolset support.

I login using the access details you shared but can you please tell me what post type or what post I should try to edit or exact steps that I should follow in order to see the issue. Maybe you should provie exact link of the post and steps that I should follow.

If duplicator does not work with WP Engline then you can use ALL in one WP Migration:
- https://wordpress.org/plugins/all-in-one-wp-migration/

Alternatively, you can check with your hosting authority what is the best practice in order to create staging site on their platform.

I need a working copy of your site where I can see the issue and once I have that I will troubleshoot further.

*** Please make a FULL BACKUP of your database and website.***
I would also eventually need to request temporary access (WP-Admin and FTP) to your site. Preferably to a test site where the problem has been replicated if possible in order to be of better help and check if some configurations might need to be changed.

I have set the next reply to private which means only you and I have access to it.

#2861718

Minesh
Supporter

Les langues: Anglais (English )

Fuseau horaire: Asia/Kolkata (GMT+05:30)

When I checked the debug log I see the following fatal error with your debug log file:

[29-Apr-2026 07:32:54 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20971520 bytes) in /nas/content/live/techboard2017/wp-includes/class-wp-object-cache.php on line 318

It does not seem to be Toolset issue but the server issue and memory resource is exhausted.

I edit the wp-config.php file and adjusted the WP_MEMORY_LIMIT and WP_MAX_MEMORY_LIMIT vlaue to 1024M.

define('WP_MEMORY_LIMIT', '1024M');
define( 'WP_MAX_MEMORY_LIMIT', '1024M' );

I hope this will help you to fix the issue.

#2861805

Thanks for identifying this memory issue... I will implement the same change on my production site.

I attach below the error messages that WPEngine provided to me. The one from 19 May (to me at least) doesn't appear to be linked to a memory size whereas the one from 29 April does has the memory issue.

Could you advise if there is any other problem that in your view might cause any issues?

FROM 19 MAY
PHP Fatal error: Uncaught TypeError: array_intersect(): Argument #1 ($array) must be of type array, string given in /nas/content/live/techboard2017/wp-content/plugins/toolset-blocks/application/controllers/cache/views/invalidator.php:274#012Stack trace:#012#0 /nas/content/live/techboard2017/wp-content/plugins/toolset-blocks/application/controllers/cache/views/invalidator.php(274): array_intersect('', Array)#012#1 /nas/content/live/techboard2017/wp-content/plugins/toolset-blocks/application/controllers/cache/views/invalidator.php(217): OTGS\Toolset\Views\Controller\Cache\Views\Invalidator->invalidate_cache_per_domain('posts', Array)#012#2 /nas/content/live/techboard2017/wp-includes/class-wp-hook.php(341): OTGS\Toolset\Views\Controller\Cache\Views\Invalidator->should_invalidate_cache('')#012#3 /nas/content/live/techboard2017/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters(NULL, Array)#012#4 /nas/content/live/techboard2017/wp-includes/plugin.php(522): WP_Hook->do_action(Array)#012#5 /nas/content/live/techboard2017/wp-includes/load.php(1308): do_action('shutdown')#012#6 [internal function]: shutdown_action_hook()#012#7 {main}#012 thrown in /nas/content/live/techboard2017/wp-content/plugins/toolset-blocks/application/controllers/cache/views/invalidator.php on line 274

FROM 29 April
php_fatal
+---------------------------------------------------------------------------------------------------------------------------------+
| Count | Message |
|-------+-------------------------------------------------------------------------------------------------------------------------|
| 46 | Uncaught TypeError: array_intersect(): Argument #1 ($array) must be of type array, string given in |
| | /nas/content/live/techboard2017/wp-content/plugins/toolset-blocks/application/controllers/cache/views/invalidator.php:… |
| | trace:#012#0 |
| | /nas/content/live/techboard2017/wp-content/plugins/toolset-blocks/application/controllers/cache/views/invalidator.php(… |
| | array_intersect('', Array)#012#1 |
| | /nas/content/live/techboard2017/wp-content/plugins/toolset-blocks/application/controllers/cache/views/invalidator.php(… |
| | OTGS\Toolset\Views\Controller\Cache\Views\Invalidator->invalidate_cache_per_domain('posts', Array)#012#2 |
| | /nas/content/live/techboard2017/wp-includes/class-wp-hook.php(341): |
| | OTGS\Toolset\Views\Controller\Cache\Views\Invalidator->should_invalidate_cache('')#012#3 |
| | /nas/content/live/techboard2017/wp-includes/class-wp-hook.php(365): WP_Hook->apply_filters(NULL, Array)#012#4 |
| | /nas/content/live/techboard2017/wp-includes/plugin.php(522): WP_Hook->do_action(Array)#012#5 |
| | /nas/content/live/techboard2017/wp-includes/load.php(1308): do_action('shutdown')#012#6 : shutdown_action_hook()#012#7 |
| | {main}#012 thrown in |
| | /nas/content/live/techboard2017/wp-content/plugins/toolset-blocks/application/controllers/cache/views/invalidator.php |
| | on line 274 |
| 6 | Allowed memory size of 536870912 bytes exhausted (tried to allocate 20971520 bytes) in |
| | /nas/content/live/techboard2017/wp-includes/class-wp-object-cache.php on line 318

#2861831

Minesh
Supporter

Les langues: Anglais (English )

Fuseau horaire: Asia/Kolkata (GMT+05:30)

I see you are using PHP 8.4.x and Toolset plugins is compatible upto PHP 8.2.x.

What if you doengrade the PHP version to PHP 8.2.x and when announce the comatibility with PHP 8.4.x you can update the plugins and PHP version at that time.