Skip Navigation

[Resolved] error 503 Service Temporarily Unavailable when trying to save / update post type

This support ticket is created 7 years ago. 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
- 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 9:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Hong_Kong (GMT+08:00)

This topic contains 6 replies, has 3 voices.

Last updated by peterJ-3 7 years ago.

Assisted by: Luo Yang.

Author
Posts
#584566
503 error.PNG

I am trying to: save post type or update a post type child or parent

Link to a page where the issue can be seen: hidden link

I expected to see: the post type page render with the updates I made

Instead, I got: error 503
"Service Temporarily Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
Web Server at davidzohar.com"

i diabled all plugins and mate only type available and still go the error
i canged the theme to defaulr theme and still got the error
i cahcked the same thing on another website i have that have tootlset installed on and got the same error

Please advise,
thanks,

David

#584688

Dear David,

There should be some PHP errors occur in your website, we need to see the PHP debug logs of your website, please check these:
1) deactivate other plugins and switch to wordpress default theme
2) Enable PHP debug mode, copy and paste the debug logs here
PHP Debugging
In case you think that Types or Views are doing something wrong (what we call a bug), you should enable PHP error logging. Again, edit your wp-config.php file and add the following:

ini_set('log_errors',TRUE);
ini_set('error_reporting', E_ALL);
ini_set('error_log', dirname(__FILE__) . '/error_log.txt');
This will produce a file called ‘error_log.txt’ in your WordPress root directory. Make sure that the web server can create and write this file. If it cannot, use an FTP program to create the file and make it writable to Apache (normally, user www-data).
https://toolset.com/documentation/user-guides/debugging-types-and-views/

#584689

Hi Luo,
I have disabled all plugin
activated only toolset type plugin
default the theme to
enabled debug by putting the following in my wp-config.php file

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

ini_set('log_errors',TRUE);
ini_set('error_reporting', E_ALL);
ini_set('error_log', dirname(__FILE__) . '/error_log.txt');

the text file was not created.
I created the file manually on the root folder of WordPress and is having read write permission

I repro the steps to update the custom post save and got the same error.
I look at the erro_log.txt file but its empty.

here is t debug information from toolset:

{"core":{"Wordpress":{"Multisite":"No","SiteURL":"https:\/\/www.davidzohar.com","HomeURL":"https:\/\/www.davidzohar.com","Version":"4.8.3","PermalinkStructure":"\/%category%\/%postname%\/","PostTypes":"post, page, attachment, revision, nav_menu_item, custom_css, customize_changeset, wp-types-group, wp-types-user-group, wp-types-term-group, net-worth, budget, investment-profile, retirement, education, major-purchase, life-insurance-need, assumption, education-parent","PostSatus":"publish, future, draft, pending, private, trash, auto-draft, inherit"},"Server":{"jQueryVersion":"1.12.4","PHPVersion":"7.1.10","MySQLVersion":"5.5.56","ServerSoftware":"Apache"},"PHP":{"MemoryLimit":"256M","UploadMax":"2M","PostMax":"8M","TimeLimit":"30","MaxInputVars":"1000"}},"plugins":{"active_plugins":{"types\/wpcf.php":{"Name":"Toolset Types","PluginURI":"http:\/\/wordpress.org\/extend\/plugins\/types\/","Version":"2.2.16","Author":"OnTheGoSystems","AuthorURI":"http:\/\/www.onthegosystems.com","TextDomain":"types","DomainPath":"","Network":false,"Title":"Toolset Types","AuthorName":"OnTheGoSystems"}},"mu_plugins":[],"dropins":{"maintenance.php":{"Name":"maintenance.php","PluginURI":"","Version":"","Description":"","Author":"","AuthorURI":"","TextDomain":"","DomainPath":"","Network":false,"Title":"","AuthorName":""}}},"theme":{"Name":"Twenty Sixteen","ThemeURI":null,"Author":"\u003Ca href=\u0022https:\/\/wordpress.org\/\u0022\u003Ethe WordPress team\u003C\/a\u003E","AuthorURI":null,"Template":"twentysixteen","Version":"1.3","TextDomain":null,"DomainPath":null},"extra-debug":{"types":{"add_resized_images_to_library":0,"register_translations_on_import":1,"images_remote":0,"images_remote_cache_time":"36","help_box":"by_types","hide_standard_custom_fields_metabox":"show","postmeta_unfiltered_html":"on","usermeta_unfiltered_html":"on"}}}

please advise,
thanks,

David

#584690

Please check it latter, some webserver will create the error logs file in 10 minutes, and you can also ask the PHP debug logs form your webserver provider.

#584691

ok,
I got some lines in the err-log.text file

all the lines are the same:

[01-Nov-2017 04:51:52 UTC] PHP Warning: Creating default object from empty value in /var/www/vhosts/davidzohar.com/httpdocs/wp-content/plugins/cred-frontend-editor/application/models/form/data.php on line 56

any thoughts?

david

#584721

That is a PHP warning message from CRED plugin, it it should be not take effect on updating post in the admin side, please deactivate CRED plugin, then update the child/parent post, and get the fresh debug logs.
Check if the problem still persists after you deactivate CRED plugin.
If the problem is fixed by deactivating CRED plugin, please provide a database dump file (ZIP file) of your website in below private detail box, I need to test and debug it in my localhost, thanks

#584999

I have the same problem and am getting around it by disabling heartbeat in wordpress itself. The plugin "Control Heartbeat" allows you to do this. Toolset creates huge spikes of server load through wp-admin.php in connection with Heartbeat and was regularly taking our site down. I would recommend using the last version of Control Heartbeat rather than the latest one, which produces some php warnings.

The downside to this is that the Edit with Layouts button in individual posts will not function without heartbeat.