http://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692011-07-30T15:43:25ZTYPO3 ForgeTYPO3 Core - Bug #28589: Autoloader Cache is not updatedhttp://forge.typo3.org/issues/28589?journal_id=812892011-07-30T15:43:25ZMr. Hudson
<ul></ul><p>Patch set 1 of change I4fa47178016925f39ff2168f65afb1ae357be556 has been pushed to the review server.<br />It is available at <a class="external" href="http://review.typo3.org/3903">http://review.typo3.org/3903</a></p> TYPO3 Core - Bug #28589: Autoloader Cache is not updatedhttp://forge.typo3.org/issues/28589?journal_id=813512011-07-30T22:15:01ZChristian Kuhnlolli@schwarzbu.ch
<ul></ul><p>@Oliver: I'd strongly recommend to abandon this change set.</p>
<p>I've instead now pushed <a class="external" href="https://review.typo3.org/#change,3911">https://review.typo3.org/#change,3911</a> 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 ...</p>
<p>I've also documented this switch in the caching framework documentation at <a class="external" href="http://wiki.typo3.org/Caching_framework">http://wiki.typo3.org/Caching_framework</a></p> TYPO3 Core - Bug #28589: Autoloader Cache is not updatedhttp://forge.typo3.org/issues/28589?journal_id=814342011-07-31T09:43:34ZOliver Haderoliver.hader@typo3.org
<ul></ul><p>Hey Christian,</p>
<p>I know that each check (and file system operation) on each request slows down the scenario. So, see it as a draft...</p>
<p>We should however still consider these stories:</p>
1) "As developer I want to test the feature at <a class="external" href="https://review.typo3.org/#change,3359">https://review.typo3.org/#change,3359</a> which add a new class file to TYPO3" <br />-> seems to be okay, since most developers should be able to handle that
<ul>
<li>either set the NullBackend</li>
<li>delete files in typo3temp/cache/<br />Suggestion: Since we already have the hardcoded context "production" we could move that to config_default as all - and hard "development"</li>
</ul>
<p>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" <br />-> probably the system is running in production mode and new classes in the next TYPO3 version will stop the system from working<br />Suggestion: Add TYPO3 version number to cache identifier</p>
Summary:
<ul>
<li>drop my MD5_file() stuff in the recent patch</li>
<li>introduce context mode to TYPO3 - production/development</li>
<li>add TYPO3 version number to identifiers of system wide caches</li>
</ul> TYPO3 Core - Bug #28589: Autoloader Cache is not updatedhttp://forge.typo3.org/issues/28589?journal_id=816432011-08-01T18:23:01ZBjörn Pedersenbjoern.pedersen@frm2.tum.de
<ul></ul><p>Hi,</p>
<p>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...).<br /> 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). <br /> This way, we don't need a version number anymore.</p> TYPO3 Core - Bug #28589: Autoloader Cache is not updatedhttp://forge.typo3.org/issues/28589?journal_id=835842011-08-18T21:20:38ZMr. Hudson
<ul></ul><p>Patch set 2 of change I4fa47178016925f39ff2168f65afb1ae357be556 has been pushed to the review server.<br />It is available at <a class="external" href="http://review.typo3.org/3903">http://review.typo3.org/3903</a></p> TYPO3 Core - Bug #28589: Autoloader Cache is not updatedhttp://forge.typo3.org/issues/28589?journal_id=835862011-08-18T22:18:47ZChristian Kuhnlolli@schwarzbu.ch
<ul></ul><p>@Oliver:</p>
<p>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).</p>
<p>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.</p>
<p>Imho the current patch set should do for 4.6, we can ease the development issues with a later version.</p> TYPO3 Core - Bug #28589: Autoloader Cache is not updatedhttp://forge.typo3.org/issues/28589?journal_id=836692011-08-20T10:48:23ZMr. Hudson
<ul></ul><p>Patch set 3 of change I4fa47178016925f39ff2168f65afb1ae357be556 has been pushed to the review server.<br />It is available at <a class="external" href="http://review.typo3.org/3903">http://review.typo3.org/3903</a></p> TYPO3 Core - Bug #28589: Autoloader Cache is not updatedhttp://forge.typo3.org/issues/28589?journal_id=836702011-08-20T11:00:28ZOliver Haderoliver.hader@typo3.org
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li><li><strong>% Done</strong> changed from <i>0</i> to <i>100</i></li></ul><p>Applied in changeset <a class="changeset" title="[BUGFIX] Autoloader Cache is not updated The patch adds the current TYPO3 version to the cache i..." href="http://forge.typo3.org/projects/typo3cms-core/repository/1749/revisions/683083926e9c9ccb0254995b081ac8bba20ec321">683083926e9c9ccb0254995b081ac8bba20ec321</a>.</p> TYPO3 Core - Bug #28589: Autoloader Cache is not updatedhttp://forge.typo3.org/issues/28589?journal_id=3851852018-10-02T12:20:53ZBenni Mackbenni@typo3.org
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li></ul>