TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692011-01-25T19:01:44ZTYPO3 Forge
Redmine TYPO3 Core - Bug #24810 (Closed): CSH popup windows for FlexForm fields do not show field labelhttp://forge.typo3.org/issues/248102011-01-25T19:01:44ZJeff Segarsjsegars@alumni.rice.edu
<p>When using CSH for FlexForms, the popup window does not show the field label in the header like it does for normal fields. Instead, a path such as tt_content.pi_flexform.myext_pi1.list: myField is shown.</p>
<p>(issue imported from #M17310)</p> TYPO3 Core - Bug #24802 (Closed): Admin Panel CSS is loaded in the Backendhttp://forge.typo3.org/issues/248022011-01-25T16:16:13ZJeff Segarsjsegars@alumni.rice.edu
<p>Since the admin panel CSS is at t3skin/visual/admin_panel.css, it is loaded with every backend request. Obviously, the admin panel is not needed in the backend so its a bit of a waste to load it.</p>
<p>In addition, the CSS has a strange issue that it interferes with resizable text areas in Chrome 9 (as described on <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Resizable textares not working in Chrome 9 (Closed)" href="http://forge.typo3.org/issues/24744">#24744</a>).</p>
<p>Moving the admin panel CSS to t3skin/standalone/admin_panel.css ensures that it is not loaded automatically by the backend.</p>
<p>(issue imported from #M17302)</p> TYPO3 Core - Bug #24692 (Closed): Live Search: Search query loops over all tables even after max ...http://forge.typo3.org/issues/246922011-01-20T22:10:23ZJeff Segarsjsegars@alumni.rice.edu
<p>When executing a live search, we loop over all tables defined in the TCA. After this search is complete, we then slice the search array and throw away everything we don't need.</p>
<p>For better performance, we should stop searching as soon as we've found enough results.</p>
<p>(issue imported from #M17177)</p> TYPO3 Core - Bug #24581 (Closed): Live Search uses id=0 to display all search results to non-admi...http://forge.typo3.org/issues/245812011-01-15T00:02:58ZJeff Segarsjsegars@alumni.rice.edu
<p>After clicking the Show All button for Live Search, results are shown in list view. Live search is currently hardcoded to always show the results on the site root (id=0), which is not accessible for non-admin users.</p>
<p>The old backend search solved this by always using the first webmount. This has its own issues, as described in <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Backend search is unusable for editors (Closed)" href="http://forge.typo3.org/issues/23190">#23190</a>.</p>
<p>(issue imported from #M17045)</p> TYPO3 Core - Bug #24534 (Closed): Update page and tt_content labels to use title casehttp://forge.typo3.org/issues/245342011-01-13T00:04:30ZJeff Segarsjsegars@alumni.rice.edu
<p>According to <a class="external" href="http://wiki.typo3.org/TCEformsRecommendedLayout">http://wiki.typo3.org/TCEformsRecommendedLayout</a>, form labels should use title case. This is mostly the case already in the backend but there are several exceptions in pages and tt_content the should be fixed.</p>
<p>This is not a change of meaning in the labels, since the wording doesn't change and it just follow different capitalization/punctuation rules so the existing labels are changed but do not need to be re-translated.</p>
<p>(issue imported from #M16989)</p> TYPO3 Core - Bug #24533 (Closed): Update Context Sensitive Help for pages and tt_content to match...http://forge.typo3.org/issues/245332011-01-12T22:27:36ZJeff Segarsjsegars@alumni.rice.edu
<p>With the recent label updates from JoH, Ingo, and others, the CSH doesn't match the actual labels for pages and tt_content very well.</p>
<p>In addition, a lot of the CSH descriptions are outdated and could use a little tweaking for their grammar. This hasn't been a complete rewrite of the CSH but more of a cleanup while fixing the label issues.</p>
<p>Additionally, we want to make these changes as easy as possible on the translators so that the existing CSH continues to work if new translations are not available.</p>
<p>1) Create new CSH files (inside a 4.5 folder) for pages and tt_content so that old TYPO3 versions are not affected.<br />2) Register these new CSH files using $TYPO3_CONF_VARS']['SYS']['locallangXMLOverride']</p>
<p>When CSH is requested, the hierarchy will look like this....<br />1) Check for new 4.5 label in the current language<br />2) Check for old label in the current language<br />3) Check for new 4.5 label in the default language<br />4) Check for old label in the default language</p>
<p>In addition to tt_content and pages, there are 2 updates for CSH files that use SysFolder rather than the new Folder label.</p>
<p>(issue imported from #M16988)</p> TYPO3 Core - Bug #24356 (Closed): Highlighted pages in a workspace overlap the pagetree border.http://forge.typo3.org/issues/243562010-12-17T18:46:49ZJeff Segarsjsegars@alumni.rice.edu
<p>When using workspaces, pages with changes are highlighted. This highlight slightly overlaps the border of the pagetree.</p>
<p>To fix it, we just need 2px of margin added to the Workspace info and highlighted pages.</p>
<p>(issue imported from #M16769)</p> TYPO3 Core - Bug #23293 (Closed): Raw HTML shown in Element Browser's pagetree with options.pageT...http://forge.typo3.org/issues/232932010-07-28T22:35:10ZJeff Segarsjsegars@alumni.rice.edu
<p>When options.pageTree.showNavTitle = 1 is set, we get a little too much data htmlspecialchar'd and raw HTML is shown in the Element Browser's pagetree. See attached screenshot.</p>
<p>(issue imported from #M15273)</p> TYPO3 Core - Bug #22961 (Closed): Missing link in Install Tool Footerhttp://forge.typo3.org/issues/229612010-06-22T15:57:34ZJeff Segarsjsegars@alumni.rice.edu
<p>"This is free software, and you are welcome to redistribute it under certain conditions; click for details."</p>
<p>The click for details text has nothing to click.</p>
<p>(issue imported from #M14822)</p> TYPO3 Core - Bug #21071 (Closed): Install Tool button in User Settings does not reflect current s...http://forge.typo3.org/issues/210712009-09-16T15:53:03ZJeff Segarsjsegars@alumni.rice.edu
<p>In User Settings we have a button to create or delete the ENABLE_INSTALL_TOOL file. The ENABLE_INSTALL_TOOL file itself is manually deleted on the first access when there's been an hour of inactivity and not immediately deleted when that hour of inactivity occurs. This leads to a User Settings button that doesn't really reflect the current state.</p>
<p>When an hour has passed since the last activity, the User Settings button will still offer the opportunity to delete the ENABLE_INSTALL_TOOL file despite the fact that the Install Tool will not be accessible if you try to browse to it directly.</p>
<p>The solution is to have User Settings update the timestamp on the existing ENABLE_INSTALL_TOOL file or delete the file completely if its more than an hour hold, just like the main Install Tool code.</p>
<p>(issue imported from #M11974)</p> TYPO3 Core - Bug #18901 (Closed): XHTML Validation Problems on Forgot Password Formhttp://forge.typo3.org/issues/189012008-06-03T17:22:46ZJeff Segarsjsegars@alumni.rice.edu
<p>The forgot password form has a minor XHTML validation problem when using the default template.</p>
<p>Both the label "for" attribute and the input ID are tied to ###FORGOT_EMAIL### (as is the input "name" attribute"). This marker evaluates as "tx_felogin_pi1[forgot_email]", but the brackets are not allowed in the ID or "for" attribute.</p>
<p>Changing the ID to forgot-email or something like that should clear up the issue, although it may introduce some small compatibility problems for people hooking CSS or Javascript onto the existing ID.</p>
<p>(issue imported from #M8600)</p> TYPO3 Core - Bug #18427 (Closed): Required fields within flexform section elements cause Javascri...http://forge.typo3.org/issues/184272008-03-11T19:29:42ZJeff Segarsjsegars@alumni.rice.edu
<p>If a flexform uses section elements with required fields, a Javascript error is generated as soon as the form is loaded and that flexform cannot be saved.</p>
<p>I believe this is related to changeset 2628, which made significant enhancements to section handling. To see the error in action, check out the Scoring Tab within the pb_survey plugin.</p>
<p>The error message is "document[TBE_EDITOR.formname][elementName] has no properties". Once the required eval is removed, the Javascript errors go away because the code causing the error is no longer executed.</p>
<p>(issue imported from #M7829)</p> TYPO3 Core - Bug #18422 (Closed): Task center iframes are only sized on loadhttp://forge.typo3.org/issues/184222008-03-10T21:35:39ZJeff Segarsjsegars@alumni.rice.edu
<p>Within the task center, iframes are used to include external content such as a TCE form for editing records as part of sys_action. These iframes have an onload attribute to set the height of the form, but this event handler could be improved.</p>
<p>Other iframes within the new backend are automatically resized when the browser window is resized (via Prototype event handlers) so the task center should get this same behavior.</p>
<p>(issue imported from #M7820)</p> TYPO3 Core - Bug #17546 (Closed): Default values not used in IRRE childrenhttp://forge.typo3.org/issues/175462007-08-21T01:48:07ZJeff Segarsjsegars@alumni.rice.edu
<p>When editing child records using IRRE, the TCA-defined defaults are not used. This is due to a small error in t3lib_tceforms_inline->getRecord().</p>
<p>The getRecord() method calls t3lib_transferdata->fetchRecord($table, $idList, $operation). According to comments on the fetchRecord method, "If $operation is "new", then negative ids are meant to point to a "previous" record and positive ids are PID values for new records. Otherwise (for existing records that is) it is straight forward table/id pairs.".</p>
<p>I updated the call to fetchRecord() so that it passes along the pid when $operation is "new" and this causes defaults to be set properly in my testing.</p>
<p>I'm attaching the one line patch to fix this.</p>
<p>(issue imported from #M6183)</p> TYPO3 Core - Bug #15354 (Closed): Import of testsite from T3D exceeds PHP maximum_execution_timehttp://forge.typo3.org/issues/153542006-01-03T17:56:04ZJeff Segarsjsegars@alumni.rice.edu
<p>When testing the import of a T3D-based testsite package on my local install, I bumped up against PHP's maximum_execution_time of 30 seconds. Once I raised this limit in php.ini, the import worked properly.</p>
<p>At Michael Stucki's suggestion, I revert to the original php.ini and added "ini_set('max_execution_time', 300);" to the top of typo3conf/localconf.php, which also fixed the timeout problems.</p>
<p>Adding ini_set to the impexp system extension should fix this issue.</p>
<p>(issue imported from #M2169)</p>