Loading...

XML

Word

Printable

Details

Type: Improvement
Resolution: Obsolete
Priority: High
Fix Version/s: None
Affects Version/s: 4.2.0
Component/s: Cronjobs, Legacy > Administration Interface
Labels:
None

Description

This is a placeholder for issues/enhancement suggestions that involves moving or offering the execution of an operation to cron, in order to avoid timeouts when executed via web.

Examples of operations that can time out when involving a lot of data (i.e. contentobjects):

empty trash
add contentclass attributes
move subtree
copy subtree
remove subtree

The implementation of a solution could be based on the eZ Script Monitor extension:
http://projects.ez.no/ezscriptmonitor

Attachments

Issue Links

relates to

EZP-10203 Changing classes with a lot of objects can result in a maximum execution time error

Closed

EZP-10687 "Empty trash" always fail on huge number of objects : potential PHP_TIME_LIMIT or InnoDB deadlocks problems *can* be circumvented

Closed

EZP-13837 Hide/Unhide will cause heavy database traffic in cluster mode

Closed

EZP-12490 let session clean up in admin interface work without grinding db to a halt

Closed

EZP-10827 Adding a CLI trash purge script

Closed

EZP-13855 Defer view cache handling to cron

Closed

EZP-16833 Package import/export in browser may time out, should be moved to cron

Closed

EZP-25514 SupportTools M1

Closed

(3 relates to)

Activity

People

Assignee:: unknown

Reporter:: jkn

Votes:: 0 Vote for this issue

Watchers:: 0 Start watching this issue

Dates

Created:: 04/Nov/09 4:57 PM

Updated:: 07/Mar/16 4:23 PM