wp-admin/error_log unserialize(): Extra data in lib/PHPInsight/Sentiment.php

  • Resolved Adi

    (@publiushadrianus)


    3 months, 2 weeks ago

    It seems a part of this plugin is not quite compatible with PHP v8…
    I dug into the JWHennessey/phpInsight library repository on GitHub and it was last updated in 2018…

    For quite a few months now, ever since switching to PHP v8 (v8.3 currently), i keep getting these in the /wp-admin/error_log file. Any chance of fixing / updating / replacing this library?

    [10-Aug-2024 17:44:04 UTC] PHP Warning:  unserialize(): Extra data starting at offset 53 of 54 bytes in /webroot/wp-content/plugins/google-analytics-dashboard-for-wp/includes/gutenberg/headline-tool/phpinsight/lib/PHPInsight/Sentiment.php on line 360
    [10-Aug-2024 17:46:37 UTC] PHP Warning:  unserialize(): Extra data starting at offset 7816 of 7817 bytes in /webroot/wp-content/plugins/google-analytics-dashboard-for-wp/includes/gutenberg/headline-tool/phpinsight/lib/PHPInsight/Sentiment.php on line 230
    [10-Aug-2024 17:46:37 UTC] PHP Warning:  unserialize(): Extra data starting at offset 53 of 54 bytes in /webroot/wp-content/plugins/google-analytics-dashboard-for-wp/includes/gutenberg/headline-tool/phpinsight/lib/PHPInsight/Sentiment.php on line 360
    [11-Aug-2024 06:05:06 UTC] PHP Warning:  unserialize(): Extra data starting at offset 7816 of 7817 bytes in /webroot/wp-content/plugins/google-analytics-dashboard-for-wp/includes/gutenberg/headline-tool/phpinsight/lib/PHPInsight/Sentiment.php on line 230
    [11-Aug-2024 06:05:06 UTC] PHP Warning:  unserialize(): Extra data starting at offset 53 of 54 bytes in /webroot/wp-content/plugins/google-analytics-dashboard-for-wp/includes/gutenberg/headline-tool/phpinsight/lib/PHPInsight/Sentiment.php on line 360
    [11-Aug-2024 06:40:56 UTC] PHP Warning:  unserialize(): Extra data starting at offset 7816 of 7817 bytes in /webroot/wp-content/plugins/google-analytics-dashboard-for-wp/includes/gutenberg/headline-tool/phpinsight/lib/PHPInsight/Sentiment.php on line 230
    [11-Aug-2024 06:40:56 UTC] PHP Warning:  unserialize(): Extra data starting at offset 53 of 54 bytes in /webroot/wp-content/plugins/google-analytics-dashboard-for-wp/includes/gutenberg/headline-tool/phpinsight/lib/PHPInsight/Sentiment.php on line 360
    [11-Aug-2024 06:41:02 UTC] PHP Warning:  unserialize(): Extra data starting at offset 7816 of 7817 bytes in /webroot/wp-content/plugins/google-analytics-dashboard-for-wp/includes/gutenberg/headline-tool/phpinsight/lib/PHPInsight/Sentiment.php on line 230
    [11-Aug-2024 06:41:02 UTC] PHP Warning:  unserialize(): Extra data starting at offset 53 of 54 bytes in /webroot/wp-content/plugins/google-analytics-dashboard-for-wp/includes/gutenberg/headline-tool/phpinsight/lib/PHPInsight/Sentiment.php on line 360
    [11-Aug-2024 06:41:07 UTC] PHP Warning:  unserialize(): Extra data starting at offset 7816 of 7817 bytes in /webroot/wp-content/plugins/google-analytics-dashboard-for-wp/includes/gutenberg/headline-tool/phpinsight/lib/PHPInsight/Sentiment.php on line 230
    [11-Aug-2024 06:41:07 UTC] PHP Warning:  unserialize(): Extra data starting at offset 53 of 54 bytes in /webroot/wp-content/plugins/google-analytics-dashboard-for-wp/includes/gutenberg/headline-tool/phpinsight/lib/PHPInsight/Sentiment.php on line 360
    [11-Aug-2024 06:41:09 UTC] PHP Warning:  unserialize(): Extra data starting at offset 7816 of 7817 bytes in /webroot/wp-content/plugins/google-analytics-dashboard-for-wp/includes/gutenberg/headline-tool/phpinsight/lib/PHPInsight/Sentiment.php on line 230
    [11-Aug-2024 06:41:09 UTC] PHP Warning:  unserialize(): Extra data starting at offset 53 of 54 bytes in /webroot/wp-content/plugins/google-analytics-dashboard-for-wp/includes/gutenberg/headline-tool/phpinsight/lib/PHPInsight/Sentiment.php on line 360
Viewing 1 replies (of 1 total)
  • Plugin Support Michelle D.

    (@devmich)

    Hi @publiushadrianus,

    Thanks for bringing this to our attention! I apologize for the delay here.

    I consulted with our developers about this and they’ve let me know they’re planning to release the fix for this in our next patch release ??

    I’m not able to say exactly when that’ll be, but once the update is released, please ensure ExactMetrics is updated to the latest version to apply the fix.

    I hope this helps! Let me know if you have further questions.

    Thank you!

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