Unfortunately this is a having-your-cake-and-eating-it kind of problem.
To allow WordPress SEO to work with the Shopp product editor we basically need to trick it into thinking the regular post editor has been loaded. Unfortunately, a plugin such as ACF suffers from this approach.
It’s possible we could fix this all up however I fear it’s the wrong approach. Really we need other plugin authors/vendors to use an alternative approach to integrate with Shopp (especially WordPress SEO!) and I’d encourage you to make your voice heard through their support channels.
And what could I do if nobody cares about my problem. Should I switch on and off your plugin all the time when I want to fill the SEO meta and the ACF fields?
Well, personally I wouldn’t really see that as a viable option but I guess you could toggle them on and off if you wanted to.
Why don’t you switch to an SEO plugin that does work with Shopp?
Unfortunatly Shopp doeasn’t together work with any other SEO plugin. :-/ So I am grateful to you for developing SEO Glue. I would be very happy if you would find a fix for this problem. Somewhere I found in Google that ACF fail to display fields when there is a javascript error. Maybe ACF and SEO Glue cause javascript error when they are running together.
All in One SEO Pack works well enough in my experience, it depends what you need really.
I would be very happy if you would find a fix for this problem. Somewhere I found in Google that ACF fail to display fields when there is a javascript error. Maybe ACF and SEO Glue cause javascript error when they are running together.
I don’t think it’s a Javascript issue.
Both WPSEO and ACF inspect the $pagenow global set by WordPress and check it’s value before rendering their metaboxes. Part of what my plugin does is change that just in time to make WPSEO think a regular post editor is being used and, unfortunately, that means ACF (which is designed to work with Shopp) is also “tricked” and doesn’t realise that the product editor is being requested.
Very likely this could be worked around, perhaps by resetting the $pagenow variable at some point in the request, but this would require me to spend time on something that A) I no longer use myself and B) no one wishes to actually contribute to or support, directly or indirectly.
Marking this as resolved for the time being.
I’ll certainly file it away as an area for improvement, it could also (potentially) solve an issue with the Genesis Framework that shows up in certain circumstances.
Great news: lkoudal has identified that the $pagenow issue can be trivially fixed, so expect a new version very soon.
It’s really great news! 🙂 I am waiting for the new version. 🙂
Thank you very much for the All in One SEO Pack tip.
1.3 is available to download so feel free to take it for a spin (unless you’re hapy ywith AISEOP, naturally!).
