• adamestafford

    (@adamestafford)


    I’ve installed the plugin on a website in development and received the error “There has been a critical error on your website. Please check your site admin email inbox for instructions.” I installed on a new, empty WP installation and get the same error. I setup debug and get a few more lines of error code:

    “Recoverable fatal error: Object of class WP_Error could not be converted to string in /home/jot*******/public_html/wp-includes/formatting.php on line 1117”

    and

    “Warning: base64_decode() expects parameter 1 to be string, object given in /home/jot*******/public_html/wp-content/plugins/church-community-builder-core-api/includes/class-ccb-core-helpers.php on line 184”

    I’m running PHP 7.2 on GoDaddy. Thanks.

Viewing 15 replies - 1 through 15 (of 16 total)
  • ponderconsulting

    (@ponderconsulting)

    Looks like you’re not alone. https://wordpress.org/support/topic/api-error-43/

    Thread Starter adamestafford

    (@adamestafford)

    Thanks @ponderconsulting

    I was hoping since that was a year ago something would be in the works or at least fixed. :/

    Plugin Author Jared Cobb

    (@jaredcobb)

    @adamestafford @ponderconsulting I have a major release coming soon which resolves this bug (related to newer versions of PHP and how encryption is handled).

    You can download a beta version of it directly here https://github.com/jaredcobb/ccb-core/archive/master.zip

    I should have it updated in the WordPress.org repo (and available to update within WordPress) in the next few days.

    ponderconsulting

    (@ponderconsulting)

    My pleasure, good luck @adamestafford!

    Thread Starter adamestafford

    (@adamestafford)

    @jaredcobb thanks for this! I downloaded the beta and uploaded. I’m still getting the same error. Could this be a hosting issue?

    Plugin Author Jared Cobb

    (@jaredcobb)

    @adamestafford Can you confirm whether you have also deactivated/deleted the known broken version? If both plugins are activated I believe the older one will take precedence.

    ponderconsulting

    (@ponderconsulting)

    <Turning off follow-up replies via email>

    Thread Starter adamestafford

    (@adamestafford)

    @jaredcobb yes. I deactivated the plugin and deleted it. then uploaded the new.

    Running the site locally with MAMP and PHP 7.2 it doesn’t give me the error. But I was running an older version of WP, added the plugin, then updated. I’ve tried to revert the WP version but no luck yet.

    Screenshot

    Plugin Author Jared Cobb

    (@jaredcobb)

    @adamestafford I believe I know the root cause of this issue. I believe the older (broken) version of the plugin has left some bad data in place. I appreciate this report, it’ll allow me to ensure this doesn’t happen for other users moving forward.

    In the short term, the best way to fix this will be to either:

    1. Edit your wp_options table and delete the row with the option_name of ccb_core_settings or
    2. Use a plugin that allows you to edit options, for example https://wordpress.org/plugins/options-inspector/ and delete the ccb_core_settings option.

    Thread Starter adamestafford

    (@adamestafford)

    @jaredcobb thanks. I tried this but it still gives the error.

    Plugin Author Jared Cobb

    (@jaredcobb)

    @adamestafford It sounds like there is still some bad data somewhere. Can you delete all options that begin with ccb_core_ in the database? That won’t hurt anything and essentially resets the installation.

    Thread Starter adamestafford

    (@adamestafford)

    @jaredcobb ok. Can do. These are the only 2 rows in the wp_options table remaining that contain ccb_core_ I’ll remove and try again. Thank you for the help.

    screenshot

    Thread Starter adamestafford

    (@adamestafford)

    @jaredcobb Deleted both rows, removed the plugin. Installed again, and tried entering the creds. Still giving the error.

    Plugin Author Jared Cobb

    (@jaredcobb)

    @adamestafford Thanks for your patience and helping me to troubleshoot this! I created a brand new environment to match yours, and I’m able to now replicate the issue. In short, it has to do with the specific version of PHP and how I’m handling encryption. I should have an update ready in the next day or so. My apologies for the inconvenience.

    Thread Starter adamestafford

    (@adamestafford)

    @jaredcobb ah! ok. great! thank you so much!!!

Viewing 15 replies - 1 through 15 (of 16 total)
  • The topic ‘There has been a critical error on your website’ is closed to new replies.