Hello,
We apologize for the issues you are facing with the warnings related to the taxonomy in Rank Math. These warnings typically indicate that the plugin is trying to access a property that is not set or is null, which can happen due to various reasons such as misconfiguration or conflicts with other plugins.
To troubleshoot this issue, we recommend the following steps:
- Check for Plugin Conflicts: Deactivate other plugins one by one to see if the issue persists. This can help identify if another plugin is causing the conflict.
- Update Rank Math: Ensure that you are using the latest version of Rank Math. Updates often include bug fixes and improvements.
- Review Taxonomy Settings: Go to the Rank Math settings and check your taxonomy settings to ensure everything is configured correctly.
- Debugging: If you have access to error logs, check them for more details on what might be causing these warnings.
If the problem continues after trying these steps, please reply to this ticket, and a human agent from the Rank Math Support team will assist you further. Thank you for bringing this to our attention!
Hello,
Thank you for contacting us and bringing this issue to our attention.
The warnings you’re encountering seem to be related to a situation where the default WordPress function get_queried_object() is returning “NULL.” This function is essential as it retrieves the current queried object of the page, and Rank Math relies on it for generating metadata and other functionalities.
The issue could be due to a conflict with the taxonomy or query on certain pages (e.g., search results, custom queries). If get_queried_object() returns null, it might be because WordPress is unable to correctly identify the queried object. You can try the following steps:
1. Check Permalinks: Sometimes resetting permalinks can fix issues with incorrect queries. Navigate to Settings > Permalinks and save your settings without changing them.
2. Check if any custom query or taxonomy filters in your theme or plugins are interfering with WordPress’ ability to fetch the queried object.
Let us know how it goes. Looking forward to helping you.
Thank you.
Hello,
In this case, we might need to take a closer look at the settings. Please edit the first post on this ticket and include your WordPress & FTP logins in the designated Sensitive Data section.
Please do take a complete backup of your website before sharing the information with us.
It is completely secure and only our support staff has access to that section. If you want, you can use the below plugin to generate a temporary login URL to your website and share that with us instead:
https://wordpress.org/plugins/temporary-login-without-password/
You can use the above plugin in conjunction with the WP Security Audit Log to monitor what changes our staff might make on your website (if any):
https://wordpress.org/plugins/wp-security-audit-log/
Looking forward to helping you.
Thank you.
Hello,
I have updated the sensitive data as requested. Can you please check further?
Thank you.
Hello,
Those warnings are also appearing from Elementor so there must be a particular page on your website that triggers the function is_tax() but then doesn’t have an object associated with it.
These are usually custom taxonomies from themes or page builders but since that page doesn’t have an ID and it’s not an object, it’s impossible to know exactly on what page those warnings are showing.
It’s important to note that this won’t cause any issues on the website as those are just warnings and not actual errors.
If our developers can do anything to mitigate those in the future, we’ll let you know of the same.
Thank you.
Hello,
Since we did not hear back from you for 15 days, we are assuming that you found the solution. We are closing this support ticket.
If you still need assistance or any other help, please feel free to open a new support ticket, and we will be more than happy to assist.
Thank you.
