Hi Ernest … appreciate the honest quick reply 🙂
I understand the balance between compatibility and usability … the reason it has come up is it is the only plugin of dozens that we use which comes up with errors like this in Safari and Chrome Web Inspect … it just makes stakeholders a little nervous about Google indexing, penalties, backwards compatibility etc. It will just have to be factored in for any future projects / purchases
Just one more item I have come across … I have added the latest version of the plugin to a local test setup (which ran the previous version) … We have a custom post type which is now not showing in the search results (it did previously) nothing has changed in the settings … and the custom post type is flagged to be searched in the settings.
Is there anything I can check which could be causing the issue?
Many thanks again