Migrate Beans term-meta from options table to termmeta table
WordPress 4.4 introduced term meta and a termmeta DB table in Core at the end of 2015: https://codex.wordpress.org/Version_4.4 https://make.wordpress.org/core/2015/09/04/taxonomy-term-metadata-proposal/ https://make.wordpress.org/core/2015/09/22/preparing-your-plugins-and-your-client-sites-for-termmeta/ https://make.wordpress.org/core/2015/10/23/4-4-taxonomy-roundup/
It would be great if we could migrate Beans term-meta from the options table to the termmeta table.
Related: https://make.wordpress.org/core/2018/07/27/registering-metadata-in-4-9-8/
So that would require to rewrite the term-meta API and to offer a migration path.
So rather rewrite the database or offer a fall back for old term-meta or rewrite term-metas on the go?
From my point of view: whatever is offered by the core should be used from the core. And that will be some work.
@ibes
So that would require to rewrite the term-meta API and to offer a migration path.
Yes, I would say so. Rewrite custom Beans functions with WP Core equivalents and/or throw deprecated notices for old Beans functions and run new functions...
So rather rewrite the database or offer a fall back for old term-meta or rewrite term-metas on the go?
Ideally, we'd run a migration script/function moving the options to termmeta.
From my point of view: whatever is offered by the core should be used from the core. And that will be some work.
👍