TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692015-11-02T18:17:01ZTYPO3 Forge
Redmine TYPO3 Core - Bug #71253 (Closed): Folder Creation Fails If Same Folder Exists at File Storage Roothttp://forge.typo3.org/issues/712532015-11-02T18:17:01ZJeff Segarsjsegars@alumni.rice.edu
<p>Creating a new folder in Filelist fails if a folder of the same name exists in the file storage root. This is due to the $this->driver->folderExists() check in \TYPO3\CMS\Core\Resource\ResourceStorage->createFolder() that only considers the new folder name and not the parent folder. I'd assume this should actually be a call to $this->driver->folderExistsInFolder() instead.</p>
<p>Steps to Reproduce:<br />1) Create "folder1" in the file storage root.<br />2) Create "folder2" in the file storage root.<br />3) Attempt to create "folder1" inside "folder2"</p> TYPO3 Core - Bug #27099 (Closed): HMENU.excludeUidList is not accounted for when determining if a...http://forge.typo3.org/issues/270992011-05-27T21:10:25ZJeff Segarsjsegars@alumni.rice.edu
<p>HMENU.excludeUidList is used to exclude certain pages from menus and is read by tslib_menu->getBannedUids(). This getBannedUids() method is called when actually generating a menu, but is not accounted for when determining menu item states such as IFSUB, ACTIFSUB, and CURIFSUB. This means that IFSUB will trigger even if a page has no visible submenu because its subpages are part of HMENU.excludeUidList.</p>
<p>The solution is to add a check for getBannedUids() inside tslib_menu->isSubMenu().</p> 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 #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 #24688 (Closed): Pagetree cannot be initialized with a specific page IDhttp://forge.typo3.org/issues/246882011-01-20T17:16:22ZJeff Segarsjsegars@alumni.rice.edu
<p>In the backend live search, when someone clicks on a record we would like to select its page in the pagetree so that the editor has a clear picture of where they are. Currently, this does not work for the first load of the tree, but does work after the pagetree is loaded. The following JavaScript has been used for testing...</p>
<p>top.fsMod.recentIds['web'] = ###PID###<br />top.TYPO3.ModuleMenu.App.showModule('web_list');<br />top.TYPO3.Backend.NavigationContainer.PageTree.refresh();</p>
<p>(issue imported from #M17172)</p> TYPO3 Core - Bug #24666 (Closed): Update plugin layout to match other content elementshttp://forge.typo3.org/issues/246662011-01-19T18:11:52ZJeff Segarsjsegars@alumni.rice.edu
<p>In TYPO3 4.5, we have a new layout for built in content elements and plugins. FE Login is a bit of a hybrid since it is a frontend plugin but replacing the old built in content element. To achieve this, it overrides the TCA showitem definition of the old login content element. This showitem definition should be updated to the 4.5 layout.</p>
<p>(issue imported from #M17147)</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 #24311 (Closed): TCEForms->getIconHTML() does not resolve back paths before chec...http://forge.typo3.org/issues/243112010-12-08T21:58:30ZJeff Segarsjsegars@alumni.rice.edu
<p>TCEForms->getIconHTML() returns the HTML for a static image file or a sprite icon. When checking for a static image file, the back path is not resolved before calling is_file() so references such as "../uploads/path/to/my/file.png" will fail. This is most easily reproduced with TemplaVoila and preview icons for Data Structures and Template Objects.</p>
<p>(issue imported from #M16703)</p> TYPO3 Core - Bug #24310 (Closed): TCEForm select dropdowns have text overlapping icon in Webkithttp://forge.typo3.org/issues/243102010-12-08T21:19:01ZJeff Segarsjsegars@alumni.rice.edu
<p>When using the select dropdown for pages, content elements, etc in Webkit, the item text overlaps the icon.</p>
<p>Since form styling (especially selects) is horribly inconsistent between browsers, the best option I've found is to target Webkit specifically with a class already applied by ExtJS.</p>
<p>(issue imported from #M16702)</p> TYPO3 Core - Feature #24092 (Closed): Add live search to the backend toolbarhttp://forge.typo3.org/issues/240922010-11-17T05:53:32ZJeff Segarsjsegars@alumni.rice.edu
<p>As part of T3UXW09, a live search module was added to the backend toolbar. This needs a little further refinement, testing, and UI work to be included in TYPO3 4.5.</p>
<p>(issue imported from #M16432)</p> TYPO3 Core - Bug #23401 (Closed): Flexform sections cannot be deleted in frontend editinghttp://forge.typo3.org/issues/234012010-08-18T22:10:12ZJeff Segarsjsegars@alumni.rice.edu
<p>When using feedit or feeditadvanced, flexform sections cannot be deleted.</p>
<p>In t3lib_tceforms->getSingleField_typeFlex_draw(), a special hidden form field is created to pass along the name of the element being deleted. In a backend context, itemFormElName is data. In a frontend context, its TSFE_EDIT[data].</p>
<p>$actionFieldName = '_ACTION_FLEX_FORM'.$PA['itemFormElName'].$s<sup><a href="#fn0">0</a></sup>.'][_ACTION]['.$s<sup><a href="#fn1">1</a></sup>;</p>
<p>In t3lib_tcemain->checkValueFlex(), the check is hardcoded to rely on the backend version.</p>
<p>$actionCMDs = t3lib_div::_GP('_ACTION_FLEX_FORMdata');</p>
<p>The "data" portion should not be hardcoded and the t3lib_tcemain should not read directly from the GET/POST data.</p>
<p>(issue imported from #M15496)</p> TYPO3 Core - Bug #23359 (Closed): pageRenderer doesn't take frontend editing into account when co...http://forge.typo3.org/issues/233592010-08-06T00:55:33ZJeff Segarsjsegars@alumni.rice.edu
<p>Currently the pageRenderer uses t3lib_compressor only when the TYPO3_MODE == 'BE'. This means that during frontend editing, individual stylesheets are loaded and are not combined. The number of stylesheets exceeds what IE can handle and results in an unstyled editing form.</p>
<p>The obvious solution would be for the page renderer to check for frontend editing also but we may need to look for an feeditadvanced solution until it can be handled properly in the core.</p>
<p>Cross-posted to the feeditadvanced bugtracker at <a class="external" href="http://forge.typo3.org/issues/9173">http://forge.typo3.org/issues/9173</a> also.</p>
<p>(issue imported from #M15368)</p>