Jack Arturo

Hey @italianiit ,

I just did a quick test on my local Multisite install and it connects when network activated, or activated at a sub-site.

Where do you see the error message? Is it on a HubSpot-hosted page? Or is it shown after you authorize the connection and return to the WordPress admin?

Thanks
Jack

Hey @kierancalv ,

It looks like Forminator v1.30.0 overhauled their integrations framework. We have an update coming out today that will fix the errors, but I’m not sure if the WP Fusion integration will work anymore (I’m unable to configure new forms, it’s possible that existing form submissions will still sync).

We’re waiting to hear back from the Forminator team as to whether they’ll be releasing an update that fixes this. At the moment several of the integration points we depend on have been removed.

If you can I’d advise downgrading to Forminator 1.29 while we try and figure out what’s changed and what can be fixed.

Jack

Hey @edivantrev 👋

No, it shouldn’t ever require reauthorization. How often does this happen?

Mautic’s “access tokens” last 14 days. So that means after 14 days, an API call will fail due to an expired token. WP Fusion then connects to Mautic to “refresh” the token, and repeats the API call.

If you’re getting disconnected about once every 14 days, then it seems like the refresh process is failing. You could turn on HTTP API logging to record the full API calls: https://wpfusion.com/documentation/getting-started/activity-logs/#http-api-logging

If you can catch the refresh failing that might show an error code or something to indicate why.

Also, FYI, we have sometimes observed problems with this and Redis / Memcached caching. The old access token gets cached and the new one isn’t saved correctly. If you are using Redis, try disabling it around two weeks after you last reauthorized the connection to see if this fixes the refresh. If so, changing Redis plugins should improve the reliability, as some plugins are more aggressive than others about caching data in the admin.

Thanks for the kind review @tufty !! 🤩

Yeah it’s tested up to 6.5.0 actually, just forgot to update the readme. It’s updated now for the next release 👍. Thanks.

@mvisman Yes, that’s right….

The reason is, you might have multiple forms (or multiple sites) connected to the same FluentCRM instance.

So we wouldn’t want someone to sign up on Site A with

First Name: Bruce
Last Name: Wayne

and then they fill out a form later on Site B with just

First Name: Bruce
Last Name:

We don’t want to erase the data that was added earlier. So by default, WP Fusion ignores any empty fields. This works the other way as well.

If you want to change that, you can change the field type to “raw” in the contact fields list: https://wpfusion.com/documentation/getting-started/syncing-contact-fields/#field-types

Ok. But the settings never save? i.e. you add an email address to the “Notification – Email” field, and click Save Changes (https://i.wpfusion.com/tC2ZcyfF), and when you reload the page nothing is saved?

If it’s not a plugin conflict, and there’s no caching, then I’m not sure.

You can easily spin up a test site on Instawp (https://instawp.io/) and install the plugin, and see that the settings save, and the test emails send.

So we need to think about what might be special about your server.

Do you have any other customizations or anything you can think of that might be special? i.e. multisite, separate database server…?

Do you have any issues with other plugins’ settings not saving?

Are there any errors recorded in the PHP error logs?

@okvee Gotcha, sorry, was copying from a template. No active plugins ✅

Since the settings aren’t saving that probably explains why the emails aren’t sending. The destination email can’t be read out of the database.

Are you using object caching (i.e. Redis) or memcached? Can you try flushing or disabling it temporarily to see if it allows the settings to save?

Removing the settings— in most cases you would not want to delete all the settings just because the plugin is deactivated (we deactivate plugins all the time during testing). But yes, we can add an option like “Delete all settings when this plugin is next deactivated”. We’ll work on that for the next update. Thanks!