Project

General

Profile

Actions

Feature #87670

closed

Really clear all caches

Added by Bernhard Eckl about 5 years ago. Updated about 5 years ago.

Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
Caching
Target version:
-
Start date:
2019-02-07
Due date:
% Done:

0%

Estimated time:
PHP Version:
7.0
Tags:
Complexity:
Sprint Focus:

Description

The clear all caches button can be activated in the install tool and also in the install tool all caches can be cleared. But if I add a new repository in an extension, I have to uninstall and install the extension again to get the repository because of the caching. So why not really clear all caches?


Files

Auswahl_009.png (76.3 KB) Auswahl_009.png Kevin Ditscheid, 2019-02-11 15:34
Actions #1

Updated by Georg Ringer about 5 years ago

  • Status changed from New to Needs Feedback

Better provide autoload information in ext_emconf, see https://docs.typo3.org/typo3cms/CoreApiReference/ExtensionArchitecture/DeclarationFile/Index.html or use composer.

Reason is that this cache is nothing what needs to be cleared if doing stuff in the backend.

Is that enough for you, then I would close the issue

Actions #2

Updated by Bernhard Eckl about 5 years ago

Better provide autoload information in ext_emconf, see https://docs.typo3.org/typo3cms/CoreApiReference/ExtensionArchitecture/DeclarationFile/Index.html or use composer.

How to do that if I add one new file under Classes/Domain/Repository?

How about a button in the install tool „Clear all caches“ and rename the exiting one to „Clear most caches“ (clear all caches should clear all caches, not just most caches, I could have saved hours if I knew that before)?

Actions #3

Updated by Georg Ringer about 5 years ago

provide psr4-information in ext_emconf as described. however for specific support, please ask in slack or stackoverflow.

cache buttons labels won't be renamed .

Actions #4

Updated by Bernhard Eckl about 5 years ago

A second button?

Actions #5

Updated by Markus Pircher about 5 years ago

lately i had a similar problem, (8.7, classic symlink installation), after add new repository, dependency injection not worked for this class. Delete caches not work, also reinstall had no effect. But it works after restarting the PHP FPM service. I using APCu.

Actions #6

Updated by Kevin Ditscheid about 5 years ago

There already is a button in the Maintenance Module in TYPO3 9 that is called "Rebuild PHP Autoload Information" and it is already telling how autoloading is handled (via composer or by TYPO3)

Actions #7

Updated by Georg Ringer about 5 years ago

  • Status changed from Needs Feedback to Rejected
Actions #8

Updated by Bernhard Eckl about 5 years ago

Okay, thank you!

Actions

Also available in: Atom PDF