Bug #80054
closed
Toolbar: Clear Cache forward to URL (Blank Page)
0%
Description
If you click clear cache in the Toolbar, as Admin, you will be forward to an empty Page with URL:
/typo3/index.php?route=%2Frecord%2Fcommit&token=XXX&cacheCmd=all or /typo3/index.php?route=%2Frecord%2Fcommit&token=XXX&cacheCmd=pages
and don't get back to the TYPO3-Backend.
TYPO3-Version: 8-master
Updated by Christian Kuhn over 7 years ago
- Status changed from New to Needs Feedback
You mean the browser tab loads this url?
Not confirmed (and I'd guess such an issue would have popped up much earlier already). Are you sure you're dealing with current JS and current composer dependencies?
Updated by Wouter Wolters over 7 years ago
Can't reproduce with current master too.
Updated by Kai Ole Hartwig over 7 years ago
Christian Kuhn wrote:
You mean the browser tab loads this url?
Yes.
Not confirmed (and I'd guess such an issue would have popped up much earlier already). Are you sure you're dealing with current JS and current composer dependencies?
I have reload the current master, deleted all caches and still have this issue - on different installations and systems.
Updated by Riccardo De Contardi over 7 years ago
I am not able to reprouce it, too.
Are you sure you're dealing with current JS and current composer dependencies?
@Kai Unterberg Ole Hartwig:
did you try to perform a composer install ?
I would also try to delete the browser cache, too.
Updated by Kai Ole Hartwig over 7 years ago
Riccardo De Contardi wrote:
did you try to perform a
composer install?
Yes, i have make:
composer update composer install
- server restart
- clear browser caches, delete typo3temp
So, I think that i have hopefully the latest master.
Updated by Riccardo De Contardi over 7 years ago
- Status changed from Needs Feedback to New
have no clue right now....
Updated by Kai Ole Hartwig over 7 years ago
Since the 8LTS Release its no longer reproducible.
Updated by Riccardo De Contardi over 7 years ago
- Status changed from New to Closed
Ok thank you very much for your testing :)
I close this as resolved, then.
If you experience the issue again then please reopen it or open a new issue with a reference to this one. Thank you again!