Details
-
Bug
-
Resolution: Unresolved
-
High
-
2.5.9, 3.3.1, 3.2.5
-
None
Description
Using the same Schedule Block in a Landing Page, that gets updated frequently will eventually result in SQL Exception (please see: EZEE-3003), as JSON for "event" field is never truncated.
Steps to reproduce
1. Clean installation of eZ Platform EE 2.5.9
2. At the Content Root create 3 Folders: Folder 1, Folder 2 and Folder 3.
3. Edit Home Landing Page: place a "Schedule Block".
4. Add all 3 folders to the "Schedule Block". Publish page.
5. Open the eZ Platform database in the preferred app and select all rows from ezpage_attributes. With Id 5 there will be a row with name "events". The value of this row "value" column will be a JSON string with a length of 772 bytes.
6. Edit Home Landing Page again: remove all folders from "Schedule Block". Publish page.
7. Open the eZ Platform database in the preferred app and select all rows from ezpage_attributes. With Id 19 there will be a row with name "events". The value of this row "value" column will be a JSON string with a length of 1207 bytes (almost twice as long as in previous version).
8. Repeat steps 4 and 6 a couple of times.
9. Check the database again.
Result
The "event" attribute value will increase gradually to infinity and beyond. Or until EZEE-3003 occurs due to the max length of TEXT fields in the SQL database.
Expected Result
The "event" attribute value is truncated out of unnecessary data, so it stays as short as possible.
Attachments
Issue Links
- relates to
-
EZEE-3003 Publishing a very big Landing Page will result in SQL Exception
- QA