TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692010-11-30T14:00:43ZTYPO3 Forge
Redmine 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 - Feature #9754 (Rejected): Module: Implement Workspaces List tabhttp://forge.typo3.org/issues/97542010-09-16T12:01:32ZOliver Haderoliver.hader@typo3.org
<p>Implement Workspaces List tab</p> TYPO3 Core - Feature #1834 (Closed): Recycler: Integrate Lost+Found possibiliteshttp://forge.typo3.org/issues/18342008-10-26T22:15:18ZOliver Haderoliver.hader@typo3.org
Imagine a record is still available in the database and not marked as deleted (deleted=0). However the accordant parent element was deleted (removed completely or marked as deleted). These parent elements could be:
<ul>
<li>a page (direct parent or any other page ancestor) that was deleted</li>
<li>a default language record that was deleted (translated records, e.g. spanish, are not marked as deleted)</li>
</ul>
<p>All these records with no correct reference to an existing resource should be displayed as "Lost+Found" with the possibilites to delete them as well or to move the to another page.</p> TYPO3 Core - Bug #18646 (Closed): Combination view not possible with symmetric relationshttp://forge.typo3.org/issues/186462008-04-19T19:45:48ZOliver Haderoliver.hader@typo3.org
<p>The combinations view, which allows one to edit a record directly which is again only related by an intermediate table, does not work.<br />Furthermore it a option for configuring a selector for the symmetric side is missing ("symmetric_selector") and endless recursions have to be checked in this context then.</p>
<p>(issue imported from #M8165)</p> TYPO3 Core - Feature #17638 (Closed): Integrate possibility to show content elements depending on...http://forge.typo3.org/issues/176382007-09-29T15:29:16ZOliver Haderoliver.hader@typo3.org
<p>Perhaps we should start with an example before an abstract:<br />Imagine, that you're running a TYPO3 site with several domains (mysite.com, shop.mysite.com, partner.mysite.com) that are all using the same page tree. Now, a content element shall only be visible if the website user hits your site using a special domain (e.g. partner.mysite.com). That content element show some additional information and isn't visible on the other pages.</p>
<p>What you can do currently, is to use some TypoScript conditions or a redirect using the domain record of TYPO3. But there isn't yet a possibility to assign such conditions to single content elements.</p>
<p>Assigning a domain was just an example, this could be anything, e.g. GET-parameter, systemtime, server-environment-variable. I tend to call this a "rule" or "front-end rules" (fe_rules).</p>
<p>(issue imported from #M6419)</p> TYPO3 Core - Feature #17615 (Closed): Integrate possibility to override TCA columns depending on ...http://forge.typo3.org/issues/176152007-09-18T18:14:02ZOliver Haderoliver.hader@typo3.org
<p>Currently it's possible to override field properties of existing TCA columns by using Page TSconfig. Settings, depending on the type of a record, can be overridden if that property was allowed to be overridden.</p>
<p>This issue is concerning the possibility to do basically the same, but in TCA (not in Page TSconfig) and also for properties that were not allowed to be overridden.</p>
<p>The following example re-uses the image field of tt_content and defines that only one image could be added:<br />$TCA['tt_content']['types'][$_EXTKEY.'_pi1']['overrideColumns'] = array(<br /> 'image' => array('config' => array('maxitems' => 1)),<br />);</p>
<p>(issue imported from #M6365)</p> TYPO3 Core - Feature #17434 (Closed): Allow more than one parent field pointing to the same child...http://forge.typo3.org/issues/174342007-07-04T14:23:46ZOliver Haderoliver.hader@typo3.org
<p>The following field configuration of a parent record in TCE is currently not possible:</p>
<p>'columns' => array(<br /> 'firstchildren' => array(<br /> 'config' => array(<br /> 'type' => 'inline',<br /> 'foreign_table' => 'tx_myext_child',<br /> 'foreign_field' => 'parent',<br /> ),<br /> ),<br /> 'secondchildren' => array(<br /> 'config' => array(<br /> 'type' => 'inline',<br /> 'foreign_table' => 'tx_myext_child',<br /> 'foreign_field' => 'parent',<br /> ),<br /> ),<br />),</p>
<p>The reason is, that with foreign_field the children are selected by the table and the uid in the field 'parent'. Thus, the children are not identified to with <em>field</em> in the parent record they belong.</p>
<p>The feature request is to have a new TCA property likle 'foreign_fieldfield' that defines a field on the child side storing the fieldname of the parent record creating the child.</p>
<p>The attached extension "test_required" reproduces this behaviour.</p>
<p>(issue imported from #M5897)</p> TYPO3 Core - Feature #17108 (Closed): Support secure database connections (e.g. MySQL over SSL)http://forge.typo3.org/issues/171082007-03-10T11:26:43ZOliver Haderoliver.hader@typo3.org
<p>It would be great to have the feature to connect to a server somewhere in the internet by using a secure connection to the database. For the beginning this feature should be available for MySQL. In future mysqli and other DBMS could be integrated - but this is more related to DBAL.</p>
<p><a class="external" href="http://dev.mysql.com/doc/refman/5.0/en/secure-connections.html">http://dev.mysql.com/doc/refman/5.0/en/secure-connections.html</a><br />(issue imported from #M5187)</p> TYPO3 Core - Feature #17102 (Rejected): EM should inform admin if a local extension is outdated a...http://forge.typo3.org/issues/171022007-03-09T14:35:21ZOliver Haderoliver.hader@typo3.org
<p>This issue is more related to system extension as to others.<br />Imagine a site was running TYPO3 4.0.1 for several month and e.g. the RTEhtmlarea was installed locally from TER (with security patches, etc.). Now the admin decides to update to TYPO3 4.1.0. The RTEhtml will not work anymore, because the local installation of this extension (made for TYPO3 4.0.x) is not compatible to TYPO3 4.1.0 anymore.</p>
<p>The Extension Manager (perhaps additionally the update wizard of the install tool) should inform the admin, that the newer system extension is required and that he has to uninstall his local extension.</p>
<p>Just read bug-id <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: RTE does not load (Closed)" href="http://forge.typo3.org/issues/17082">#17082</a> to see what could happen.</p>
<p>(issue imported from #M5178)</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 - 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 - Feature #16915 (Closed): Integrate function to determine extension key from a table ...http://forge.typo3.org/issues/169152007-01-29T12:17:30ZOliver Haderoliver.hader@typo3.org
<p>Sometimes it could be necessarry to know which table belongs to which extension key. If such a mapping is integrated, the inverse function is also possible.</p>
<p>e.g.<br />table 'tx_myextension_data' -> extension 'my_extension'<br />extension 'my_extension' -> tables 'tx_myextension_data,tx_myextension_categories'</p>
<p>The results should be stored in $GLOBALS['TYPO3_LOADED_EXT'][<extKey>]['tables'] and $GLOBALS['TYPO3_LOADED_TABLES'][<tableName>].</p>
<p>(issue imported from #M4877)</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 - Feature #16482 (Rejected): Extending $TCA[$table]['ctrl']['thumbnail'] to use more t...http://forge.typo3.org/issues/164822006-08-21T13:41:38ZOliver Haderoliver.hader@typo3.org
<p>Generally the thumbnail field in the TCA ctrl section is used like this:</p>
<p>$TCA["tx_myext"] = Array (<br /> "ctrl" => Array (<br /> ...<br /> 'thumbnail' => 'image',<br /> ...<br /> ),<br />);</p>
<p>This diff provides a solution, to use more fields, separated by comma, e.g.</p>
<p>$TCA["tx_myext"] = Array (<br /> "ctrl" => Array (<br /> ...<br /> 'thumbnail' => 'image,map,icon',<br /> ...<br /> ),<br />);</p>
<p>See the following diff file.</p>
<p>(issue imported from #M4079)</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>