Got the issue notification again

astromono
(@astromono)

2 weeks, 4 days ago

Constant Contact Forms has experienced issues that may need addressed and functionality may be missing. Please enable the “Support” checkbox under the Support tab in Constant Contact settings and start a forum support thread. Our support team will aid with further steps.

https://pastebin.com/cBPXAm99

Aside from this notification, I also have a message saying the following: “Constant Contact Forms has detected errors that indicate a need to manually disconnect and reconnect your Constant Contact account. Visit the Connection Settings to manage.”

I already manually disconnected and pasted a new token to reconnect, but the message persists.

Thanks,

Luis

Viewing 3 replies - 1 through 3 (of 3 total)

Plugin Contributor Michael Beckwith
(@tw2113)

The BenchPresser

2 weeks, 4 days ago

By and large, based on the logs at least, it’s been mostly pretty steady. The most standout spot is in the last few days or so when it’s gotten a bit unstable.

It seems that the stored refresh token somehow got invalidated or not the newest refresh didn’t save properly on the 6th

On top of that, JSON errors are coming up today the 10th.

Is it still failing to connect? That JSON error line has me curious what the API responses are, but I am not able to recreate with my development environment. Wondering if you’d be willing to help extract more information.
Thread Starter astromono
(@astromono)

2 weeks, 3 days ago
Hi Michael, thanks for the assist. On the 6th was the day I created a staging instance of my WordPress installation, which basically mirrored my live instance down to plugins and everything. Maybe the error is happening because both installations were using the same token?

I’ve since changed the token for my live install and I’ve deactivated the plugin altogether in my staging site. Unfortunately, the notification is still showing on my live site.

Let me know what steps to follow if you wanna do the deep dive.

Thanks,

Luis
- This reply was modified 2 weeks, 3 days ago by astromono.
Plugin Contributor Michael Beckwith
(@tw2113)

The BenchPresser

2 weeks, 3 days ago

Maybe the error is happening because both installations were using the same token?

Access token wise,it’d be fine until the it expires (24hr lifespan).

Refresh token on the other hand would definitely be affected by this, as it’s tied with the connecting user + domain. We’re exploring messaging and methods to get around this without disrupting say the production tokens.

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.