Incredibly long metadata .. Is it ok?

Is it ok with to have a really long string inside a single meta key on a post? I am talking about a heavy array inside a simple string..

Or should i look into multiple meta values in the same meta key?

should be ok. my framework saves the whole theme options array into one field, I have tested it while I was building it, there were no performance differences compared to multiple fields.

As far as I know all of the meta information (keywords, description, others) must be no more than 256 characters, no matter if you are on homepage or post page. The more concise the better.

If you are talking about incredibly long keywords they could be used when makes sense as a whole and ONLY if they are related to the page content. EG: [one way street] or [all round lenses]

Technically yes, you can use them. I’ve never encounter any limitation.

Wordpress, right?
From what I know, meta values are the same type as post_content fields – mysql longtext – stuff that can hold 4gb of data. Pretty big I can say. If you need all the data at once, then a single field can be good.

@dnp 255 characters is for the name of the metakey.

Yes, i am now trying to build my own content composer and wondered if it’s ok to hold the page data(arrays) into a hidden textarea and save that as a meta key..

Are you using a separate panel for content composer or inside edit posts section, I earlier tried adding content composer to edit posts section and it got buggy .. Better to create a separate db table for it, that way you can create lots of templates independent of a theme.

wptitans said
Are you using a separate panel for content composer or inside edit posts section, I earlier tried adding content composer to edit posts section and it got buggy .. Better to create a separate db table for it, that way you can create lots of templates independent of a theme.

I was trying to do it inside the edit posts section..

RubenBristian said
I was trying to do it inside the edit posts section..

For example, you can create AJAX saving/loading of the templates, that way you save users some time as they do not have to recreate a teplate from scratch on each post/page.

And you can save templates as a custom post type that is hidden from the ui.

OriginalEXE said

wptitans said
Are you using a separate panel for content composer or inside edit posts section, I earlier tried adding content composer to edit posts section and it got buggy .. Better to create a separate db table for it, that way you can create lots of templates independent of a theme.

Isn’t it better to create a custom post type then? That way you don’t have to create a separate table for it and you already have all the functions for management you could possibly need.

that way we are back to posts meta, it is a personal choice imo . When you have a template not relating to any post you can re use it any where.
Goto edit post / custom post / page , select template from a drop it insert via shortcode done .