Shaun Robinson

That’s the one we’re using – strange.

This seems to be broken – after creating a table and saving it, you can no longer edit it.

Thanks

Yes that is correct, latest versions of everything.

Hi,

I’ve done all that – it’s not a Javascript error, because there is one line of PHP code in your plugin that can be commented out to fix the issue.

I realise the above is just a copy/paste job, please read the actual problem I linked to and you’ll find it is a bug with the plugin.

Custom built

No, not a conflict with ACF. Only a conflict when ANOTHER plugin uses ACF’s “get_field” function inside it, along with your plugin.

It is the latest version of WordPress.

I cannot share a link to the sites. But the thing they all had in common was another plugin, which simply included something similar to the following lines:

if(function_exists('get_field')) {
$something = get_field('something', 'options');
}

As you can see that is using the plugin Advanced Custom Fields, which was also up to date and active.

Deactivating that plugin, or yours, fixed the issue. But that plugin is active on lots of sites with no issue, it’s only when it clashes with yours that is the problem.

Actually this is not fixed – user switching now works on all domains, except for the one with its own domain

When I try to switch I get an error 500, and in my error log it says:

9810#0: *8022887 upstream sent too big header while reading response header from upstream

I’m using the default WordPress domain mapping, and in my WP Config file I have set:

define( ‘COOKIE_DOMAIN’, $_SERVER[ ‘HTTP_HOST’ ] );

Any ideas how to fix this?

Thanks
Shaun

Yep I’ve opened a ticket with them to look into it.

Just letting you know really.

In the meantime I’m just mapping the domain using the default WordPress way, introduced in 4.5, this does work.

Thanks
Shaun

Hi

This is a live and very busy website so switching themes and disabling plugins is going to be out of the question.

Are you saying some of those numbers could be draft or cancelled/pending products/orders? If so then that would be about right, so it should be fine.

We have started getting emails from the automation now so I think it’s all working, just showing incorrect numbers.

No

Using a different API key seemed to do the trick – not sure why that is.

Hi, I tried deactivating everything but it still does not work. I meet the minimum requirements. Any idea what could be wrong?

I’m having this exact same issue, was it resolved?