Viewing 4 replies - 1 through 4 (of 4 total)
  • Normally you would not run a production site in debug mode, because of performance and possible exposure of sensitive data on the public site.
    There should be a reason that the buttons disabled, so if you can figure that out, you wouldn’t need to use the debug mode.

    Thread Starter David Borrink

    (@davidborrink)

    Thanks. I pulled the code out of the config file and looked at my console while visiting the dashboard. I’m not seeing any errors at the moment, but the buttons aren’t fading so this is obviously an intermittent problem. I’ll have to keep an eye on it.

    Thread Starter David Borrink

    (@davidborrink)

    I followed the instructions on this page: https://codex.wordpress.org/Using_Your_Browser_to_Diagnose_JavaScript_Errors

    After doing the define('SCRIPT_DEBUG', true); method in my config file, I went to step 3 checking the error console. Opening the console and checking errors doesn’t show me anything except two errors referenced as a wp-review plugin and the tinymce files.

    Can anyone tell me what I could do to find out why the draft and publish buttons stay deactivated? We’re using a workaround, but it’s getting old.

    Screen shot from my dash on a post…
    https://prnt.sc/lq7ucd

    Thread Starter David Borrink

    (@davidborrink)

    Found a solution, simply re-install WordPress by going to Dashboard > Updates and choose the re-install option. It’s a “clear the head” reset that obviously fixes whatever is causing the hangup.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Using SCRIPT_DEBUG to fix dimmed publish buttons in dash’ is closed to new replies.