Problem:
The REST API is one way that WordPress and other applications communicate with the server. For example, the block editor screen relies on the REST API to display and save your posts and pages.
Solution:
I checked that the customer's site has Cloudfare CDN on.
I found a similar case where the culprit of this issue was Cloudfare firewall blocking wp-json/wp/v2 requests.
Problem:
Customer wanted to check the current versions of Toolset and how is the process of updating/keeping it up-to-date Solution:
I referred him to our downloads page and sent a list with all Toolset plugins current version. I also explained how to update manually and via plugins page:
For you to check if there are updates available you can go to wp-admin > dashboard > updates or wp-admin > plugins > add new > commercial tab.
Please make sure to refresh the results by clicking on check again. If there are any updates available, they'll be listed in there and you'll be able to proceed to the update.
Alternatively, you can upgrade Toolset plugins manually by following this procedure:
1) Backup your website database
2) Deactivate/delete old version of Toolset Types plugin
3) Download the latest version of Types plugin here: https://toolset.com/account/downloads/
click link "Download Toolset manually"
4) Upload/activate Types plugin in your website manually
Problem:
Customer was getting the error 'Unable to register: site key not matching' while trying to update the WPML plugins.
Solution:
If you have this issue, follow the steps below to re-register Toolset to be able to update Toolset as it seems for some reason the key you use is not valid:
- Make sure that you are logged in toolset.com.
- Go to "WordPress Dashboard > Plugins > Add New > Commercial (Tab)".
- Click the "Unregister Toolset" link.
- Click the "Register Toolset" at the right section of the screen.
- Click the "Get a key for this site" link .
- A new page will open up and the auto-generated key will show in pop-up.
- Copy the key and paste it into the "Site Key" input box annotated in the screenshot below.
- Click the "OK" button.
- Go to wp-admin > Dashboard -> Updates
- Click on check again
Problem:
When the latest version of the Toolset Types plugin is activated, it becomes impossible to activate any other plugin, although deactivating them is still feasible. Additionally, installing new plugins also becomes unfeasible.
Solution:
I checked it and the issue is fixed if we install the latest OTGS Installer Version 3.1.1.
There are some dependencies needed in Toolset that are fixed in this plugin's new version.
I installed it and then updated the Toolset plugins. I tested it and I'm no longer able to replicate the issue.
For the time being, in order for you to apply this fix in the live as well, I uploaded the latest version of the installer plugin to your webroot, you can connect to it via FTP and download the zip file or download directly in the private link I sent you above.
Then, proceed to manually installing it and update the Toolset plugins afterwards.
Problem:
I am trying to get rid of this message - not sure what to do. My site is registered. Solution:
Hi thank you Mateus! I had tried your Workflow a couple of times but I think this was what I was missing:
>(please make sure to enter the exact URL that appears in the url fields in the WP dashboard -> Settings -> General page)
Also for future readers - I suspect the problem was caused by "renaming" the site (assigning new domain/SSL/etc) while using the same database and db configurations as the old site.
Problem:
Install toolset onto a new site for development - php 8.2 is installed. Will this need rolling back to an older version?
Is there any documentation that you are following?
Reading installation requirements and support tickets. Support tickets seem to suggest php 8.2 will work. Installation documentation say use version 8.0.x
Solution:
As of now, we have not yet conducted a full-scale review for compatibility with PHP 8.2.
Toolset is confirmed to work seamlessly with PHP 8.0 and 8.1. For PHP 8.2, we've been actively addressing any concerns raised by our clients. So far, these have been mostly minor and often related to PHP deprecation notices appearing in the logs, as only a limited number of clients are using PHP 8.2 at the moment.
Upon reviewing our internal tickets, I didn't find any major issues specifically tied to PHP 8.2. If you do decide to maintain this version and encounter any issues, please don't hesitate to report them. We will make it a priority to resolve them promptly.
