Plugin settings are missing or changed

To make sure I’m understanding: you are able to authenticate and see everything, but it becomes unauthenticated without any actions taking place. Correct?

I have this issue too —?I think since we just updated the plugin a few days to the latest version. Periodically it’s losing the settings and logs us out, so all of our forms disappear sitewide until someone manually goes in and logs in again in the plugin settings page.

Got it. I’m looking into this—if it is happening as a result of this newest release, it must be related to removing some seemingly dead code, as the update focused on other areas.

If you can, post here how long it’s taking for the plugin to become unconnected. That can help me isolate the issue.

2-3 times per day so 6-8 hours. Approx.
I fixed it temporary for myself with hardcoding settings in get_settings() if they missing.

Thanks. I’m keeping my eye on this today and looking at what’s happening.

Try adding back the following at line 927 in includes/pardot-settings-class.php and then re-auth:

$settings['password'] = self::pardot_encrypt( $settings['password'], 'pardot_key' );

That will mess up the formatting (possibly) in the settings area itself, but may be the part that’s causing the un-auth issue.

• This reply was modified 8 years, 2 months ago by Cliff Seal.

From my client, “So far I had to fix it an additional time today, around 3-4 hours later. Yesterday, it was disconnecting roughly every 2-3 hours. So on average…every 3 hours? As for anything after 5:30pm, I’m not sure.”

As posted in the other thread, I’ve added that line of code to to the plugin file and will see what happens. Crossing fingers. ??

My client had emailed Pardot Support directly before contacting me, and they suggested the following, which makes no sense to me — but thought I’d let you know in case there is some possible connection (we are using W3 Total Cache on our site) though I can’t figure out why a caching plugin would possibly wipe database settings:

“This problem can happen whenever there is a WordPress caching plugin or caching mechanism in place from a web host that is clearing the database information where the authentication data is stored. When this happens, the connector will show as not authenticated because this data has been purged.

The effect is similar to clicking on the “Reset All Settings” button on the plugin settings page.

I’d recommend also contacting your webhost and seeing if they have any caching services that could be causing this to happen and have them disable or configure differently. Also, see if you have any caching plugins (such as WP Super Cache) enabled that would be clearing out this data.”

I’ve released the update after some successful testing. Let me know if 1.4.2 doesn’t do the trick.

That code change didn’t work for us, it lost the settings again since I made that change. I’ll try the update but if that’s the only change, that may not be it, sorry.

• This reply was modified 8 years, 2 months ago by fastasleep.

Also, the API still doesn’t stick — if I try to change from 3 to 4 and save, it just reverts to 3.

Same problem again after updating, FYI. Settings are still present in the fields but the campaign dropdown goes back to “These will show up once you’re connected” and I gotta clear the fields and reauthenticate.

Can we roll back to a previous version?

Did you re-authenticate after updating? I’ve tried this in 3 different environments now, and the code itself is basically where it was in a previous update.

The API version will automatically revert to the one your account uses, so that’s an expected function.

I think it had stayed signed in when I updated, so I probably just left it. I just checked again for the first time this weekend since last signing in though, and it seems to have stuck! Pretty sure it was just that one time I had to sign back in after updating. So, I’ll keep watching this obviously but looks like it’s fixed if the above was just me neglecting to sign back in.

Thank you!

Looks like fixed.

Unfortunately, the issue appears again on one of our websites.