• Updating from V11.9.1 to V12.0 broke my site.

    I managed to recover by disabling the pkugin via SSH and downgrading but would like to see a fix.

Viewing 13 replies - 1 through 13 (of 13 total)
  • Plugin Support Aditya Bhaskar Sharma

    (@adictonat0r)

    Hi @scldad

    Thank you for reaching out and bringing this issue to our attention.

    I’m sorry to hear that the update to v12.0 caused problems on your site. We strive to ensure smooth transitions between versions, and I’d like to help resolve this for you.

    To better understand what might have caused the issue, could you please provide some additional details?

    1. What version of WordPress are you currently using?
    2. Did you notice any specific error messages or logs when your site broke?
    3. Can you share any server details (PHP version, hosting provider, etc.) that might be relevant?

    Once we have this information, we’ll be in a better position to identify the cause and work on a fix.

    Thank you for your patience, and we look forward to your response.

    Best regards,
    Aditya
    Contributor & Maintainer

    Thread Starter Stephen Davies

    (@scldad)

    Thanks for getting back to me so promptly.

    WP V6.6.1

    PHP V8.2

    Host: Dreamhost

    Error: Cookies blocked due to unexpected output (or words to that effect)

    This meant that I could not login to my site until I deactivated the plugin via SSH.

    Cheers,

    Stephen

    Plugin Support Aditya Bhaskar Sharma

    (@adictonat0r)

    Hi Stephen,

    Thanks for the quick update.

    The error suggests there might be an issue with output being sent before headers, which can block cookies and cause login problems.

    To help us investigate, could you let us know if:

    1. You saw any specific errors in your logs before this happened?
    2. There were any recent changes to your site (like new plugins or theme updates)?

    We’ll work on identifying the cause and getting a fix out.

    Thanks for your patience.

    Best regards,
    Aditya
    Contributor & Maintainer

    Thread Starter Stephen Davies

    (@scldad)

    A raft of warnings such as:

    [05-Aug-2024 00:08:04 UTC] PHP Warning: foreach() argument must be of type array|object, null given in /home/hmac1956/holdfastmac.asn.au/wp-content/plugins/css-javascript-toolbox/framework/db/mysql/table.inc.php on line 102
    [05-Aug-2024 00:08:06 UTC] PHP Warning: Undefined property: stdClass::$pages in /home/hmac1956/holdfastmac.asn.au/wp-content/plugins/css-javascript-toolbox/models/blocks.php on line 198
    [05-Aug-2024 00:08:06 UTC] PHP Warning: Undefined property: stdClass::$posts in /home/hmac1956/holdfastmac.asn.au/wp-content/plugins/css-javascript-toolbox/models/blocks.php on line 199
    [05-Aug-2024 00:08:06 UTC] PHP Warning: Undefined property: stdClass::$categories in /home/hmac1956/holdfastmac.asn.au/wp-content/plugins/css-javascript-toolbox/models/blocks.php on line 200
    [05-Aug-2024 00:08:06 UTC] PHP Warning: Undefined property: stdClass::$post_tags in /home/hmac1956/holdfastmac.asn.au/wp-content/plugins/css-javascript-toolbox/models/blocks.php on line 201
    [07-Aug-2024 07:20:32 UTC] PHP Warning: foreach() argument must be of type array|object, null given in /home/hmac1956/holdfastmac.asn.au/wp-content/plugins/css-javascript-toolbox/framework/db/mysql/table.inc.php on line 102
    [07-Aug-2024 07:20:33 UTC] PHP Warning: Undefined property: stdClass::$pages in /home/hmac1956/holdfastmac.asn.au/wp-content/plugins/css-javascript-toolbox/models/blocks.php on line 198
    [07-Aug-2024 07:20:33 UTC] PHP Warning: Undefined property: stdClass::$posts in /home/hmac1956/holdfastmac.asn.au/wp-content/plugins/css-javascript-toolbox/models/blocks.php on line 199
    [07-Aug-2024 07:20:33 UTC] PHP Warning: Undefined property: stdClass::$categories in /home/hmac1956/holdfastmac.asn.au/wp-content/plugins/css-javascript-toolbox/models/blocks.php on line 200
    [07-Aug-2024 07:20:33 UTC] PHP Warning: Undefined property: stdClass::$post_tags in /home/hmac1956/holdfastmac.asn.au/wp-content/plugins/css-javascript-toolbox/models/blocks.php on line 201
    [08-Aug-2024 00:38:13 UTC] PHP Warning: Attempt to read property “ID” on null in /home/hmac1956/holdfastmac.asn.au/wp-content/plugins/css-javascript-toolbox/models/metabox.php on line 112
    [08-Aug-2024 06:15:02 UTC] PHP Warning: Cannot modify header information – headers already sent by (output started at /home/hmac1956/holdfastmac.asn.au/wp-content/plugins/css-javascript-toolbox/framework/php/includes.class.php:1) in /home/hmac1956/holdfastmac.asn.au/wp-admin/includes/misc.php on line 1438
    [09-Aug-2024 11:21:07 UTC] PHP Warning: Attempt to read property “ID” on null in /home/hmac1956/holdfastmac.asn.au/wp-content/plugins/css-javascript-toolbox/controllers/blocks-coupling.php on line 702

    Sometimes repeated with different line numbers but no “error” messages.

    I did update another plugin at the same time (just before the lockout) but trial and error excluded it from the issue.

    Plugin Support Aditya Bhaskar Sharma

    (@adictonat0r)

    Hi Stephen,

    Thanks for sharing the warnings.

    It looks like the plugin is encountering some null values where it expects data, which is likely causing the issues you’re seeing. The “headers already sent” warning is also consistent with the login problem.

    I’ll start looking into these specific areas to identify the root cause. In the meantime, if you haven’t already, could you confirm if reverting to V11.9.1 resolved all the issues?

    Thanks for your help in troubleshooting this. We’ll work on a fix ASAP.

    Best regards,
    Aditya
    Contributor & Maintainer

    Hi,
    I have the same issue with this update on multiple sites.
    All are running the latest version of WP, PHP, and hosted on SiteGround.
    Sometimes the sites does not come up when typing the URL manually in the URL bar.
    Using a link works oddly enough.
    /wp-admin/ is not accessible, only a white screen is shown.
    No errors are shown.

    Rolling back to the previous version resolves this.

    Regards

    Thread Starter Stephen Davies

    (@scldad)

    Yes. Downgrading stops the problem

    Plugin Support Aditya Bhaskar Sharma

    (@adictonat0r)

    Hi @torkild

    Thanks for reaching out and letting us know you’re experiencing the same issue.

    It seems similar to what Stephen reported, with sites running the latest WP and PHP versions.

    We’re investigating the issue and will work on a fix. In the meantime, rolling back to the previous version is a good temporary solution, as you mentioned.

    If you notice anything else unusual or if any error logs do appear, please share them with us.

    Thanks for your patience.

    Best regards,
    Aditya
    Contributor & Maintainer,

    Thread Starter Stephen Davies

    (@scldad)

    Just checked the logs for V11.9.1 and the “Attempt to read property “ID” on null” warning is also there in models/metabox.php on line 112 and controllers/blocks-coupling.php on line 702.

    Plugin Support Aditya Bhaskar Sharma

    (@adictonat0r)

    Hi Stephen,

    Thanks for the follow-up.

    The “Attempt to read property ‘ID’ on null” warnings aren’t critical errors, rather more of a heads-up that the code is encountering unexpected data. While they don’t usually affect functionality, I understand they can be concerning.

    We’re planning to address these warnings in upcoming releases as part of our ongoing improvements to CSS & JavaScript Toolbox. We’ll make sure to smooth out these issues as we push more updates.

    Thanks for your patience and for bringing this to our attention.

    Best regards,
    Aditya
    Contributor & Maintainer

    Plugin Support Aditya Bhaskar Sharma

    (@adictonat0r)

    Hi everyone,

    We are pleased to announce that we have released a new version of the plugin, v12.0.1, for both CJT Free and CJT PLUS versions. This update includes several fixes and improvements.

    We recommend installing the latest version and checking to see if the issues you experienced have been resolved. Your input has been invaluable in making these updates, and we’re confident this version will offer a better experience.

    If you encounter any further issues or have additional feedback, please don’t hesitate to reach out. We’re here to help and ensure everything runs smoothly.

    Thank you for your patience and continued support!

    Best regards,
    Aditya
    Contributor & Maintainer

    Thread Starter Stephen Davies

    (@scldad)

    Looks good ??

    Plugin Support Aditya Bhaskar Sharma

    (@adictonat0r)

    Hi @scldad

    I’m glad to hear that the issue has been resolved. Thank you for confirming and for your cooperation throughout this process.

    Since the problem is fixed, I’ll go ahead and close this issue thread. If you encounter any other issues or have additional feedback, please feel free to open a new thread or contact us directly.

    Thanks again for your support!

    Best regards,
    Aditya
    Contributor & Maintainer

Viewing 13 replies - 1 through 13 (of 13 total)
  • You must be logged in to reply to this topic.