TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692012-03-03T00:49:20ZTYPO3 Forge
Redmine TYPO3 Core - Feature #34476 (Closed): Add hook to t3lib_cache_frontend_VariableFrontend->set()http://forge.typo3.org/issues/344762012-03-03T00:49:20ZFabrizio Branca
<p>A hook is needed that is processed when storing something into the cache.</p>
<p>This hook could be used to reuse the page tags in some external caches like nc_staticfilecache or even varnish. In combination with the hook introduced in <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Adding hook in flushByTag (Closed)" href="http://forge.typo3.org/issues/34475">#34475</a> external caches could easily be synced to the TYPO3 page cache.</p> TYPO3 Core - Feature #34475 (Closed): Adding hook in flushByTaghttp://forge.typo3.org/issues/344752012-03-03T00:34:24ZFabrizio Branca
<p>Cache tags could be reused for nc_staticfile cache or even for tagging varnish cache content. When it is flushed using the caching framework there should be a hook in place that allows to also purge other external caches.</p> TYPO3 Core - Feature #34474 (Closed): Remove clear cache by id from clearCacheCMDhttp://forge.typo3.org/issues/344742012-03-03T00:15:28ZFabrizio Branca
<p>This issue is related to <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Add clearing cache by tag and by identifier to t3lib_tcemain->clear_cacheCmd() (Closed)" href="http://forge.typo3.org/issues/34352">#34352</a>. There a feature was introduced that allows to clear the cache by tag and by id from TCEMAIN.clearCacheCmd.</p>
<p>As discussed (also check comments on <a class="external" href="https://review.typo3.org/#/c/9266/">https://review.typo3.org/#/c/9266/</a>) the clear by id should not be part of the public api as a cache identifier is something internal that's not disposed to the outside in case of cache_pages.</p>
<p>This patch removes the clear cache by id part (while keeping the clear cache by tag).</p> TYPO3 Core - Feature #34403 (Closed): Add stdWrap feature: addPageCacheTagshttp://forge.typo3.org/issues/344032012-02-29T00:22:01ZFabrizio Branca
<p>In the release notes for TYPO3 4.7.0beta1 in the wiki (<a class="external" href="http://wiki.typo3.org/TYPO3_4.7">http://wiki.typo3.org/TYPO3_4.7</a>) you'll find:</p>
<pre>
As a result, these tags are added to the page-cache and TCEmain.clearCacheCmd is enabled to drop page cache by these tags.
</pre>
<p>Actually <strong>this is not true</strong> as issue <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: stdWrap caching (Closed)" href="http://forge.typo3.org/issues/34299">#34299</a> does store cache tags for the stdWrap content to <strong>cache_hash</strong>, but not to <strong>cache_pages</strong>.</p>
<p>This means that you cannot delete this cached stdWrap content using TCEmain.clearCacheCmd with the feature introduced in <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Add clearing cache by tag and by identifier to t3lib_tcemain->clear_cacheCmd() (Closed)" href="http://forge.typo3.org/issues/34352">#34352</a>.</p>
<a name="Add-stdWrapaddPageCacheTags"></a>
<h2 >Add stdWrap.addPageCacheTags<a href="#Add-stdWrapaddPageCacheTags" class="wiki-anchor">¶</a></h2>
<p>On the one hand it actually also might be a very useful feature if page cache tags can be added using stdWrap so I suggest to add following easy to implement feauture to stdWrap that actually stores the tags into cache_pages</p>
<pre>
stdWrap.addPageCacheTags = pagetag1,pagetag2,pagetag3
</pre>
<p>I suggest to not put this configuration option inside "cache." to make clear that this will affect other cache tables than the ones addressed in "cache.".</p>
<p>We usually write those page cache tags inside frontend plugins but having this also inside stdWrap could be very handy.</p>
<a name="Add-TCEmainclearCacheCmd-cacheHashTaglatestnewsbox"></a>
<h2 >Add TCEmain.clearCacheCmd = cacheHashTag:latestnewsbox<a href="#Add-TCEmainclearCacheCmd-cacheHashTaglatestnewsbox" class="wiki-anchor">¶</a></h2>
<p>On the other hand we could also add a TCEmain feauture to clear content by tag from cache_hash. (Also see comments in <a class="external" href="https://review.typo3.org/#change,9266">https://review.typo3.org/#change,9266</a>)</p>
<a name="Conclusion"></a>
<h2 >Conclusion<a href="#Conclusion" class="wiki-anchor">¶</a></h2>
<p>Add these two features to the other set of newly introduced cache (tag) related features gives youfull flexibility to handle cache entries and cache tags on cache_pages and cache_hash content.</p> TYPO3 Core - Feature #34363 (Closed): Add cache_tags to pages tablehttp://forge.typo3.org/issues/343632012-02-27T21:38:41ZFabrizio Branca
<p>By adding a cache_tag field that contains a comma-separated list of tags that will be attached to the stored content many fine-grained caching scenarios are possible. (Also see <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Add clearing cache by tag and by identifier to t3lib_tcemain->clear_cacheCmd() (Closed)" href="http://forge.typo3.org/issues/34352">#34352</a> that allows to clear pages by tag)</p> TYPO3 Core - Feature #34352 (Closed): Add clearing cache by tag and by identifier to t3lib_tcemai...http://forge.typo3.org/issues/343522012-02-27T20:57:22ZFabrizio Branca
<p>The caching framework supports to remove cache entries by identifier and by id. If this was supported by the t3lib_tcemain->clear_cacheCmd(), this feature could also be used in TSConfig's TCEMAIN.clearCacheCmd.</p>
<p>As both require an additional parameter I suggest a syntax like this:</p>
<p>TCEMAIN.clearCacheCmd = tag:firsttag,tag:secondtag<br />TCEMAIN.clearCacheCmd = id:first,id:anotherid</p>
<p>Of course this still can be combined and also used with the other features:</p>
<p>TCEMAIN.clearCacheCmd = 15,tag:news,id:latestnewsbox</p> TYPO3 Core - Feature #34346 (Closed): Add hook to tslib_fe->get_cache_timeout()http://forge.typo3.org/issues/343462012-02-27T20:43:13ZFabrizio Branca
<p>I'd like to have a hook here to influence the calculated cacheTimeout.</p>
<p>This could be used to have the cache lifetime of a page shortened if there are objects on it with a shorter lifetimes. (See <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: stdWrap caching (Closed)" href="http://forge.typo3.org/issues/34299">#34299</a> and <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Add hook to stdWrap_cacheStore (Closed)" href="http://forge.typo3.org/issues/34343">#34343</a>)</p> TYPO3 Core - Feature #34343 (Closed): Add hook to stdWrap_cacheStorehttp://forge.typo3.org/issues/343432012-02-27T20:26:03ZFabrizio Branca
<p>In issue <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: stdWrap caching (Closed)" href="http://forge.typo3.org/issues/34299">#34299</a> caching for stdWrap was introduced.</p>
<p>With this patch I'd like to add a hook to the cacheStore method. Using this patch cache handling can be refined. usecases are<br />- reuse provided tags for page tags<br />- memorize lifetimes so that the pages lifetime can be limited to the shortest stdWrap lifetime</p> TYPO3 Core - Bug #34299 (Closed): stdWrap cachinghttp://forge.typo3.org/issues/342992012-02-26T20:56:21ZFabrizio Branca
<a name="Problem"></a>
<h2 >Problem:<a href="#Problem" class="wiki-anchor">¶</a></h2>
<ul>
<li>Cacheable content is always page specific. Pages cannot share cached content.</li>
<li>Cacheable content has no individual lifetime but is bound to the lifetime of the page where it is placed.</li>
</ul>
<a name="Solution"></a>
<h2 >Solution:<a href="#Solution" class="wiki-anchor">¶</a></h2>
<p>Introduce new configuration options that will store the content into the caching framework:</p>
<pre>5 = TEXT
5 {
cache.key = mycurrenttimestamp
cache.tags = tag_a,tag_b,tag_c
cache.lifetime = 3600
data = date : U
strftime = %H:%M:%S
}
</pre>
<p>See details on <a class="external" href="http://www.fabrizio-branca.de/typo3-individual-cobject-caching.html">http://www.fabrizio-branca.de/typo3-individual-cobject-caching.html</a></p> TYPO3 Core - Feature #28299 (Closed): Add hook to tslib_fe->getHash()http://forge.typo3.org/issues/282992011-07-18T20:43:06ZFabrizio Branca
<p>This hook enables you to modify the hash_base that is used to store <br />different versions of a page in the cache. Normally it is fixed to <br />take the id, cHash, groups and some other stuff into account, but does <br />not allow to add own parameters. <br />Using this hook you can enable to store different versions of a page <br />depending on other parameters than GET-parameters. <br />It also solves an issue that different values of linkVars will produce <br />the same page if used independent from TypoScript conditions and without <br />cHash (which otherwise should be forced for all plugins and menu generation).</p> TYPO3 Core - Feature #28095 (Closed): Add hashing algorithms to stdWraphttp://forge.typo3.org/issues/280952011-07-11T20:02:56ZFabrizio Branca
<p>Currently it is not possible to get an md5 hash for a value in stdWrap. By adding some lines we could have md5 generation e.g. enabling you to get a gravatar image without using a userfunc:</p>
<p>page.10 = TEXT<br />page.10 {<br /> value = <a class="email" href="mailto:mail@domain.com">mail@domain.com</a><br /> md5 = 1<br /> wrap = <img src="<a class="external" href="http://www.gravatar.com/avatar/|&quot;">http://www.gravatar.com/avatar/|&quot;</a> /><br />}</p> TYPO3 Core - Bug #25021 (Closed): Create page via drag'n'drop does not respect TCAdefaults in pagetshttp://forge.typo3.org/issues/250212011-02-13T19:27:06ZFabrizio Branca
<p>When creating a new page via drag'n'drop in the new pagetree the configured TCAdefaults settings from pagets won't be applied to the newly created page.</p>
<p>(issue imported from #M17565)</p> TYPO3 Core - Bug #24017 (Closed): htmlArea RTE: PHP Warning: Invalid argument supplied for foreac...http://forge.typo3.org/issues/240172010-11-11T08:16:44ZFabrizio Branca
<p>Problem:<br />The foreach loop in EXT:rtehtmlarea/ext_tables.php creates warnings because it is not always an array.</p>
<p>Solution:<br />Check if $TYPO3_CONF_VARS['EXTCONF'][$_EXTKEY]['plugins'] is an array before</p>
<p>(issue imported from #M16347)</p> TYPO3 Core - Feature #23883 (Closed): Edit TypoScript file content in t3editorhttp://forge.typo3.org/issues/238832010-10-30T17:19:22ZFabrizio Branca
<p>Problem:<br />When putting TypoScript in files you cannot edit their content within the t3editor (using syntax highlighting,...)</p>
<p>Solution:<br />This feature loads the content of the referenced (via <INCLUDE_TYPOSCRIPT ...>) TypoScript files into the editor wrapping them into "### <INCLUDE_TYPOSCRIPT ...> BEGIN" and "### <INCLUDE_TYPOSCRIPT ...> END". After saving the template the content between those commented lines will be written back to the file.</p>
<p>Read some more here (that was my first approach putting this feature into an own extension "tsf")<br /><a class="external" href="http://www.fabrizio-branca.de/fablog/post/edit-typoscript-file-content-in-t3editor.html">http://www.fabrizio-branca.de/fablog/post/edit-typoscript-file-content-in-t3editor.html</a></p>
<p>Additionally now the tstemplate_info module comes with an extra checkbox that allows you to enable/disable this feature.</p>
<p>(issue imported from #M16183)</p> TYPO3 Core - Feature #22169 (Closed): ext_typoscript_setup.txt cannot be overriden by static file...http://forge.typo3.org/issues/221692010-02-23T16:54:48ZFabrizio Branca
<p>Problem:<br />Some extension still deliver ext_typoscript_setup.txt (amongst them some popular ones like templavoila and new ones like felogin...). In the sys_template record you can choose <br />- whether to not include them at all (Never include before this template record) <br />- whether to always include them<br />- or to include them only if the template is a root template.<br />In any case (when include) the templates will be included <em>after</em> the static ones and the static ones from extensions. This makes it impossible to override settings there from within a static template (without having a second template on the next level)</p>
<p>Solution:<br />Offer a new option that includes those templates if the Root-Flag is set, but includes them before all other templates (so you can overwrite them).</p>
<p>Notes: <br />Apply the patch, install an extension with ext_typoscript_setup.txt and tehn have a look at the order of templates in the template analyzer with the different options.</p>
<p>(issue imported from #M13634)</p>