Plugin Support
Jeremy
(@jeremrm)
Hello @alireza9898,
Thank you so much for bringing this to our attention, and we really appreciate you sharing your workaround. Your suggestion is noted and will be reviewed by our development team.
To help us investigate and reproduce the issue accurately, could you please let us know the exact steps you took before the fatal error appeared, and also what type of page or taxonomy you were on when the error occurred? For example, whether it happened on a post, page, product, category, or a custom taxonomy. Having this context will help us dig deeper and ensure the issue is properly addressed.
Looking forward to helping you with this one.
Hello again
It happend in product category page when I press second page button on pagination. I noticed that $advanced_robots variable return null thus this type error occurs .
Plugin Support
Miguel
(@miguelrm)
Hello @alireza9898,
We tried to replicate this with a new installation and we don’t see this error being triggered. Can you please reach out to our developers via the support@rankmath.com email address with the details of your setup and include any custom filter you might be using?
We would love to help you get to the bottom of the issue.
Hello again
As I said it happens when $advanced_filter variable’s value gets null somehow. Maybe there’s other plugin that affects this variable’s value. It was a temporary client and I don’t access to website anymore. I think a simple null checking will solve the issue
Plugin Support
Jeremy
(@jeremrm)
Hello @alireza9898,
Based on our review, the issue is likely caused by the + operation failing when a third-party filter returns a non-array value. The frontend/advanced_robots filter allows other plugins or custom code to modify the robots array, so if that filter returns null or anything other than an array, this error can occur.
Since we’re unable to reproduce the issue in a clean environment and it seems to be caused by an external filter returning an unexpected value, we won’t be adding this change to the plugin at this time.
If you encounter the issue again or can reproduce it in another setup, please feel free to reach out and we’ll be glad to investigate further.
We appreciate your time.