Has anybody had issues from moving metabox data from post to post or database to database? Meta Box Builder is NOT involved.
I'm not sure if this is a server env issue, a MYSQL config issue, or a Metabox issue.
Has anyone else experienced an issue moving the DATA entered into a complex metabox (groups & conditionals), between databases (or even between fields in the same database).
So... we have a complex metabox (including groups & conditionals) that has been filled out on a custom post type. The post type is Exam and the metabox is questions.
In postmeta there is a serialized array with a meta_key of "questions" for a given post_id. Moving the (quite long) meta_value for that post_id/meta_key to another post_id/meta_key doesn't result in the metabox being filled out in the new post (no data).
As an added clue LENGTH(meta_value) and CHARLENGTH(meta_value) between new and old differ... but it's the same table...
I have tried it multiple ways but the only one that works is mysqldump --where post_id =XXX > file.sql and then mysql <file.sql.
The wp export/import also chokes on the serialized array.
I realize this is confusing but I admit I'm confused.
Has anybody had issues from moving metabox data from post to post or database to database?
Thank you for reaching out.
What do you mean "Moving the (quite long) meta_value for that post_id/meta_key to another post_id/meta_key doesn’t result in the metabox being filled out in the new post (no data)"?
I've tested on my local site to copy the meta value from a post ID to another post ID that has the same meta key and it filled out in the new post as well.
Can you please share the code that creates the meta box and some screenshots of the issue? I will re-check it on my end.
Thanks for getting back to me.
The code to generate the metabox is 120+ lines spread over several objects so I won't bore you with that.
If you're interested I will do some further work to consistently reproduce the error and will respond with some metabox code and the serialized array that is the problem. It will be a little while since I am on deadline and have to table this one for the moment.
But it's odd.
never mind... my bad.