Settings could not be parsed – New clean install

Same thing is happening to me for the first time. It is also a new WordPress install, multisite is not enabled.

Hey y’all, thanks for posting here! This is actually a bug we are trying to track down so any help you can provide will be very much appreciated.

The most useful thing for me would actually be to get admin access to one of your sites —?if you can add me at [email protected], I can take a look.

If you can’t do that, the next best thing you would be to install Query Monitor and do a few things:

1. Visit the Clef settings page and walk through the tutorial.
2. When you see the error message, copy down the contents of the ajax message that happened directly before. Having access to the request headers and body would help me determine what exactly is going on here.

If you’d prefer, you can also achieve the above steps by using the Javascript Console to inspect the requests that are being sent.

Thank you so much for your help! If you’d prefer to work through this in private, you can also email us at [email protected] and we can get this solved.

Cheers,
Jesse

Hi, just wanted to follow up here —?any chance y’all can help us out with this information?

Thanks!

Hey Jesse,

For some reason my post didn’t email subscribe so I missed your replies.

Anyway, this is now working for me but no logical reason why it should. I turned on debugging to see what was coming up by adding this to wp-config

// log php errors
@ini_set(‘log_errors’,’On’);
@ini_set(‘display_errors’,’Off’);
@ini_set(‘error_log’,’/home/php-errors.log’);

and as soon as I had saved it Clef just started working. I can’t see what effect turning on error logging could possible have on the plugin but it worked twice.

Probally not much help in your bug hunt but at least its working perfectly now.

Thanks !

Thanks for that report @engagecommerce! Do you think there’s any chance I could have admin access to your site (or one like it that has the same issue)?

If not, would you mind letting me what host you use and anything special that you may have configured? I’m trying to reproduce this issue so I can fix it.

One more thing: off the top of my head, it looks like the switch from *displaying errors* to *logging error* may have caused Clef to start working. This makes me think that errors were being displayed somewhere, which was causing the body to not be parsed — do you think this could be possible? Could you try leaving display_errors on, and also having log errors on?

Thanks!

cc @jeremycaris – would love any help you can offer as well!

I’ve got the same, old site, to log in I have to go to another clef enabled.

Ahh breakthrough

I uninstalled, reinstalled. It just won’t finish setup.

Then I made an invite to a “super user” and it appears fixed!!!!

TA DA

Hi Jesse,

I was using FastComet, it was a setup for a client.

I’ve signed up for a FastComet account and ran the install again as I did for the client and the error hasn’t re-occured. Only difference was the client install was using HTTPS from Lets Encrypt and my one isn’t it.

No problem giving you admin access to the site I just setup but without the error I don’t think it will be much help. Let me know

Thanks,
Bob

@engagecommerce thanks for the information. if the error isn’t happening that won’t be helpful. you weren’t by any chance using a non-administrator account for the install were you?

@markcross when you say you “made an invite to a ‘super user’, what exactly do you mean? do you mean that you invited a super user to use Clef? or that you logged in as a super user and were able to set it up? Thanks!

>do you mean that you invited a super user to use Clef?
yes,

1. after I had the parsing error went away
2. the menu item on the LHS of WP indicating plug-in not set up properly went away

Mine was on a site which was using Clef, then stopped letting me in.
The only way to get back into the site, was to log into another WP site of mine also using CLef, which then allowed me to get in and have a look at the plug-in which may have been auto-updated by wordshell.

Experiencing the same problem. Did a fresh WP 4.5 installation via my hoster (A2 Hosting and Softaculous automated script). Clef came pre-installed and I’m getting the exact same problem as previous posters. Did a couple of reinstalls, wiping the WP database completely to be double sure: nope, bug still prevails.

@jollytime — do you think you could give me admin access to the site? My email is [email protected].

Thanks!

Hi Jesse. Why don’t you create a WP site from scratch using any of the hosters, so you can run all kinds of tests on your own?

I’ve swapped to another 2FA solution in the meantime, hoping this gets resolved sometime in the future.

We’re happy to announce that version 2.5.1 contains a fix for this issue. If you continue to see this error message after (a) updating the plugin and (b) refreshing your caches (browser and/or server-side caches), please let us know.