Details
-
Bug
-
Resolution: Fixed
-
Medium
-
3.6.11, 3.7.9, 3.8.6, 3.9.0
-
None
Description
Changing classes with a lot of objects can result in a maximum execution time error, leaving your content objects inconsistent with your content class definition.
Please do not replace existing class with it's temporary version when too many objects exist of it (specify a limit in an INI file) and instruct to run a script like http://ez.no/community/contribs/hacks/update_class_from_command_line instead.
This is similar to what has been done for the removal of nodes with too many children.
Attachments
Issue Links
- is duplicated by
-
EZP-11350 contents objects are not updated after chaginf attributes of class if there are thousands of nodes
- Closed
-
EZP-15304 Problems with adding attributes in large classes
- Closed
-
EZP-12706 adding an attribute on content classes with many existing objects causes php timeout
- Closed
- relates to
-
EZP-14133 Batch initialization of object attributes
- Closed
-
EZP-16133 Putting the logic of content objects modifications in a handler when content class get modified
- Closed
-
EZP-14307 Script for adding missing object attributes [patch]
- Closed
-
EZP-15753 [placeholder] operations that should be deferred to cron
- Closed
-
EZP-13855 Defer view cache handling to cron
- Closed