Translate
We are not aware of character limitations on metadata fields except for fields like title or description where the limit is 255 chars
If there is indeed an issue with limits please report an SRQ
Below is the history of changes to this idea's status. Return to the idea.
We are not aware of character limitations on metadata fields except for fields like title or description where the limit is 255 chars
If there is indeed an issue with limits please report an SRQ
I'll need some technical context on where the Metadata restriction occurs--is that in the Content Manager or in Content Delivery? Are users prevented from saving or is there an issue during publishing and rendering? Update: this might be a size limit with Content Delivery using Oracle, but more details appreciated "from the field."
I believe systems should try to prevent issues up front as much as possible, though sometimes things are less "real time" than desired for performance (e.g. when resolving or validation takes to long).
I'm also curious about the use case. What kind of content are you storing in the Metadata tab (is this for Components) and is this in the Metadata tab because of the type of fields (e.g. they're for more technical users or should be hidden from the General tab)? Are these fields queried against in delivery?
I'll need some technical context on where the Metadata restriction occurs--is that in the Content Manager or in Content Delivery? Are users prevented from saving or is there an issue during publishing and rendering?
I believe systems should try to prevent issues up front as much as possible, though sometimes things are less "real time" than desired for performance (e.g. when resolving or validation takes to long).
I'm also curious about the use case. What kind of content are you storing in the Metadata tab (is this for Components) and is this in the Metadata tab because of the type of content? Or is it possibly queried against in delivery?
