Okay and just to be clear, does this error continue appearing in the logs if you deactivate all Toolset plugins and save other posts or pages in wp-admin? Please clear or delete the current log file after deactivating Toolset plugins. Then try creating a new Page in the backend. If the log file is generated, please send me its contents.
I did a quick search online and found this:
https://oxygenbuilder.com/forums/topic/internal-server-error-500-with-the-grid-plugin/
It seems to show the same error with only Oxygen and The Grid active, though I wouldn't place all my confidence in one or two reports.
I deactivated all Toolset plugs and created a new post and saved without issue. Log below:
[06-Feb-2019 20:45:15 UTC] PHP Notice: Undefined index: WP_Widget_Recent_Comments in /nas/content/staging/concordportal/wp-content/themes/pro/framework/functions/setup.php on line 213
[06-Feb-2019 20:45:15 UTC] PHP Notice: Undefined index: tco_google_analytics_code in /nas/content/staging/concordportal/wp-content/plugins/tco-google-analytics/functions/options.php on line 50
[06-Feb-2019 20:45:26 UTC] PHP Notice: Undefined index: WP_Widget_Recent_Comments in /nas/content/staging/concordportal/wp-content/themes/pro/framework/functions/setup.php on line 213
[06-Feb-2019 20:45:26 UTC] PHP Notice: Undefined index: tco_google_analytics_code in /nas/content/staging/concordportal/wp-content/plugins/tco-google-analytics/functions/options.php on line 50
[06-Feb-2019 20:45:33 UTC] PHP Notice: Undefined index: WP_Widget_Recent_Comments in /nas/content/staging/concordportal/wp-content/themes/pro/framework/functions/setup.php on line 213
[06-Feb-2019 20:45:33 UTC] PHP Notice: Undefined index: tco_google_analytics_code in /nas/content/staging/concordportal/wp-content/plugins/tco-google-analytics/functions/options.php on line 50
[06-Feb-2019 20:45:34 UTC] PHP Notice: Undefined index: WP_Widget_Recent_Comments in /nas/content/staging/concordportal/wp-content/themes/pro/framework/functions/setup.php on line 213
[06-Feb-2019 20:45:34 UTC] PHP Notice: Undefined index: tco_google_analytics_code in /nas/content/staging/concordportal/wp-content/plugins/tco-google-analytics/functions/options.php on line 50
[06-Feb-2019 20:45:37 UTC] PHP Notice: Undefined index: WP_Widget_Recent_Comments in /nas/content/staging/concordportal/wp-content/themes/pro/framework/functions/setup.php on line 213
[06-Feb-2019 20:45:38 UTC] PHP Notice: Undefined index: tco_google_analytics_code in /nas/content/staging/concordportal/wp-content/plugins/tco-google-analytics/functions/options.php on line 50
[06-Feb-2019 20:45:39 UTC] PHP Notice: Undefined index: WP_Widget_Recent_Comments in /nas/content/staging/concordportal/wp-content/themes/pro/framework/functions/setup.php on line 213
[06-Feb-2019 20:45:39 UTC] PHP Notice: Undefined index: tco_google_analytics_code in /nas/content/staging/concordportal/wp-content/plugins/tco-google-analytics/functions/options.php on line 50
[06-Feb-2019 20:45:47 UTC] PHP Notice: Undefined index: WP_Widget_Recent_Comments in /nas/content/staging/concordportal/wp-content/themes/pro/framework/functions/setup.php on line 213
[06-Feb-2019 20:45:47 UTC] PHP Notice: Undefined index: tco_google_analytics_code in /nas/content/staging/concordportal/wp-content/plugins/tco-google-analytics/functions/options.php on line 50
[06-Feb-2019 20:45:48 UTC] PHP Notice: Undefined index: WP_Widget_Recent_Comments in /nas/content/staging/concordportal/wp-content/themes/pro/framework/functions/setup.php on line 213
[06-Feb-2019 20:45:48 UTC] PHP Notice: Undefined index: tco_google_analytics_code in /nas/content/staging/concordportal/wp-content/plugins/tco-google-analytics/functions/options.php on line 50
[06-Feb-2019 20:46:03 UTC] PHP Notice: Undefined index: WP_Widget_Recent_Comments in /nas/content/staging/concordportal/wp-content/themes/pro/framework/functions/setup.php on line 213
[06-Feb-2019 20:46:03 UTC] PHP Notice: Undefined index: tco_google_analytics_code in /nas/content/staging/concordportal/wp-content/plugins/tco-google-analytics/functions/options.php on line 50
Okay thanks for your patience. I was just able to replicate the error you described on my local environment while logs were running. Here's what I get:
[07-Feb-2019 14:40:49 UTC] purge_varnish_cache() failed for: (localhost) #^(concord\.test)$# #(/concord-albums/my-finest-work-yet(.*))#
[07-Feb-2019 14:40:49 UTC] purge_varnish_cache() failed for: (localhost) #^(concord\.test)$# #(/concord-albums/my-finest-work-yet(.*))#
[07-Feb-2019 14:40:49 UTC] PHP Fatal error: Uncaught ArgumentCountError: Too few arguments to function The_Grid_Admin::delete_transient_on_save(), 2 passed in /path/to/site/wp-includes/class-wp-hook.php on line 286 and exactly 3 expected in /path/to/site/wp-content/plugins/the-grid/backend/admin-init.php:184
Stack trace:
#0 /path/to/site/wp-includes/class-wp-hook.php(286): The_Grid_Admin->delete_transient_on_save(36183, Object(WP_Post))
#1 /path/to/site/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(true, Array)
#2 /path/to/site/wp-includes/plugin.php(453): WP_Hook->do_action(Array)
#3 /path/to/site/wp-content/plugins/layouts/classes-auto/wpddl.layouts-editor.class.php(396): do_action('save_post', 36183, in /path/to/site/wp-content/plugins/the-grid/backend/admin-init.php on line 184
So it does seem to have to do with that Fatal Error. I'm asking my 2nd tier team to investigate and determine if this is a problem that should be addressed in Layouts, or in The Grid, or in the WP Engine caching mechanism. I'll let you know what I find out.
Just a quick update, my 2nd tier's initial investigation indicates this is an issue that must be addressed in Layouts. We're escalating the problem to our developers for additional investigation, and I'll keep you update here as I receive more information.
Hi, I can see activity on the internal ticket within the last 6 hours. A fix has been proposed and is being submitted for QA, then the developers will decide to include this in the next release of Layouts or push it to a later release depending on other priorities. I'll let you know once I have more concrete information about the timing.
Nothing more concrete yet, I'm afraid. If this is holding up development of your site, perhaps we can come up with a workaround that will allow you to move ahead? We could try:
- Create a staging environment that does not use the WPEngine caching system
- Export your site's contents into the staging environment
- Make changes to the problematic Layouts in staging
- Export Layouts from staging
- Import Layouts in the live site
Hi Christian,
So this is related to WpEngine cache, Varnish? I can try and get them to turn it off for layouts in the admin area. I have had them turn off a page manually for me before.
Yes from what we can tell it's related to WPEngine's caching system. If it's possible to disable caching for requests initiated by the Layouts editor pages, that may be enough to fix the problem temporarily.
Hi, we are going through some older tickets and it seems that notifications for this one fell through the cracks somehow. I can see that the fix for this issue was released in Layouts, and the problem should be resolved. Please let me know if that is not the case.
