Syncing issues

Hi @leodonnini, Sorry to hear you’re having issues with the plugin, we definitely want to try to help out. Just to get a handle on the situation you’re experiencing, could you provide a few more pieces of information to help us understand the issue?

– What plugin version are you using?
– Who is your hosting provider and can you check to see if they block access to the admin-ajax.php file for any reason?
– What PHP version are you using and what is the memory limit is set to?
– Is there any logging errors in the plugin’s logs tab (when it’s set to standard or debug)?
– Do you have any caching plugins or services running?

Thanks in advance for these details. I’ll keep an eye out for your reply.

Thank you for the answer.
I’ll try to provide the informations you asked for.

-I’m using the 2.1.9 version. I’ve downloaded it three or four times from the wordpress plugins list to try resolving the issue. I believe it’s the last version available, isn’t it?
-The hosting provider is VHosting at the moment. Unfortunately I don’t know for sure if that file is blocked for any reason but it shouldn’t be. In this case it’s importat to notice that the site is in construction, where I mean that we don’t have a domain yet. Not only, the domain belongs to the old site at the moment, that will be closed only at the end of the work for the new one. Don’t know if it can block the plugin from working correctly. Others work fine, so I didn’t think about this at first.
-PHP version has been updated to 7.1 before installing the plugin.
-I’ve already checked the logs tab, both in Standard and Debug mode, but no errors are explicitly shown: it says only: “2018-08-10T15:57:53+00:00 NOTICE sync.started :: Starting Sync :: Fri, Aug 10, 2018 3:57 PM” many times (’cause I’ve resynced it a couple of times.
-I’ve checked also for the caching, but we don’t have any plugin at all for caching, nor CDN networks active.

Thank you again, hope to resolve the problem.
Leonardo Donnini

• This reply was modified 6 years, 6 months ago by leodonnini.
• This reply was modified 6 years, 6 months ago by leodonnini.

@leodonnini thanks for that info – can you check to see if your site actually loads up the wp-admin/admin-ajax.php file ( that would return a white page with a 0 at least ) or if it redirects to an under construction page?

Checked!
It returned a blank page with a 0, as you said.

@leodonnini OK so – i’m a little bit confused on what you mean when you say that the domain is under construction / closing etc – do you mind expanding a bit on the scenario? Did you just migrate to a development server somewhere? Local?

If it’s easier for you to email us directly – just send that over to [email protected] – otherwise here is fine.

Yes, I’m sorry: it was not that much detailed.
So, this is the situation.
We are building a new site for an e-commerce at the moment, that means that an old site stil exists (on a different host) and can not be put offline untill the new one is ready. At the same time, the domain (registered at the moment for the old site) must not be changed. So we bought a new hosting space and started working there, but, because of the domain issue, we access it directly trough the ip of the hosting server (modifying the host file), ’cause otherwise the browser will show the old site.
This is a method we used in other occasions, so nothing too strange.
Hope I’ve been exhaustive now; sorry if it wasn’t clear.

Thanks!

@leodonnini – ok this is making more sense to me now.

You’re using the host file trick to get your local browser to load up the site at the new IP. That’s fine for your local machine – but your domain currently resolves to the old IP for the rest of the world. Your server is making post requests server side to the admin-ajax file which ends up going to the real server – not your new host.

I know – it’s confusing ??

I’m assuming that you’ve been trying to get the plugin to work with the new server, and not the ‘current’ site, correct?

If you’re installing the plugin on the new IP, you’ll have to change up your settings in wordpress to use the temporary domain name that you’ve gotten for this to act correctly – but that will have side effects and pass in the wrong URL to the MailChimp API – so I would not do that now.

I would suggest working with the plugin after your domain is migrated – or better yet – you should be able to get the WP-CLI version running up pretty quickly on this setup as long as you have command line access.

Do you have command line access to this server? We’ll get you all squared away here one way or another.

Hi ryan, sorry for the delay.
At last, we found somehow a solution using a temporary new domain and building all the site under it. When everything gets finished, we will migrate again to the ‘real’ definitive domain and put offline the old site.
Sorry for this ‘mess’, but we could not work on it after migrating in any way (for commercial issues), so I was searching for another solution.
When other plugins and tools got us problems for the same reason, we decided to proceed like that to just get over with this.
Thank you very much for your support, though!

Leonardo

• This reply was modified 6 years, 6 months ago by leodonnini.