I recently changed server. Problem is that the backend is too slow. I am getting "Toolset plugin cannot connect to toolset.com" error on my dashboard.
Communication error details,
toolset: Unable to register: Site key not matching subscription-fetching 2024-28-08 01:08:44
toolset: Unable to register: Site key not matching subscription-fetching 2024-27-08 01:08:29
toolset: Unable to register: Site key not matching subscription-fetching 2024-26-08 01:08:22
toolset: Unable to register: Site key not matching subscription-fetching 2024-25-08 01:08:10
toolset: Unable to register: Site key not matching subscription-fetching 2024-24-08 01:08:51
toolset: Unable to register: Site key not matching subscription-fetching 2024-23-08 01:08:24
toolset: Unable to register: Site key not matching subscription-fetching 2024-22-08 01:08:04
toolset: Unable to register: Site key not matching subscription-fetching 2024-21-08 01:08:48
toolset: Unable to register: Site key not matching subscription-fetching 2024-20-08 01:08:37
Subscriptions updated successfully. subscription-fetching 2024-19-08 01:08:10
The website folder path structure is currently changed while migrating, I have already changed the the url structure in the database.
Before: vinjournalen/public-html/wpsysfiles/wp-content/.....
Now: vinjournalen/public-html/wp-content/....
Is this somehow affecting my website?
website: hidden link
The site key is explicitly tied to the site URL. If you change the URL (even changing from http to https) then you need to replace the key with a new key for that specific URL.
The "Site key not matching" message suggests that the URL itself has changed.
I have changed the site name and also in the commercial tab, i have unregistered and re-registered using new site key.
Now i get "Toolset needs to update the database. This will take a few minutes to complete." when i click "update now". it seems to do nothing. Its been more than one hour, still getting same message in the dashboard.
Were you updating from a very old version of Types?
There were migration routines for post relationships in Types 3.0 and 3.4, it sounds like what you are describing may be related to those.
Could I take a look at your site to check?
Let me mark your next reply as private so that I can get log-in credentials from you—you may want to create a temporary admin user for me to use that you can later delete. And be sure to have a current backup of your site.
I can see an error in the browser console that prevents the database upgrade routine from running.
I tried to recreate a similar scenario on my own test site to see if it triggered a similar error, but it does not, the error seems specific to your site.
Do I have permission to take a copy of your site, to be able to test locally?
While reporting this issue internally I realised that the error occurs specifically in the context of WordPress 6.6, which removes a polyfill that Types depends upon. I've reported this to the developers so that we can fix this.
To fix the problem on your site in the meantime, you could temporarily downgrade WordPress (e.g. to version 6.5.5), run the process to upgrade the Toolset database, and then you can upgrade again to WordPress 6.6.
1. Take a backup
2. Install the WP Downgrade plugin, and use it to downgrade WP 6.5.5
3. Run the Toolset database upgrade process
4. Remove the WP Downgrade plugin
5. Update to WordPress 6.6.1
If you could please try that, and let me know how it goes.
That shows that the database migration worked, but during the process it noticed some inconsistencies in your existing data that it couldn't migrate. It is not unusual if you have a large number of connections between posts that a small number might be broken for some reason; the warning suggests there were a few examples that were broken before the migration which it wasn't able to fix.
But the process itself has completed normally, and you should now be able to revert back to WordPress 6.6.
