Debug modes

Use debugging when you need readable errors for yourself or for support. Turn debugging off on production once the issue is fixed.

1. Ultimate plugin debug / script loading

  1. Go to Progress Map → Troubleshooting.
  2. Under Debug mode & Speed Optimization, open Loading scripts & styles.
  3. Choose Separate files (Debugging versions).
  4. Save.
Option Use
Separate files (Minified versions) Default / recommended for production
Separate files (Debugging versions) Easier to debug JS; slightly heavier
Combine files Deprecated — do not use

Leave minified mode on after troubleshooting — debug builds can slow the map.

2. WordPress debugging (wp-config.php)

On staging (preferred), edit wp-config.php in the site root:

define( 'WP_DEBUG', true );

if ( WP_DEBUG ) {
	error_reporting( -1 );
	@ini_set( 'log_errors', true );
	@ini_set( 'log_errors_max_len', '0' );

	define( 'WP_DEBUG_LOG', true );
	define( 'WP_DEBUG_DISPLAY', false ); // Prefer log-only on staging/public
	define( 'CONCATENATE_SCRIPTS', false );
	define( 'SCRIPT_DEBUG', true );
}

Notes:

  • Use boolean true / false — not the strings 'true' / 'false'.
  • Prefer WP_DEBUG_DISPLAY = false so visitors never see PHP errors; read wp-content/debug.log instead.
  • A log viewer plugin can help read debug.log from wp-admin.

3. What to send to support

  • Ultimate version (About Ultimate)
  • Enabled modules
  • Exact front-end URL of the map
  • Browser console errors
  • Relevant lines from debug.log
  • Confirmation that Pro / standalone add-ons are inactive

Related

Top