TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692011-10-19T18:59:47ZTYPO3 Forge
Redmine TYPO3 Core - Bug #31120 (Closed): Add default csc-mailform DIV wraphttp://forge.typo3.org/issues/311202011-10-19T18:59:47ZOliver Haderoliver.hader@typo3.org
<p>A new form element does not have any class settings.<br />This issue reintroduces stdWrap possibilites for the new form system extension.</p> TYPO3 Core - Bug #11163 (Closed): Actions performed on tabs are not executed on the correct works...http://forge.typo3.org/issues/111632010-11-30T14:00:43ZOliver Haderoliver.hader@typo3.org
<p>Actions performed on tabs are not executed on the correct workspace</p> TYPO3 Core - Task #11162 (Closed): Suggest to Core and other extensions to increase the type of t...http://forge.typo3.org/issues/111622010-11-30T12:40:17ZOliver Haderoliver.hader@typo3.org
<p>Currently the field t3ver_stage which is defined by each module/extension that supports workspaces is defined as TINYINT and thus supports up to 255 stages. This was way enough until now - however since we have custom stages right now and each workspace can also have stages, it might happen that 255 is not enough anymore.</p>
<p>Thus, we should consider to give the suggestion to the Core and Extension Developers to use INT as storage type for the t3ver_stage field.</p> TYPO3 Core - Task #10201 (Closed): Set up test environment for team membershttp://forge.typo3.org/issues/102012010-10-11T18:29:49ZOliver Haderoliver.hader@typo3.org
<p>Set up a test environment for team members.<br />A TYPO3 introduction package will be used to visualize the work. The sources are fetched automatically via cron job from GitHub.</p>
<p>Future URL: <a class="external" href="http://workspaces.typo3projects.org/">http://workspaces.typo3projects.org/</a></p> TYPO3 Core - Bug #23287 (Closed): Clearing caches in backend only displays empty framehttp://forge.typo3.org/issues/232872010-07-28T14:52:00ZOliver Haderoliver.hader@typo3.org
<p>Clearing caches in backend only displays empty frame - applies for the typo3conf and the frontend cache.</p>
<p>(issue imported from #M15263)</p> TYPO3 Core - Bug #21168 (Closed): Improve the error and exception handlinghttp://forge.typo3.org/issues/211682009-10-01T14:24:37ZOliver Haderoliver.hader@typo3.org
<p>Problem:<br />The new errorhandling in TYPO3 is way too unflexible.<br />- Errors are "converted" to exceptions. This is not very useful because every php warning will be turned into an exception. and will stop the script execution.<br />- DIsplayed error break the backend layout and make forms unusable<br />- Errors and exceptions are only displayed, but there's no build-in possibility to write errors and exception to a log.</p>
<p>Solution(s):<br />- introduce a new parameter for errors which should be handled by the error handler. The already existing parameter "exceptionalErrors" is used only for the error which should throw exceptions.<br />- Display the errors as flashmessages in the BE and as TsLog messages in FE (in the adminpanel)<br />- implement logging of errors and exceptions to the different logging systems TYPO3</p>
<p>Documentation:<br /><a class="external" href="http://wiki.typo3.org/index.php/File:Error_and_exception_handling.odt">http://wiki.typo3.org/index.php/File:Error_and_exception_handling.odt</a></p>
<p>(issue imported from #M12093)</p> TYPO3 Core - Bug #21078 (Closed): Optimize disposal of t3lib_PageRendererhttp://forge.typo3.org/issues/210782009-09-17T17:08:41ZOliver Haderoliver.hader@typo3.org
<p>t3lib_PageRenderer is currently used in the TYPO3 backend and frontend. There the classes template and tslib_fe inherit from t3lib_PageRenderer. However, in frontend disposal it's not required to have the feature set of the page renderer loaded if a request gets served by the cache and nothing is rendered at all.</p>
<p>Thus, instead of using "tslib_fe extends t3lib_PageRenderer", an aggreation shall be used.<br />Extension can then access the page renderer e.g. by $TSFE->getPageRenderer()->addJsFile()</p>
<p>(issue imported from #M11985)</p> TYPO3 Core - Bug #19530 (Closed): Store OpenID information in database instead of using the files...http://forge.typo3.org/issues/195302008-10-30T11:11:28ZOliver Haderoliver.hader@typo3.org
<p>The OpenID information currently gets stored in the filesystem. Due to security reasons it's preferred to have that sensible data in the database.</p>
<p>The file to be changed is class.tx_openid_sv1.php</p>
<p>(issue imported from #M9683)</p> TYPO3 Core - Bug #19496 (Closed): Flexform sections are not working anymore since script.aculo.us...http://forge.typo3.org/issues/194962008-10-22T16:41:47ZOliver Haderoliver.hader@typo3.org
<p>Due to a change of loading JavaScript resources between TYPO3 4.2.1 and 4.2.2 the script.aculo.us JavaScript framework now only gets loaded when it is required (before it was always loaded).</p>
<p>The solution is to explicitely load script.aculo.us when flexform sections are being rendered.</p>
<p>(issue imported from #M9623)</p> TYPO3 Core - Bug #19485 (Closed): Frontend Editing does not work anymorehttp://forge.typo3.org/issues/194852008-10-21T10:51:06ZOliver Haderoliver.hader@typo3.org
<p>Due to a change of loading JavaScript libraries in the back-end by a commond handler function, the front-end editing does not work anymore and shows the following PHP error:</p>
<p>Fatal error: Call to undefined method stdClass::loadJavascriptLib() in t3lib/class.t3lib_tceforms.phpon line 5079</p>
<p>(issue imported from #M9608)</p> TYPO3 Core - Feature #19347 (Closed): Integrate string replacement to stdWraphttp://forge.typo3.org/issues/193472008-09-17T20:23:49ZOliver Haderoliver.hader@typo3.org
<p>With stdWrap it's not possible yet to do (ordered) string replacements for processing content data.</p>
<p>On introducing a new stdWrap property "replacement" that takes a ordered list of replacement definitions multiple manipulations could be executed the same time. Additionally it regular expressions can be used if required.</p>
<p><b>TypoScript example:</b><br /><pre>20 = TEXT
20 {
value = There_is_a_cat,_a_dog_and_a_tiger_in_da_hood!_Yeah!
stdWrap.replacement {
10 {
search = _
replace.char = 32
}
20 {
search = in da hood
replace = around the block
}
30 {
search = #a (Cat|Dog|Tiger)#i
replace = an animal
useRegExp = 1
}
}
}</pre></p>
<p>The indexes 10, 20, 30 are just for setting an order on the execution of the replacement. Each subkey "search", "replace" and "useRegExp" has again stdWrap functionality.</p>
<p>(issue imported from #M9373)</p> TYPO3 Core - Bug #17905 (Closed): t3lib_div::readLLXMLfile does not use localized content anymorehttp://forge.typo3.org/issues/179052007-12-11T16:43:40ZOliver Haderoliver.hader@typo3.org
<p>In bug <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Translated language files are not loaded (Closed)" href="http://forge.typo3.org/issues/17894">#17894</a> the localization of other languages (besides the 'default' language) should be move to an external file to prevent loading unused string data.<br />If this file generated by t3lib_div::llXmlAutoFileName doesn't exist, the localized part is set to an empty array at the end of t3lib_div::readLLXMLfile.</p>
<p>The solution is to check whether this external file exists.</p>
<p>Affects TYPO3 4.1.4 and Trunk when locallang.xml files of extensions were modified locally or extension were updated from TER and have a modified locallang.xml.</p>
<p>(issue imported from #M6924)</p> TYPO3 Core - Feature #17500 (Closed): Localization of child recordshttp://forge.typo3.org/issues/175002007-08-06T20:58:11ZOliver Haderoliver.hader@typo3.org
<p>The localization of child records when viewing the parent record isn't possible. This is a missing feature of TYPO3 4.1.</p>
<p>(issue imported from #M6087)</p> TYPO3 Core - Bug #17001 (Closed): config.linkVars check doesn't allow negative rangeshttp://forge.typo3.org/issues/170012007-02-17T11:05:42ZOliver Haderoliver.hader@typo3.org
<p>The newly introduced linkVars check in TYPO3 4.1 doesn't allow negative ranges.</p>
<p>Example:<br />config.linkVars = my_variable(1-5) is valid<br />config.linkVars = my_variable(-1-5) doesn't work<br />config.linkVars = my_variable(-1--3) doesn't work and looks very ugly</p>
<p>I suggest to use ".." as delimiter, e.g.<br />config.linVars = my_variable(-1..-3)</p>
<p>Possibly it is allowed in TYPO3 4.2 to use config.linkVars = tx_myext_pi1[var](<del>1..-3), but we should change the delimiter from "</del>" to ".." now.<br />(issue imported from #M5009)</p> TYPO3 Core - Bug #16875 (Closed): Wrong character encoding in new child records created via AJAX ...http://forge.typo3.org/issues/168752007-01-21T15:05:47ZOliver Haderoliver.hader@typo3.org
<p>If a new child record was created dynamically using an AJAX call. Umlauts like "äöüß" were not displayed correctly due to a missing character encoding.</p>
<p>(issue imported from #M4820)</p>