[Résolu] Invalid warning: Toolset plugin cannot connect to toolset
Ce fil est résolu. Voici une description du problème et la solution proposée.
Problem:
The issue here is that the user is getting the "Toolset plugin cannot connect to toolset.com" warning on their dashboard.
Solution:
This error generally occurs when you've migrated your site and the url changes and your Toolset plugins can no longer validate with our servers.
To check if your plugins are able to validate correctly you will need to go to Toolset -> Dashboard, then click on help in the top right hand corner. Select the Toolset Debug tab then click "Toolset Debug Information and Troubleshooting"
From there you will be taken to the Toolset Debug information. Scroll down on the page until you see the link for "Installer Support". Click this link.
You should now be able to see your site validation information. If you're see "Toolset site key not matching for http://www.xyz.com" then you will need to regenerate your site as the URL may have changed and your key isn't validating for the current URL.
Once you've done this go to Dashboard and click Check Again and the warning notice should no longer appear.
This support ticket is created Il y a 3 années et 1 mois. There's a good chance that you are reading advice that it now obsolete.
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
Aucun de nos assistants n'est disponible aujourd'hui sur le forum Jeu d'outils. Veuillez créer un ticket, et nous nous le traiterons dès notre prochaine connexion. Merci de votre compréhension.
Yes, the key is valid, the product is working, and I had done all that before writing. I've reset this multiple times.
The warning message shows up on the plugins home page, as well as any page in that part of the site. lien caché lien caché
etc.
The most likely cause of this is that this website had a different domain before. This site was previously registered for the subdomain lien caché
However, I've taken all the obvious steps such as removing the original key/registration and setting up a new one.
Also, the website was previously using WPML. I've since removed that plugin, but I still see it mentioned on this screen: lien caché
The errors there include,
toolset: Site key does not match for lien caché
wpml: Site key does not match for lien caché
I tried to reset the file "installer.php" by temporarily hiding it, but that breaks the site.
/wp-content/plugins/types/vendor/otgs/installer/installer.php
Hopefully the attached helps. Otherwise I guess you'd have to log in to see it.
Maybe I should remove the Toolset plugin(s) and reinstall them. Is it generally safe to do that without losing settings?
Just to clarify: although the annoying error message says "cannot connect to Toolset", it connects just fine.
The connection itself is not the problem; the plugin is updating and working perfectly.
It's just the existence of a nuisance warning, and the inability to get any new site key I generate to stop that false "mismatch" error, that I'm reporting.
...and I meant to repeat: although you will see WP Rocket installed, that's not what's causing this. Caching was cleared, and also I disabled it before as a test.
I don't see any other plugin here that would cause a conflict.
Usually i've seen this occur when users copy and paste their website URLs to register their plugin but it is always best to let our installer automatically get the URL.
That sounded promising. As you supposed, I was previously creating the key on your site by pasting the URL manually. So I followed step 3 and used the auto-registration method this time (after removing the key on both sides first).
Although the new key works and the website connects to Toolset just fine, that nuisance warning is still there at top of page.
I have to consider it a bug, but it's not a critical one. As you can tell from the domain above, it's actually a temp dev site and not really important. So I'm OK to just let this go since the client is not seeing it.
(FYI I had tried registering this site with the "dev site" checkbox both ticked and unticked, just out of curiosity. Since we have an unlimited license, I'm currently not actually using 'dev' status for this.)
And with that, the annoying warning dialog is also gone. I didn't have to refresh anything.
I think I just didn't wait long enough before writing my last note. It must have taken an interval for things to sync up after doing the key setup properly.
So the conclusion is: don't register the domains manually, and then wait longer after redoing it automatically. 🙂