Character Max set at 4000

Generally speaking, you want to use the standard "body" field for the largest chunk of HTML in a Content Type. (The standard "body" field is not limited in length, but all custom properties are limited to around 4K characters.) For a Blog Post, that would likely be the body of the post. If you've already defined your Blog Content Type with a custom "blog_body" property, then I'd suggest you take the following steps to get yourself where you want to be:

1. For each Blog instance, copy the contents of the custom "blog_body" property to the standard "body" field. If you have a large number of Blog Posts, you might want to try using the CSV Download/Upload tools to accomplish this task. If you have a dozen or fewer, it may be simpler to do it manually one-by-one.
2. Update your Blog display templates to use "body" instead of "blog_body".
3. Verify that your updated templates render the content properly
4. Update the Blog Content Type and remove the no-longer-needed "blog_body" property. This will delete the data so make sure that you really fixed the templates and verified everything in steps 2 and 3

Rachel Hassinger:

Hi Bruce and Bill,

How would you set the code in a list template to limit the characters of a content type field?

- Rachel

Rachel Hassinger

Join Together

http://www.JoinTogether.org

Rachel, check out the in particular, the bits on local variables and strings.You can do something like this:

<t:set id="truncatedCustomProperty" value="truncate(your_custom_property,250)" />
<t:value id="truncatedCustomProperty">the truncated text will appear here!</t:value>

If you don't want the trailing ellipsis that truncate gives you, you can remove them using the replace method.