TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692009-11-28T15:53:33ZTYPO3 Forge
Redmine TYPO3 Core - Bug #21726 (Closed): Updating translations from repository in extension manager fail...http://forge.typo3.org/issues/217262009-11-28T15:53:33ZOliver Haderoliver.hader@typo3.org
<p>Updating translations from repository in extension manager fails in Safari 4.0.4 on Mac OS X. Just a white page is shown - after a while, when all packages have been downloaded, suddenly the full status appears. Thus, showing the process dynamically does not work.</p>
<p>In Firefox everything works as expected.</p>
<p>(issue imported from #M12822)</p> TYPO3 Core - Feature #20294 (Closed): Integrate possibility to validate custom links for RTEhtmla...http://forge.typo3.org/issues/202942009-04-08T13:12:09ZOliver Haderoliver.hader@typo3.org
<p>In RTEhtmlarea there's a possibility to define custom links, e.g. by using a link handler. It might happen, that the name of the linkhandler (defined in $TYPO3_CONF_VARS['SC_OPTIONS']['tslib/class.tslib_content.php']['typolinkLinkHandler']) is different to the used link prefix (e.g. "linkhandler" vs. "myOwnLinkhandler:"). Furthermore it can happen that those custom links are not defined using a linkhandler at all.<br />Links that could not be validated by the current strict mechanism are shown as invalid in RTEhtmlarea.</p>
<p>The solution is to integrate a new hook that can take care of that validation in general.</p>
<p>(issue imported from #M10872)</p> TYPO3 Core - Feature #2567 (Closed): Recycler: Change layout and interface to fit HCI suggestionshttp://forge.typo3.org/issues/25672009-02-04T21:46:43ZOliver Haderoliver.hader@typo3.org
Change layout and interface to fit HCI suggestions
<ul>
<li>concerning usability</li>
<li>concerning styling and colors</li>
</ul> TYPO3 Core - Bug #17058 (Closed): foreign_unique without foreign_selector doesn't workhttp://forge.typo3.org/issues/170582007-03-01T09:27:49ZOliver Haderoliver.hader@typo3.org
<p>If in TCA on the parent side a field of type "inline" is defined to be unique ("foreign_unique") and no selector is used ("foreign_selector") this will produce a JavaScript error.<br />The reason is a wrong value delivered by JSON concerning uniqueness/selector.</p>
<p>Use the IRRE Testsuite from <a class="external" href="http://inpublica.de/typo3/T3X_irre_testsuite.t3x">http://inpublica.de/typo3/T3X_irre_testsuite.t3x</a>, create new company and person records of type "[IRRE Foreign Field Attributes] ..." and then try to relate companies to persons by using the select field of the child records.</p>
<p>This issue was reported by Thomas Murphy on the irre-list, see <a class="external" href="http://lists.typo3.org/pipermail/typo3-project-irre/2007-February/000020.html">http://lists.typo3.org/pipermail/typo3-project-irre/2007-February/000020.html</a><br />(issue imported from #M5098)</p> TYPO3 Core - Bug #17040 (Closed): TSconfig mod.web_list.allowedNewTables used in t3lib_TCEforms_i...http://forge.typo3.org/issues/170402007-02-25T15:01:48ZOliver Haderoliver.hader@typo3.org
<p>The TSconfig property mod.web_list.allowedNewTables is accidently used for IRRE to determine if a record link is allowed. This behaviour is not required for Inline Relational Record Editing anymore.</p>
<p>The following TSconfig example breaks the functionality of IRRE while editing an existing parent record:<br />mod.web_list {<br /> allowedNewTables = pages,tt_content<br />}</p>
<p>(issue imported from #M5069)</p> TYPO3 Core - Feature #17039 (Closed): Integrate mod.web_list.deniedNewTables as opposite of allow...http://forge.typo3.org/issues/170392007-02-25T13:27:42ZOliver Haderoliver.hader@typo3.org
<p>TSconfig mod.web_list.allowedNewTables allows to define a set of tables which are allowed as new records on a page. mod.web_list.hideTables hides existing records on a page to be displayed but doesn't affect creating new records.<br />Thus, the opposite of allowedNewTables is required: mod.web_list.deniedNewTables</p>
<p>Inline Relational Record Editing (IRRE) handles relations of the cardinality 1:n. Child records depend directly on their parent and cannot exist without them (composition). Thus, it makes no sense to allow to create tables of the second or third generation in this hierarchy directly.<br />(issue imported from #M5068)</p> TYPO3 Core - Bug #17002 (Closed): cHash is not recreated on disposal in config.linkVarshttp://forge.typo3.org/issues/170022007-02-17T11:16:11ZOliver Haderoliver.hader@typo3.org
<p>Imagine you'd like to forward one or more extension variables through the system. The common way to do this is to use config.linkVars. For caching purposes the cHash should be set.</p>
<p>Example:<br />config.linkVars = type,L,tx_myext_pi1,tx_myext_pi2,cHash</p>
<p>Unfortunatelly the cHash will be taken as it is from the current page being displayed. A wrong cHash results into an error message being reported ("wrong cHash").</p>
<p>The solution is to recreate/recalculate the cHash if it should be used in config.linkVars.</p>
<p>(issue imported from #M5010)</p> TYPO3 Core - Feature #16974 (Closed): Provide general AJAX call handler for backend functions/mod...http://forge.typo3.org/issues/169742007-02-11T11:07:25ZOliver Haderoliver.hader@typo3.org
<p>This is a feature request for TYPO3 4.2.</p>
<p>To avoid that every backend module has to create and use its own AJAX handler, a general handler class is required. According to the eID of the TYPO3 front-end there shall be a mID (module identifier) for back-end purpose.</p>
<p>The stack to register and enable a module and an action could look like this:<br />$TYPO3_CONF_VARS['BE']['mID_include'][<package>][<action>] = array(<br /> 'handler' => '<handler>',<br /> 'required' => array('<php-class-file-1>', '<php-class-file-2>'),<br /> 'encodeUTF8' => <boolean><br />);</p>
<p>The extended Backus-Naur (eBNF) form of the key 'handler' could look like this:<br />handler ::= <static> | <instance><br />static ::= <class> "::" <function><br />instance ::= (<variable>|<class>) "->" {<object> "->"} <method><br />variable ::= "$" <valid-php-identifier><br />class ::= <valid-php-identifier><br />object ::= <valid-php-identifier><br />function ::= <valid-php-identifier><br />method ::= <valid-php-identifier><br />(* @see <a class="external" href="http://www.php.net/manual/en/language.variables.php">http://www.php.net/manual/en/language.variables.php</a> *)<br />valid-php-identifier = ? chars that are valid in PHP for variables ?</p>
<p>Currently affected parts of the TYPO3 core:<br />- Kasper's new backend functionalities<br />- AJAX page tree and file tree<br />- Inline Relational Record Editing</p>
<p>This feature could be used by any backend function of individual user extensions.</p>
<p>(issue imported from #M4966)</p> TYPO3 Core - Feature #16919 (Closed): AJAX pagtree update could be used when a new page is createdhttp://forge.typo3.org/issues/169192007-01-29T19:58:43ZOliver Haderoliver.hader@typo3.org
<p>When a new page is created, the page tree is triggered to be refreshed by a javascript call:<br />top.content.nav_frame.refresh_nav()</p>
<p>This behaviour could also be achieved by the new AJAX pagetree. To speed up reloading, only the updated branch of the tree has to be loaded.</p>
<p>(issue imported from #M4885)</p> TYPO3 Core - Feature #16900 (Closed): Use static method to integrate prototype or script.aculo.us...http://forge.typo3.org/issues/169002007-01-25T14:44:38ZOliver Haderoliver.hader@typo3.org
<p>Prototype javascript framework and script.aculo.us are used in several backend modules. But also frontend extensions could use these frameworks.<br />It could possibly happen, that there a two or more extensions which integrate on of these files by <script src="..." type="..."></script>.</p>
<p>To avoid this, it's requested to have a static method like</p>
<p>t3lib_div::includeJSprototype()</p>
<p>that takes care of it and stores a true value to a global variable like $GLOBALS['JSincluded']['prototype']. Now all scripts "know" that prototype.js was included and don't have to do that again.</p>
<p>(issue imported from #M4860)</p> TYPO3 Core - Bug #16741 (Rejected): typoLink doesn't use "type" correctly with simulateStaticDocu...http://forge.typo3.org/issues/167412006-11-27T10:35:06ZOliver Haderoliver.hader@typo3.org
<p>Imagine a TypoScript configuration like the following and simulateStaticDocuments enabled:</p>
<p>page.10 = TEXT<br />page.10 {<br /> stdWrap = 1<br /> stdWrap.typolink {<br /> returnLast = url<br /> useCacheHash = 1<br /> parameter.data = tsfe:id<br /> additionalParams = &type=5<br /> }<br />}</p>
<p>You would get something like this as link-URL:</p>
<p>SomePage.13+M5bd9214a8c2.0.html?&type=5</p>
<p>If a user clicks that link, he isn't forward to typeNum "5" as defined, but to the regular typeNum "0". So we would expect to have a link like the following one:</p>
<p>SomePage.13.5.html</p>
<p>The MD5-Part is missing here because it was used for the "&type=5" param only.</p>
<p>The attached patch file is exactly doing this by adding an additional check to tslib_cObj::typoLink.</p>
<p>It's not only a 4.1-beta1a issue. This exists since a long time... ;-)<br />(issue imported from #M4564)</p> TYPO3 Core - Bug #16692 (Closed): htmlArea RTE conflicts on using prototyped Array objects (e.g. ...http://forge.typo3.org/issues/166922006-11-06T14:07:51ZOliver Haderoliver.hader@typo3.org
<p>TYPO3 Ver. 4.1-dev</p>
<p>In htmlarea.js there are some lines of code, that walk through an array like this:<br />for (var plugin in RTE["plugin"])</p>
<p>But some of these class variables (RTE['plugin'] is one of them) are defined as "Array", not as "Object". So, if the code from above walks through RTE['plugin'] it also processes prototyped variables, that are not really part of the JavaScript array and throws a JavaScript exception in the browser.</p>
<p>Solution: Change "new Array()" for usage on associative array to "new Object()".<br />See my experimental changeset at <a class="external" href="http://svn.t3.digitaldistrict.de/cgi-bin/trac.cgi/changeset/5716">http://svn.t3.digitaldistrict.de/cgi-bin/trac.cgi/changeset/5716</a></p>
<p>The Inline Relational Record Editing Project uses prototype.js to handle AJAX calls and to do some DOM-stuff. On using the htmlArea RTE together with Inline Relational Record Editing, the mentioned errors occur.</p>
<p>see <a class="external" href="http://wiki.typo3.org/index.php/Inline_Relational_Record_Editing">http://wiki.typo3.org/index.php/Inline_Relational_Record_Editing</a><br />(issue imported from #M4469)</p> TYPO3 Core - Bug #16642 (Closed): TCEmain: Wrong syntax on checking NEW itemshttp://forge.typo3.org/issues/166422006-10-13T13:05:20ZOliver Haderoliver.hader@typo3.org
<p>There are some lines like in class.t3lib_tcemain.php<br />if (strstr($pid_value,'NEW'))</p>
<p>The syntax for substr is<br />string substr ( string string, int start [, int length] )</p>
<p>The code shown above will always return the first argument of the substr-call.<br />I guess a "preg_match" should have been standing there.</p>
<p>olly</p>
<p>(issue imported from #M4384)</p> TYPO3 Core - Bug #16392 (Closed): Page-TSconfig ###PAGE_TSCONFIG_STR### not evaluated correctly i...http://forge.typo3.org/issues/163922006-07-21T14:47:43ZOliver Haderoliver.hader@typo3.org
<p>A plugin on Web>Page, that is normally stored in tt_content, is configurable by a flexform. That flexform has a paragraph, using a select-type to get data from a foreign table.</p>
<p>The flexform-configuration on that is a bit special:<br /><config><br /> <type>select</type><br /> <foreign_table>tx_ohhotels_hotel</foreign_table><br /> <foreign_table_where><br /> AND pages.pid = ###PAGE_TSCONFIG_ID###<br /> AND ('###PAGE_TSCONFIG_STR###' = '-' OR tx_ohhotels_hotel.exthotel REGEXP '(^|,)###PAGE_TSCONFIG_STR###(,|$)')<br /> ORDER BY tx_ohhotels_hotel.title<br /> </foreign_table_where><br /> <size>15</size><br /> <minitems>0</minitems><br /> <maxitems>500</maxitems><br /></config></p>
<p>And on Page-TSconfig we have:<br />TCEFORM.tt_content.pi_flexform.PAGE_TSCONFIG_ID = 474<br />TCEFORM.tt_content.pi_flexform.PAGE_TSCONFIG_STR = 1</p>
<p>If you have a look to the image attached, you can see, that the "Items" on the right side are shown correctly. But if chose some of the available items, save and reload the page, this selected items should be visible under "Selected:" - but here they are not!</p>
<p>To get more in detail, here are the performed SQL-queries (depending on the flexform-structure above):</p>
<p>1) This is a WRONG query, trying to get the selected-fields:<br />SELECT tx_ohhotels_hotel.uid,tx_ohhotels_hotel.title,tx_ohhotels_hotel.hidden<br />FROM tx_ohhotels_hotel,pages<br />WHERE pages.uid=tx_ohhotels_hotel.pid<br />AND pages.deleted=0 AND tx_ohhotels_hotel.deleted=0 AND 1=1<br />AND pages.pid = 0<br />AND ('' = '-' OR tx_ohhotels_hotel.exthotel REGEXP '(^|,)(,|$)')<br />ORDER BY tx_ohhotels_hotel.title</p>
<p>If you compare this query to the flexform-configuration, you can see, that the ###PAGE_TSCONFIG_STR### and ###PAGE_TSCONFIG_ID### are not correctly replaced by the configured values in Page-TSconfig.</p>
<p>2) And this is the correct query, used to get the items on the right side:<br />SELECT tx_ohhotels_hotel.uid,tx_ohhotels_hotel.title,tx_ohhotels_hotel.hidden<br />FROM tx_ohhotels_hotel,pages<br />WHERE pages.uid=tx_ohhotels_hotel.pid<br />AND pages.deleted=0 AND tx_ohhotels_hotel.deleted=0 AND 1=1<br />AND pages.pid = 474<br />AND ('1' = '-' OR tx_ohhotels_hotel.exthotel REGEXP '(^|,)1(,|$)')<br />ORDER BY tx_ohhotels_hotel.title</p>
<p>I think the queries for rendering the "Items:" and the "Selected:" part (as shown in the image) are composed differently. For "Selected:" the marker substituion is missing.</p>
<p>(issue imported from #M3906)</p> TYPO3 Core - Bug #15855 (Closed): TCEFORM.tt_content.CType.removeItems not applied to db_new_cont...http://forge.typo3.org/issues/158552006-03-18T15:57:40ZOliver Haderoliver.hader@typo3.org
<p>The following value defined in TSconfig of any page is not applied to db_new_content_el.php:<br />TCEFORM.tt_content.CType.removeItems = html,div,text</p>
<p>If I select "New Content Element" at Web>Page the wizard shows icons of removed items. On selecting a denied item the next page tells me '[INVALID VALUE ("html") ]' at the pull down menu of "Type".</p>
<p>In typo3/sysext/cms/layout/db_new_content_el.php is a function removeInvalidElements(&$wizardItems) which should additionally check the TSconfig of the current page and - if necessary - remove the denied CTypes.</p>
<p>If I'm wrong, please let me know.</p>
<p>(issue imported from #M2918)</p>