sert-disable-block-css file is causing error

  • Resolved Creatives

    (@julialifetime)


    7 months, 2 weeks ago

    Hi there, we are experiencing a random error that shows up in error logs as coming from the sert-disable-block-css file:

    Use of undefined constant PHP_MAX_INT – assumed ‘PHP_MAX_INT’ INT’ (this will throw an Error in a future version of PHP) in | | | /nas/content/live/lifetimenew2/wp-content/plugins/sert-disable-block-css/sert-disable-block-css.php on line 14]

    I found the file, but it says version 1.0 of Remove Gutenberg CSS even though we have your latest version, 3.2.3 installed. I am not sure what to do other than disable the plugin until we can resolve, the random error completely breaks the home page when it happens.
    Thanks in advance for your help!

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Jeff Starr

    (@specialk)

    7 months, 2 weeks ago

    Hey I am glad to help investigate and resolve any issue. Just need the basic steps to repeat the issue starting from default WordPress installation, so something like:

    1. Install WordPress
    2. Activate DG plugin
    3. Perform some action
    4. Visit some page
    5. Etc., until the issue happens

    That way I can follow along and try to help asap, thank you.

    Plugin Author Jeff Starr

    (@specialk)

    5 months ago

    Hi @julialifetime, just wanted to follow up with this. It’s been a while with no reply, so I hope the issue is resolved? Or if there is anything I can do to help, please let me know. Thank you.

    Plugin Author Jeff Starr

    (@specialk)

    4 months, 2 weeks ago

    Hi @julialifetime, I hope you got this sorted. It’s been a while with no reply so gonna go ahead and mark this thread as resolved to help keep the forum organized. Feel free to post again with any further questions or feedback, I am glad to help anytime. Thank you.

    Thread Starter Creatives

    (@julialifetime)

    4 months, 2 weeks ago

    Hi Jeff,

    Thank you and apologies for not getting back sooner. We did disable and remove the plugin, and then reinstalled and activated. No more error for it, so not clear as to why, but all working well. Thanks for your help!

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

You must be logged in to reply to this topic.