Skip Navigation

[Resolved] Custom post type in the backend causing: There has been a critical error

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 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 -

Supporter timezone: America/Sao_Paulo (GMT-03:00)

This topic contains 1 reply, has 2 voices.

Last updated by Mateus Getulio 1 year, 1 month ago.

Assisted by: Mateus Getulio.

Author
Posts
#2664179

When i click the custom post type i made to add a post the wordpress 'There has been a critical error...' comes up.
Could you help me sort this out?

Thanks!

#2664287

Mateus Getulio
Supporter

Languages: English (English )

Timezone: America/Sao_Paulo (GMT-03:00)

Hello there,

Thank you for contacting the Toolset support.

So that we can take a better look at this, could you please attach the Debug info?

You can see how to retrieve and paste it here: https://toolset.com/faq/provide-debug-information-faster-support/

In addition to that, I'd also like your help enabling the WordPress debug mode.

To do so, please add the following code in wp-config.php file of your site:

// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );
  
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );
  
// Disable display of errors and warnings 
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
  
// Use dev versions of core JS and CSS files (only needed if you are modifying these core files)
define( 'SCRIPT_DEBUG', true );

Please check following links to read more about debugging with WordPress.

https://codex.wordpress.org/Debugging_in_WordPress
https://codex.wordpress.org/Debugging_in_WordPress#Example_wp-config.php_for_Debugging

After doing that please try to reproduce the issue again, then check if you can find a file debug.log inside the wp-content folder. Open it and send us the last lines of log here in this ticket.

Thanks, please let us know.

#2664357

It was a plugin conflict

Thank you for the advice!