I’m curious if the browser developer console is showing anything for errors that may help with this.
This is just for SEO metaboxes on your term editor screen correct? And you’re uptodate with both plugins and they’re on the latest versions?
Yes, good idea, there are some Yoast errors showing here:
Uncaught TypeError: Cannot read property ‘registerPlugin’ of undefined
at new App (yoast-acf-analysis.js?ver=3.0.1:11)
at initializeYoastACFAnalysis (yoast-acf-analysis.js?ver=3.0.1:409)
It is the metaboxes on the Yoast SEO plugin screen for the particular category, so I see SEO Title, Slug, Meta description, none of which will save.
Having said that, I tried deactivating the YoastACF analysis plugin, but it doesn’t resolve the issue, just takes away the error message on console.
I am also getting the following errors on console:
media-models.min.js?ver=5.8:2 Uncaught TypeError: _.contains is not a function
at Function.r.extend.get (media-models.min.js?ver=5.8:2)
at n._requery (media-models.min.js?ver=5.8:2)
at n._changeQuery (media-models.min.js?ver=5.8:2)
at p (backbone.min.js?ver=1.4.0:2)
at f (backbone.min.js?ver=1.4.0:2)
at c (backbone.min.js?ver=1.4.0:2)
at h.Model.n.trigger (backbone.min.js?ver=1.4.0:2)
at h.Model.set (backbone.min.js?ver=1.4.0:2)
at n.initialize (media-models.min.js?ver=5.8:2)
at n.h.Collection (backbone.min.js?ver=1.4.0:2)
autocomplete.min.js?ver=1.12.1:9 Uncaught TypeError: this._addClass is not a function
at t.<computed>.<computed>._create (autocomplete.min.js?ver=1.12.1:9)
at t.<computed>.<computed>.t.each.t.isFunction.l.<computed> [as _create] (backend.js?ver=5.8:56)
at t.<computed>.<computed>._createWidget (backend.js?ver=5.8:56)
at new t.<computed>.<computed> (backend.js?ver=5.8:56)
at HTMLInputElement.<anonymous> (backend.js?ver=5.8:56)
at Function.each (backend.js?ver=5.8:14)
at k.fn.init.each (backend.js?ver=5.8:14)
at k.fn.init.t.fn.<computed> [as autocomplete] (backend.js?ver=5.8:56)
at i.onPostRender (wp-tinymce.js?ver=49110-20201110:45)
at i.a (wp-tinymce.js?ver=49110-
Can you send me your “Debug info” tab content from the Tools menu? In there I’ll be able to import your post type and taxonomy settings and see if anything looks off there, or if settings may be somehow interfering.
Beyond that, I’m really not sure what to suggest here thus far
I have messaged you in Slack. Many thanks
Not managing to recreate thus far. I’ve imported your post types and taxonomies, and activated Yoast SEO and the premium upgrade as well.
My best hunch is that one of the other plugins may still be interfering somehow, but I don’t know which or how.
Okay thanks for trying, I will try deactivating them one by one and see if it is one of the plugins.
Ah found it. There was a plugin called Custom Post Types created by Andrea De Giovine – I disabled that and the Meta Boxes now work as they should. Not sure why original builder of site had another Custom Post plugin installed. That must have been confusing things. Thanks again Michael.
That one was feeling a bit odd from the list of plugins shared, but didn’t want to touch any more than I had to for debugging. Glad you got it figured out and thanks for the coffee 🙂
Yeah that other plugin is causing me all sorts of other issues it seems. Having issues with the block editor now, unfortunately a whole section of posts has been created using that plugin, and it has no export, so looks like I am going to have to cope and paste everything manually and completely redo, before deactivating it. 🙁
If it’s just creating post types for you, among whatever else it may be also doing, and not storing the post content and whatnot in custom areas, then you should be able to just re-register the same slug and whatnot with CPTUI and inherit everything without content moving. As long as those post type posts and meta are in the appropriate database tables, they should be pretty portable.
