TYPO3 Core

Patch set 1 of change I4fa47178016925f39ff2168f65afb1ae357be556 has been pushed to the review server.
It is available at http://review.typo3.org/3903

@Oliver: I'd strongly recommend to abandon this change set.

I've instead now pushed https://review.typo3.org/#change,3911 The patch enables usage of the NullBackend for the phpcode cache to easy development on a dev system. This is also very useful for the new language cache ...

I've also documented this switch in the caching framework documentation at http://wiki.typo3.org/Caching_framework

Hey Christian,

I know that each check (and file system operation) on each request slows down the scenario. So, see it as a draft...

We should however still consider these stories:

• either set the NullBackend
• delete files in typo3temp/cache/
  Suggestion: Since we already have the hardcoded context "production" we could move that to config_default as all - and hard "development"

2) "As TYPO3 integrator and editor I want to check out the most recent version of TYPO3 and upgraded locally from TYPO3 4.6.0 to 4.7.0alpha2"
-> probably the system is running in production mode and new classes in the next TYPO3 version will stop the system from working
Suggestion: Add TYPO3 version number to cache identifier

• drop my MD5_file() stuff in the recent patch
• introduce context mode to TYPO3 - production/development
• add TYPO3 version number to identifiers of system wide caches

Hi,

Story 2) could be taken care of by the upgrade wizard in the install tool, as this wizard is needed on major version upgrades anyway ( DB schema changes...).
so: add a clear all (low-level) caches to the install tool ( should also clear e.g. the RTE cache and the temp_cached_ files).
This way, we don't need a version number anymore.

Patch set 2 of change I4fa47178016925f39ff2168f65afb1ae357be556 has been pushed to the review server.
It is available at http://review.typo3.org/3903

@Oliver:

Your suggestions are great! Actually, I introduced the TYPO3_version addition to the identifier before I read you post of this issue again (see latest patch version in gerrit).

And yes, we are on the same track with the production / development context thing, but I think we need a broader implementation and interface for this (I'd love to have it!). We are currently beyond 4.6 feature freeze, so a solid implementation will not make it for 4.6 anymore. For 4.7 we have plans for a better bootstrap, and this one could possibly consider a context as well. So, I'd like to shift the context thing a bit and maybe work on it for a later version, the caching framework even has methods for it.

Imho the current patch set should do for 4.6, we can ease the development issues with a later version.

Patch set 3 of change I4fa47178016925f39ff2168f65afb1ae357be556 has been pushed to the review server.
It is available at http://review.typo3.org/3903