Fatal Error with Legacy feeds

  • Resolved Isu

    (@isuke01)


    4 months, 2 weeks ago

    I noticed on one of my client’s page that get updated plugin Fatal error.
    The shortcode [custom-facebook-feed id="207785512594299"]

    They are having “legacy” feeds
    When the shortcode is used page is getting:
    PHP Fatal error: Uncaught TypeError: base64_decode(): Argument #1 ($string) must be of type string, array given /content/plugins/custom-facebook-feed/inc/SB_Facebook_Data_Encryption.php:99

    Seems like base64_decode is getting Array while it has set STRICT check.

    And there is another one when I tried to edit (click Settings) (second time it worked some how)
    PHP Fatal error: Uncaught TypeError: json_decode(): Argument #1 ($json) must be of type string, array given in public/content/plugins/custom-facebook-feed/inc/CFF_Shortcode.php:1827

    Plugin Version: 4.3.4
    WP: 6.8.3
    PHP: 8.2

    Sorry, I can’t give access to the page.

    NOTE: Seems like the “Source” is also missing but that’s my client’s fault. But I don’t think this should cause Fatal? 😀

    • This topic was modified 4 months, 2 weeks ago by Isu.
Viewing 1 replies (of 1 total)
  • Plugin Support Smash Balloon Manuel

    (@mescobar)

    4 months, 1 week ago

    Hi @isuke01,

    Thanks for reporting this issue. What you’re seeing does appear to be a PHP 8.2 compatibility issue related to how the plugin processes legacy feed data.

    What’s happening: PHP 8.2 enforces stricter type checking. In this case, the plugin is expecting string values for functions like base64_decode() and json_decode(), but it’s receiving arrays instead when handling legacy feed data, which triggers the errors you’re seeing.

    Next steps: Resolving this will require a plugin update from our developers. To help them investigate and fix this properly, could you please open a support ticket at: https://smashballoon.com/support

    When submitting the ticket, please include a full WordPress debug log. That information will allow us to trace exactly what’s happening with your specific feed configuration. In the meantime, we also recommend:

    • Reconnecting the source in the plugin to clear any related connection errors
    • Creating a new feed using the new plugin interface
    • Updating your legacy shortcode to the new format

    This should help reduce issues while we work toward a permanent fix. I appreciate your patience, and I look forward to continuing to work with you on this. If you have any questions in the meantime, feel free to let me know, I’m happy to help.

    Best,

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.