Bug #35902
closedfatal error in scheduler / Swift mailer
0%
Description
While trying to set up the cronjob for the scheduler, something apparently went wrong resulting in the non-accessibility of the scheduler. Now, when trying to access the scheduler, I always get the following error message:
Fatal error: Call to a member function clearAll() on a non-object in /PATH/TO/TYPO3-SRC/typo3/contrib/swiftmailer/classes/Swift/Mime/SimpleMimeEntity.php on line 800
At line 800 I found this code (TYPO3 Version 4.5.14):
$this->_cache->clearAll($this->_cacheKey);
It is trying to clear the cache at that point, but $this->_cacheKey is empty. As long as this line of code is commented out, it is working again.
There should be a check, whether $this->_cacheKey is empty or not.
Updated by Steve over 12 years ago
I already had the same issue. I cleared the "lastexecution_failure" field in db tx_scheduler_task to get the scheduler back to work.
Updated by Lina Wolf over 12 years ago
UPDATE tx_scheduler_task SET lastexecution_failure = '' also temporarily solves the problem until problem arises again.
Updated by André Steiling over 12 years ago
Check your install tool configuration under $TYPO3_CONF_VARS['MAIL']: In my case missconfigured SMTP settings cause the PHP error. Set the mail transport to "mail" and test again. If it works, something with the further mail configuration theems do be wrong ...
Updated by Philipp Gampe over 12 years ago
This sounds more like a bug in swiftmail itself. Swiftmail is a third party product and TYPO3 will not mess in the code. Please check whether this code as been fixed upstream.
Updated by Christian Kuhn about 12 years ago
- Status changed from New to Resolved
Not an issue with the scheduler itself: If a task send mails or something else, it should have proper error handling on its own (eg. by catching the mailer result and giving proper result values).
Updated by Michael Stucki almost 11 years ago
- Project changed from 739 to TYPO3 Core
- Category changed from scheduler to scheduler
Updated by Gernot Ploiner over 9 years ago
I had the same issue today.
My problem was a missing image in a RTE-Content (bodytext field). It was deleted from the uploads-folder.
After uploading the image again all works fine.