[Resolved] Requested options that do not exist - wpml_registered_endpoints
This thread is resolved. Here is a description of the problem and solution.
Problem: You are experiencing an issue with over 200,000 calls to
wpml_registered_endpoints
on your staging site, which uses the same site key as the main site. This high number of requests typically occurs when WPML settings cannot be validated due to the use of a site key intended for a different domain or setup. Solution: To resolve this, create a new site key for your staging environment by visiting the Registered Sites section on your WPML.org account. Follow these steps: 1. Log in to your staging site and navigate to "Plugins > Add New > Commercial". 2. Click "Unregister WPML from this site". 3. Enter the new site key and save the changes. This should reduce the unnecessary requests to the WPML endpoint. We do not recommend setting the value to
false
as it might disrupt WPML's functionality.
If the problem persists after these changes, or if you encounter other issues, please check the related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. If the issue still remains, we recommend opening a new support ticket at WPML support forum for further assistance.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Background of the issue:
I'm trying to solve an issue where I have more than 200,000 calls for wpml_registered_endpoints. My site uses only one language besides the main one (Czech). I use the AAA Optimizer Plugin, which logged these calls. I have the opportunity to create this option with the value false, but I can't tell how that will affect my site.
Symptoms:
Requested options that do not exist - wpml_registered_endpoints. There are more than 200,000 calls logged by the AAA Optimizer Plugin.
Questions:
Are these duplicate calls from WPML?
How will creating the option with value false affect my site?
Reference to our recent chat, meanwhile this ticket is attended by one of my colleagues, please provide temporary access (WP-Admin and FTP), preferably to a test site where the problem has been replicated.
Your next answer will be private, to share this information safely.
Also provide detailed steps to reproduce the issue and links to pages in the admin and on the frontend.
IMPORTANT: Please take a complete backup of the site to avoid data loss. I may need to activate/deactivate plugins also.
I reviewed the entire conversation you had with my colleague Waqas and understand the issue. The high number of requests to `wpml_registered_endpoints` typically occurs when something in WPML is misconfigured—meaning that certain settings cannot be validated by WPML.
When I checked our system, I found that the staging site was recently created from the main site and is currently reusing the site key from the main site. Please note that each WPML key is unique to a specific domain and setup. When a site uses a key intended for another domain or configuration, WPML may struggle to validate settings, which can cause repeated queries or reinitializations, potentially resulting in the high number of logged calls you’re seeing.
If the issue is occurring on the staging site, please create a new site key specifically for the staging environment in the "Registered Sites" section of your WPML.org account. Once you have the new key, follow these steps:
1. Log in to your staging site and navigate to "Plugins > Add New > Commercial".
2. Click "Unregister WPML from this site".
3. Once the previous key is removed, you’ll see a field to enter the new site key. Enter the new key and save the changes.
This will allow the site to use the new key, which should reduce requests to the WPML endpoint. We do not recommend setting the value to `false`, as WPML relies on several API endpoints to ensure the site receives updates and communicates properly with WPML’s servers.
After making these changes, please wait a little while and monitor the situation. If the issue persists, let me know, and I’ll be happy to take a closer look.
I attempted to access the backend, but I received a "Forbidden" error. If there are any restrictions in place, please let me know how to bypass them so I can access the backend and investigate further, if you continue to experience issues after following these steps.
Several factors can impact site speed. If you notice a performance drop after activating WPML, I recommend following the suggestions outlined in the ticket link below.
We have some expert advice on that ticket that could help.
However, if you’re still experiencing issues, it would be best to create a new ticket detailing your findings. This way, we can focus solely on resolving the performance issue, if any. Please note that we address one issue per thread to keep everything organized and clear.
In this thread, let’s concentrate on fixing the API request issue with `wpml_registered_endpoint`. Once you create a new ticket for the performance concern, our supporters will review it and provide guidance on the next steps.
I hope you understand. Please let me know if you need further assistance with the WPML endpoint issue. I’ll be happy to help!
