Large pages - what's the limit?

[photon]

I have trouble with a couple of pages that seem to be too large for CMSMS - the code just gets cut off at the end.

What's the limit - characters or lines or what? One page is about 57600 characters with spaces, and 1645 lines...

Any modifications I can make myself, or is it just not recommended to have large pages in CMSMS?

[bertmelis]

I don't know in what type the data is stored in the database. But think of this: If your page is really large, why don't you cut it in pieces?

You'll end up with a story that is spread over several pages, which is -my opinion- better to read. I prefer clicking a few times more than scrolling all the way down.

[tsw]

db has type text so it shouldnt limit (well it does, but its somewhere around 2GB or so

apache could also have limit for post size (by default its 10mb or something)

havent tested though

[Einstein]

I having the same problem on my sports club site. Publishing a startlist with over 300 row won't go. Cutting some blank rows out but still there is content left out.  Preview does show all content, but after saving the content is lost.

Anyone having a solution to this?

[tsw]

it seems that mysql text field has a limit of 65k and it will silently truncate data to that length...

UNTESTED:
but you could try changing that field to longtext

Code: Select all

ALTER TABLE cms_content_props CHANGE content LONGTEXT;

PLEASE do backup first.

(longtext limit is around 4gb)

[Russ]

I tried altering the field - no luck. In Firefox on mac I get "Unresponsive Script" when I try to save large content ??
I then can't save a new page at all - "No content message"

This is not very good if you want big pages. Not sure why longtext doesn't work? Anyone any ideas?

Russ

[tsw]

I had some errors when doing larger content on my test server. php couldnt allocate enough memory. check if you get any errors in your logs

[photon]

Thanks for the suggestions. I solved it (temporarily?) by splitting the text into two content blocks in the template:
{content}
{content block="parttwo"}
This because in my case I prefer scrolling down a large page rather than clicking on (many) smaller pages.