Bug #4047
closed
There's no error message when adding an event failed
100%
Description
this happens for example when playing with the scheduler while an own event is not fully implemented yet
Updated by Ingo Renner over 15 years ago
the reason was that the class could not be found and thus a fatal error occured, that might be require some check
Updated by Francois Suter over 15 years ago
You mean the class for the event? Indeed it should be checked for.
Updated by Francois Suter over 15 years ago
- Status changed from New to Resolved
- Assignee set to Francois Suter
- % Done changed from 0 to 100
Solved in r1121
I really think the only situation where this happened was when a task was declared, but the corresponding class file did not exist for some reason (does not exist at all, is badly named, exists but is not autoloaded, etc.). The validation added in the patch checks for class existence and issues a proper error message.
Updated by Ingo Renner over 15 years ago
Francois Suter wrote:
I really think the only situation where this happened was when a task was declared, but the corresponding class file did not exist for some reason (does not exist at all, is badly named, exists but is not autoloaded, etc.). The validation added in the patch checks for class existence and issues a proper error message.
should solve the issue I had, thanks
Updated by Francois Suter over 12 years ago
- Status changed from Resolved to Closed
Updated by Michael Stucki almost 11 years ago
- Project changed from 739 to TYPO3 Core
- Category changed from scheduler to scheduler