Open Graph Conflicts (due to being ‘on’ by default)
-
Open graph tags appear to be ‘on’ by default, upon updating OceanWP to the latest version. This may be fine for most folks (who just turn it off), but for those using The SEO Framework (and I don’t know what others) might have an issue.
When the OceanWP Theme updates, it enables OpenGraph tags immediately.
If any pages are loaded between the Theme Update and DISABLING those OpenGraph tags in the Customizer, The SEO Framework detects that there is a conflict (due to another plugin – or in this case, the theme – creating OG tags already).
The SEO Framework seems to be ‘stuck’ thinking that OceanWP is still in conflict with regard to OpenGraph tags already, and there is no resolution. I have submitted this information to Sybre on Github as well.
I would imagine that it be best if either OceanWP have the OpenGraph tags OFF by default, or perhaps when someone goes into the Customizer for the first time since an update – perhaps a Wizard can ask if they want it on.
Most folks with production websites already are using OpenGraph if they are in production, so this update seems to conflict with that, by virtue of having OpenGraph on by default!
Perhaps as well, OceanWP can do a quick detection (by loading the home page and checking for og:title or something) and have the feature turned off by default if they are already detected (with ability to override). Just a suggestion here.
Thank you for all your great work!
Paul
- The topic ‘Open Graph Conflicts (due to being ‘on’ by default)’ is closed to new replies.
