Hello,
I purchasesd the product for hidden link
I need to test it on our staging installation : hidden link
When registering on staging with the site I get "Invalid site key for the current site" message.
What can be done about this please?
Thanks,
Jacques
Hi Jacques,
Thank you for contacting us and I'd be happy to assist.
We have a recommended approach for using the Toolset site key between the production and the development environments at:
https://toolset.com/faq/how-to-install-and-register-toolset/#registering-toolset-in-a-development-environment
Each registration site key is bound to the URL used to generate the key. This can create a challenge for site administrators who have different environments for development and production. If you create a site key for your live site, you cannot register your development site with the same site key. Instead, holders of the Unlimited Sites (and old, Lifetime) account can create as many different site keys as necessary to register Toolset in their development environments.
Since our 1 Site account plan only includes a single site key, we recommend 1 Site account holders to not register Toolset in their development environments. Instead, download the necessary plugins from your Toolset Account page and install them directly, manually on your development site. Register the live, production site to generate a site key bound to the live URL, where you can use the automatic update feature.
I hope this helps and please let me know if you need further assistance.
regards,
Waqar
Hi,
Thanks for the info.
I started by trying to upload the Types plugin via wordpress dashboard bit I got a screen saying "The link you followed has expired."
Any idea what may cause this?
Will uploading via FTP work maybe?
Thanks,
Jacques
Thanks for writing back.
The error "The link you followed has expired." is usually showing when installing themes or plugins from the WordPress admin area and the server's configurations need to be updated.
Here is a details guide on how to fix this:
hidden link
And yes, another alternative is to use FTP access to upload the plugin files:
( ref: hidden link )
My issue is resolved now. Thank you!