Exceeding Maximum Content Size

[jkowens]

Hello,

I have a very large page I am trying to save in SteerCMS. The content
exceeds 65K characters so I had to change the field
steercms_core_node_public_il8n.body from text to mediumtext. I can
edit and preview the page just fine, but when I navigate to the actual
page on the frontend the body content is still truncated at around 65K
characters.

Any Ideas?

BTW I am using the sandbox version of SteerCMS.

Thanks,
Jordan

[jkowens]

Ok, after more investigation I see that my content is saved in its
entirety in steercms_core_node_il8n.body, but it's being truncated in
steercms_core_node_public_il8n.body. Both are now defined as type
mediumtext. Would there be something in the publishing code that
limits the size of content?

[jkowens]

Well I have now updated the Propel schema for the tables
steercms_core_node_il8n and steercms_core_node_public_il8n
to define body as a CLOB and rebuilt the model.

I can manually insert data into steercms_core_node_public_il8n.body
that is > 65K bytes, and it displays correctly on the frontend.
However the act of publishing a page still seems to truncate data at
65,000 bytes.

I'm running out of ideas, I really would appreciate any suggestions!

Thanks,
Jordan

> > Jordan- Hide quoted text -
>
> - Show quoted text -

[jkowens]

If this helps I'm using Symfony 1.0.11, PHP 5.2.5, and MySQL 5.0.45...

> > - Show quoted text -- Hide quoted text -

[Jordan Owens]

I have finally resolved this issue. If anyone is interested I
discovered that the field attribute_value in the table
resource_attribute_version also needed to be
redefined as mediumtext. It appears that the propel mappings can
remain longvarchar and do not need to be changed to clob.