Dev site takes over sync | ww.wp.xz.cn

Resolved thomaskarl
(@thomaskarl)

4 years, 6 months ago

Hi, it seems like every time we are cloning the http://www.live.com site to http://www.dev.com site.
Omnisend plugin starts to use the http://www.dev.com site as the ‘main’ site.
And therefor we need to remember to remove the Omnisend plugin on http://www.dev.com and ‘re-add’ it to http://www.live.com to get the sync to start to work again on http://www.live.com.
Any other way this can be solved?

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

Plugin Author Omnisend
(@omnisend)

4 years ago

Hello there!
Thank you for taking the time to submit a support request!

Do you use the updated plugin version? Can you let me know if the Omnisend snippet is present in both the development and production websites? To avoid an issue like this, we recommend removing the snippet from the development website code and leave it only with the production one.

Thread Starter thomaskarl
(@thomaskarl)

4 years ago

Yes, if plugin is on development website, it is going to be problems.
When working with many plugins and sites, and are cloning sites from production to development all the time. It is impossible to keep track on what plugins that cannot be activated on development sites…
Would be great if plugin could be working only with production site without have to remove snippet on development site.

Plugin Author Omnisend
(@omnisend)

4 years ago

Can you share links to both the production and development websites? When copying the development website content to the production one, is Omnisend installed on both website versions? Do they share the same backend?

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

The topic ‘Dev site takes over sync’ is closed to new replies.

3 replies
4 participants
Last reply from: Omnisend
Last activity: 4 years ago
Status: resolved