TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692008-02-20T23:09:03ZTYPO3 Forge
Redmine TYPO3 Core - Bug #18263 (Closed): Backend Alignment Problems in Internet Explorerhttp://forge.typo3.org/issues/182632008-02-20T23:09:03ZJeff Segarsjsegars@alumni.rice.edu
<p>The second row of the docheader has some alignment problems in Internet Explorer, as text labels and icons are not inline with one another and have different vertical spacing than other browsers.</p>
<p>The username in the top bar of the backend also suffers from similar alignment problems in Internet Explorer.</p>
<p>The attached patch tweaks the CSS for improved cross browser alignment.</p>
<p>(issue imported from #M7605)</p> TYPO3 Core - Bug #18259 (Closed): Remove checkbox border from t3skin in Internet Explorerhttp://forge.typo3.org/issues/182592008-02-20T18:14:22ZJeff Segarsjsegars@alumni.rice.edu
<p>t3skin defines a CSS style for input checkboxes that has no border, but this style is ignored by Internet Explorer since it doesn't support attribute selectors.</p>
<p>The solution is to dynamically add a class to all checkboxes using Prototype so that the CSS style can be targeted at that class.</p>
<p>(issue imported from #M7601)</p> TYPO3 Core - Bug #18258 (Closed): Fix module menu alignment and hover in Internet Explorerhttp://forge.typo3.org/issues/182582008-02-20T16:21:32ZJeff Segarsjsegars@alumni.rice.edu
<p>In Internet Explorer, labels in the module menu are not aligned the same as other browsers due to a collapsing span on the menu icons. Also, Internet Explorer 6 does not support the hover attribute on list elements.</p>
<p>To fix this, I've changed the icons to float left which allows IE and other browsers to give them a consistent width (regardless of icon size) and preserve the alignment in all browsers. For the hover, I've used a CSS selector within prototype to add and remove a hover class on mouseenter and mouseleave. These events are only available in IE, but thats fine since IE is our target.</p>
<p>(issue imported from #M7598)</p> TYPO3 Core - Bug #18118 (Closed): CSS Gremlins in t3skinhttp://forge.typo3.org/issues/181182008-02-05T06:28:37ZJeff Segarsjsegars@alumni.rice.edu
<p>From a thread on the dev list, we came up with a list of simple CSS gremlins in t3skin that can be addressed quickly. The attached patch fixes the following issues...</p>
<p>1. Links are not underlined (For now, all links are underlined but this means a lot of stuff is underlined. We may want to revisit this).<br />2. Remove borders and background colors from select fields.<br />3. File->Filelist has an old-style table header.<br />4. File->Filelist has an unstyled table when using clipboard #1.<br />5. Web->Info tables are not styled at all in the pagetree overview.<br />6. TCEForms record header has a background in IE.<br />7. Task Center horizontal tab menu on the left still has old skin colors and background.<br />8. Category treeviews like in tt_news have some extra pixels between the records.</p>
<p>(issue imported from #M7388)</p> TYPO3 Core - Bug #18116 (Closed): Remove hardcoded references to alt_main.php backend interfacehttp://forge.typo3.org/issues/181162008-02-04T19:17:41ZJeff Segarsjsegars@alumni.rice.edu
<p>Various places in the core are hardcoded to use the alt_main.php backend interface. I'm introducing a t3lib_BEfunc function to get the current backend script and use this instead of alt_main.php.</p>
<p>(issue imported from #M7386)</p> TYPO3 Core - Feature #18087 (Closed): Improve usability of Constants Editorhttp://forge.typo3.org/issues/180872008-02-01T06:26:42ZJeff Segarsjsegars@alumni.rice.edu
<p>The current Constants Editor requires clicking on a checkbox and reloading the entire editing form in order to edit a single constant. This can be improved by using Javascript to make the editing more dynamic.</p>
<p>A demo of this dynamic editing can be seen at <a class="external" href="http://webempoweredchurch.com/fileadmin/proj/misc/constants_editor.mp4">http://webempoweredchurch.com/fileadmin/proj/misc/constants_editor.mp4</a></p>
<p>In addition, the HTML output of the submodule can be cleaned up to produce more semantically valid HTML.</p>
<p>There's still plenty of room for discussion on this patch. Is a trash can the appropriate icon or should we have something that indicates close or rollback instead of delete.</p>
<p>We'll also need intregration with the new docheader for the Templates module once that is complete.</p>
<p>As such, this is an attempt to get the patch out there for inclusion in 4.2, but I expect there will be some refinements needed.<br />(issue imported from #M7336)</p> TYPO3 Core - Bug #18041 (Closed): Add hook for warning messages within Help->About modules and im...http://forge.typo3.org/issues/180412008-01-23T05:57:47ZJeff Segarsjsegars@alumni.rice.edu
<p>A postProcessingHook within t3lib_beFunc->displayWarningMessages would allow extensions to insert their own warning messages if critical problems were detected.</p>
<p>The default warning messages could also be cleaned up a little, with links to the location where the suggested updates can be made.</p>
<p>(issue imported from #M7247)</p> TYPO3 Core - Feature #17992 (Closed): Add pageUnavailable_handling for system problems and mainte...http://forge.typo3.org/issues/179922008-01-14T23:40:45ZJeff Segarsjsegars@alumni.rice.edu
<p>There are already several places in the TYPO3 Core where an HTTP 503 Not Available header is sent in response to major problems rendering the page. This occurs mainly when a database connection is unavailable or there's a serious problem getting the requested page and template. In each of these cases, the 503 header is sent and a specific, but static a error message is displayed.</p>
<p>I would propose that we add an equivalent to pageNotFound_handling for the times when a page is unavailable. This would allow a customized maintenance page to automatically be displayed when problems occur (ie. database goes down) and for the normal site to return immediately when those problems are resolved. I'd also suggest an Install Tool setting to manually turn this maintenance page off and on whenever the site admin is performing maintenance.</p>
<p>I'm attaching an inital version of patch for this. It adds some Install Tool settings to t3lib/config_default.php and mimics the pageNotFound_handling in tslib_fe. There's also a small addition to tslib/index_ts.php that checks if pageUnavailable has been forced after TSFE is created, but before a database connection is attempted.</p>
<p>The one thing this patch does not currently handle is the "Page is being generated" message since there's some additional complexity with it.</p>
<p>(issue imported from #M7150)</p> TYPO3 Core - Bug #17959 (Closed): Section-based FCEs are saved with incorrect element IDhttp://forge.typo3.org/issues/179592007-12-31T06:09:22ZJeff Segarsjsegars@alumni.rice.edu
<p>When working with trunk and FCEs that have sections defined, saving the FCE results in bad data in the the FCE XML. Instead of an element like <br /> <section index="1"><br />I end up with<br /> <field index="ID-edd5ba543c-idx36456-form"></p>
<p>This data results in PHP errors in both the frontend and in the TV Page Module.</p>
<p>From what I can tell, these IDs are related to the FCE changes in changeset 1628. In TCEMain, the temporary IDs are mapped into normal section indexes, and the normal section elements are saved FCE XML. In the current code, this mapping only occurs if the element is not new. When I move the mapping outside this check so that it always occurs, saving and rendering work fine for me.</p>
<p>I'm attaching the patch for this issue. I don't fully understand all the code at this point in TYPO3 so there may be better ways to get it done, but it does seem to work for me.</p>
<p>(issue imported from #M7067)</p> TYPO3 Core - Feature #17765 (Closed): Add tab filtering and file type filtering to TCA-defined li...http://forge.typo3.org/issues/177652007-11-07T18:09:03ZJeff Segarsjsegars@alumni.rice.edu
<p>Many extensions would benefit from the ability to simplify the link wizard. For example, when creating a record for a TemplaVoila Template Object, selecting an HTML template is the only reasonable option but the tabs for TYPO3 Pages and email addresses are still displayed. Likewise, its possible to select an image file.</p>
<p>The attached patch adds allowedExtensions and blindLinkOptions as params when defining the link wizard in the TCA. There is already TSConfig support for blindLinkOptions, so we're sticking with a common name.</p>
<p>The TYPO3 Core API documentation will need to be updated to reflect this change also.</p>
<p>(issue imported from #M6672)</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 - Feature #17540 (Closed): Add user function support to Constant Editorhttp://forge.typo3.org/issues/175402007-08-17T22:43:22ZJeff Segarsjsegars@alumni.rice.edu
<p>In addition to the built in form widgets, it would be nice if the Constant Editor supported user functions to allow more custom user interfaces.</p>
<p>This can be accomplished pretty easily with t3lib_div::callUserFunction and a user function that outputs the appropriate HTML.</p>
<p>I'm attaching a patch to add this support. I can also add a small extension that demonstrates this functionality if it would be helpful.</p>
<p>(issue imported from #M6169)</p> TYPO3 Core - Bug #17339 (Closed): linkHandler Hook Not Initialized Properlyhttp://forge.typo3.org/issues/173392007-05-29T18:36:02ZJeff Segarsjsegars@alumni.rice.edu
<p>TYPO3 4.1.0 added a new hook for linkHandlers in tslib_content to allow extensions to link to individual records.</p>
<p>The code here uses TYPO3_CONF_VARS to initialize the hook, but the TYPO3_CONF_VARS are not declared as a global so the hook array is always empty.</p>
<p>I"m attaching the very trivial patch to declare them as a global and also to make sure the hook method exists before it is called.</p>
<p>(issue imported from #M5701)</p> TYPO3 Core - Bug #17206 (Closed): Problem ignoring extension constraintshttp://forge.typo3.org/issues/172062007-04-13T22:06:21ZJeff Segarsjsegars@alumni.rice.edu
<p>When an extension has several types of constraints (dependencies, suggestions, and conflicts) problems can result when trying to install the extension.</p>
<p>As long as there are unresolved constraints in a category, a hidden input box is used to keep track of the constraints that have already been ignored. When all constraints in a category have been resolved, however, the hidden input boxes are no longer used. This causes problems when one category of constraints has been resolved but another has not.</p>
<p>For example, I can have extension dependencies and suggestions. I click ignore for all the suggestions and click the "Try Again" button. When I do this, the resulting page only shows my dependencies. I then resolve these dependencies and click the "Try Again" button again. When I do this, the ignored suggestions come back because they were not tracked on the previous page.</p>
<p>The solution is to keep the hidden input boxes and any associated text around even if all the constraints in a category have been resolved. I'm attaching a patch that should accomplish this.</p>
<p>(issue imported from #M5421)</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>