netPhotoGraphics / netPhotoGraphics

The netPhotoGraphics media content management project
https://netPhotoGraphics.org
Other
24 stars 13 forks source link

Pages: Large content won't display in admin/frontend but is in database #206

Closed Quy closed 9 years ago

Quy commented 9 years ago

A page with 28,000 characters adds/displays fine in ZP1.4.6, but not in ZP2.0. Content was copied/pasted into the Content field. The content is saved in the database but won't display in the Contents field in admin and frontend. Tested with TinyMCE enabled/disabled.

sbillard commented 9 years ago

I will probably need more details. What theme are you using? Are there any error messages in either the zenphoto logs or the server logs? I suppose that smaller content does display so maybe this is a problem with the size of the content.

Is the content just text or are there embedded pictures, etc. From where was the content copied?

Quy commented 9 years ago

ZenPage, No errors in both logs. Yes smaller content (up to 1,286 characters) is fine. Content is plain text. No pictures. Copied from EditPad. I installed ZP1.4.6 on the same server to test out this issue. It had no problem with the large content.

Tested in Firefox, Chrome 38

sbillard commented 9 years ago

Can you provide a link to the page?

sbillard commented 9 years ago

I have tried to reproduce this, see http://testalbum-2.sbillard.org/zenphoto/pages/Large-lroem

All works for me. Have you switched themes to be sure you theme is not truncating the text?

sbillard commented 9 years ago

And an even bigger one: http://testalbum-2.sbillard.org/zenphoto/pages/Huge-lorem

So the problem is somehow unique to your server/situation. Maybe you can experiment to find what the limit might be. Could be a clue. Also look in the database to see if the full text is there so we can try to home in on where the problem is occurring.

Quy commented 9 years ago

The full text is in the database. It is okay when I copied an old report. I will research further to see what is unique about this new content and report back. Thank you!

Quy commented 9 years ago

OK. The database had a different collation (lantin1_swedish_ci). Changed to utf8_unicode_ci and it is working beautifully. Sorry for the false alarm.

sbillard commented 9 years ago

No problem. That would have been my next suggestion to check.