Bug #57032
closed
Context "Development" in installer behaves different than with SetEnv for TYPO3_CONTEXT
Added by Stefan Neufeind over 10 years ago.
Updated over 10 years ago.
Description
If you set via .htaccess:
SetEnv TYPO3_CONTEXT Development
You get a "Flush system caches" in the dropdown in BE. But if you don't set TYPO3_CONTEXT there, the context chosen in the installer should (afaik) behave the same. Setting it to "Development" however does not bring that flush-entry for system-caches.
NEWS.md says:
- "Flush system caches" clears all system-related caches, which is the class
loading cache, configuration cache (previously known as temp_CACHED_* files)
and some other extbase-related class caches. The symbol is now disabled
by default, even for admins, and can be enabled by setting the userTSconfig
option "options.clearCache.system=1", and is also always enabled using
the Application Context / TYPO3_CONTEXT Environment Option "Development".
Additionally, clearing system caches can be done via the Install Tool, they
are automatically flushed when an extension is being activated/uninstalled.
- Category set to Install Tool
- Status changed from New to Needs Feedback
The "Clear all caches" in the install tool is not affected by any setting. Why should it? It's documented in the text that it "hard-codedly" clears all caches (without even going through the caching API itself, in case it is broken). So this is different from the BE toolbar "Flush caches".
Maybe I don't get your suggestion right. Or what is your suggestion anyway? :)
- Status changed from Needs Feedback to New
I think you misunderstood something. Sorry if maybe I wasn't clear. This is not about flushing caches in installtool.
The "context" set via TYPO3_CONTEXT to Development will bring up "Flush system caches" in BE. But choosing the "Development"-context in Installtool instead (which afaik applies if no TYPO3_CONTEXT is set) does not bring up that additional menuitem. Imho both "contexts" are supposed to do the same, right?
- Status changed from New to Needs Feedback
Maybe you misunderstand something in the Install Tool, because there is no way there to set any context. This can only be set in the Apache (or Webserver) environment, as this is defined through an environment variable.
The Install Tool can only configure basic settings, and there are presets of these configuration which happen to be called "Production Settings" and "Development Settings", but this does not affect the "Context" (environment variable) at all.
Might be that the text surrouding these preset configuration is misleading, as they also mention the CONTEXT environment variable, but does not clearly mentions that this Configuration presets have no influence over this.
- Status changed from Needs Feedback to Rejected
Also available in: Atom
PDF
Updated by 
Updated by