Thread

Hi!

I have a few entries that are very long and the text is truncated within the editor. I hesitate to set the character limit in the database higher because I expect disadvantages (space, speed). Is that true?

I can split the article into several parts. What is the best way to do that?

Just how long (number of characters) is very long?

Ingmar,

I have no character count available but the size has to be 2-3 times larger then currently possible.

I prefere to split the page anyway. Any pointers?

Peter,

Take a look at
_EE Docs : Spanning a Channel Entry Across Multiple Pages

Or just create as many separate custom fields as you would like something like {body}, {body_extended} etc
hey can just go after each other in your template then. If they aren’t filled in then they just won’t show.

Does that help?

John,

multi-fields do not help here. And adding fields is a bit too fat, isn’t it?

Never mind! I had hoped for a known better solution but I probably can use hidden subcategories.

Peter,

And adding fields is a bit too fat, isn’t it?

Remember you can hide them by default in their settings

So leave the firs ton unhidden and hide the others until they are needed. Then just click the + to open them out

Remember you can hide them by default in their settings

Hmmm, haven’t thought of this. The problem with this approach is that the list of fields becomes quite long (title, url-title, summary, text, text-1, ...). Unfortuanatly the visible fields and the headlines appear after each submit and the user has to scroll down and expand the hidden fields again.

It would be good if the the publish page remains open after each submit. Something like “submit” and “submit and finish” like on other places.

Anyway, thanks John, I’ll think about it…

Hi, Peter. Feel free to make a Feature Request or find an existing one and add your comment.

One other thing you could consider doing is to have a separate field for longer articles, and only use that field when needed. Then you’d check for that field when displaying the entry.

Might that work for you?

Hi, Peter. Feel free to make a Feature Request or find an existing one and add your comment.

Sue, I feared that this will will be suggested. 😉 Seriously: I think the CP needs and will have a general overhaul. That is a minor annoyance…

One other thing you could consider doing is to have a separate field for longer articles, and only use that field when needed. Then you’d check for that field when displaying the entry.

Might that work for you?

May be. I’ll check it out. Ccurrently I consider to reorganize the site a bit to adhere better to some requirements.

Thanks for the hint!

Peter

Unfortunately I see no other options here, if you want to cram more content into a single field, as it were, changing the field type in the backend would be the way to go.

I’ll go with a second field. After a bit of reorganisation (all custom fields closed) this seem to work well.

Thanks for help!

Peter

Glad to help. Feel free to start a new thread if you have any more questions.