Bug #21020
closedrecycler can't delete INITIAL PLACEHOLDER
0%
Description
Records from tt_content where the field t3ver_label has the value "INITIAL PLACEHOLDER" can't be deleted and give the following error upon delete:
ERROR:
Fatal error: Uncaught exception 'InvalidArgumentException' with message '"pageId_-1" is not a valid tag for a cache entry.' in /var/www/sites/sources/typo3_src-4.3.0alpha3/t3lib/cache/frontend/class.t3lib_cache_frontend_abstractfrontend.php:143 Stack trace: #0 /var/www/sites/sources/typo3_src-4.3.0alpha3/t3lib/class.t3lib_tcemain.php(7031): t3lib_cache_frontend_AbstractFrontend->flushByTag('pageId_-1') #1 /var/www/sites/sources/typo3_src-4.3.0alpha3/t3lib/class.t3lib_tcemain.php(4001): t3lib_TCEmain->clear_cache('tt_content', 373) #2 /var/www/sites/sources/typo3_src-4.3.0alpha3/t3lib/class.t3lib_tcemain.php(3958): t3lib_TCEmain->deleteRecord('tt_content', '373', true, true) #3 /var/www/sites/sources/typo3_src-4.3.0alpha3/t3lib/class.t3lib_tcemain.php(3937): t3lib_TCEmain->deleteVersionsForRecord('tt_content', 372, true) #4 /var/www/sites/sources/typo3_src-4.3.0alpha3/typo3/sysext/recycler/classes/model/class.tx_recycler_model_deletedRecords.php(341): t3lib_TCEmain->deleteEl('tt_content', 372, true, true) #5 /var/www/sites in /var/www/sites/sources/typo3_src-4.3.0alpha3/t3lib/cache/frontend/class.t3lib_cache_frontend_abstractfrontend.php on line 143
The only way to delete them is through phpmyadmin.
(issue imported from #M11907)
Updated by Rupert Germann about 15 years ago
hi ben,
this bug seems to be a duplicate of bug #20218
fixed by Steffen K in rev 5567
(which was committed after release of alpha3)
updating to latest trunk should fix the problem
Updated by Oliver Hader about 15 years ago
This bug should not be valid anymore:
1) the separator in the caching framework was changed from "-" to "@"
2) the caching framework is not used by default since TYPO3 4.3-beta1
Updated by Oliver Hader about 15 years ago
Closing this issue since it should be fixed.
If the problem still occurs with the current trunk or TYPO3 4.3-beta1, please reopen this issue.