[Resolved] Toolset plugin cannot connect to toolset
This support ticket is created 2 years, 5 months ago. 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.
No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.
I am trying to resolve the errors I am receiving from Toolset and WPML (same company right) that says it cannot connect to Toolset.com and WPML.com. (See screenshot).
Is there any documentation that you are following?
Yes. I have tried to resolve the issue by updating the site key. I recently moved to a new host. That went well. But after moving to the new host I pushed a backup from October which was saved when we were on our previous host. This caused the errors. We have resolved everything we can think of with the host, including reinstalling the WordPress files.
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 hidden link" then you will need to regenerate your site as the URL may have changed and your key isn't validating for the current URL.
As I mentioned in my initial reply, I have already followed the exact steps you sent me to update and register a new site key. However, I am still getting these errors. Please see the screenshot.
Since I have already done this, what is the next step in debugging this?
I acknowledge what you are pointing out however that issue is created by Toolset, not me.
When choose "generate a key for this site" it first shows me the correct and expected https prefix. However, once the key has been saved in my Toolset account and registered in the WP admin area, it shows as levelupforchange.org with the https prefix MISSING(!) and highlighted in yellow in the Toolset account. There is no option for me to manually set the address either.
Do tell me how to get past this since I have renewed the key 3 times now with no progress on the matter.
Would you like me to record a screencast to prove it to you?
Update: I now clicked on the site URL from within the Toolset account. This made the yellow highlight disappear and now the registered site is showing as the expected hidden link (see screenshot) But the ERROR IS STILL NOT RESOLVING within WordPress. It still says "site key not matching".
Strange. Unless I am misunderstanding what you did, I attempted to force a new connection several times. The errors have now resolved HOWEVER Toolset still doesn't seem to work as it should. When you go to the homepage and click " full resource hub", we get a 404 result that we didn't get before.
The resource hub is all built in Toolset. Please advise what the issue is. Thank you.
The issue with the resource page should now be resolved.
In a case like this when your page is returning an error 404 the best thing to do as a test is to revert your website to using the Default Permalinks for wordpress at Settings -> Permalinks then try to check the page if it loads.
If it does then its a clear indication that there is an issue with the PostName permalink setup. In Most cases refreshing the permalinks will fix the issue. What I mean by this is to select the default permalinks and hit save then refresh and set it back to postname.
In your case a simple refreshing the permalinks resolved the issue, however it can also be a case where your page slug is the same as the slug of a post type. For this you will need to change one or the other. For you this was not the case.
