TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692011-03-21T11:12:55ZTYPO3 Forge
Redmine TYPO3 Core - Bug #13941 (Closed): Removing child records in a workspace does not workhttp://forge.typo3.org/issues/139412011-03-21T11:12:55ZOliver Haderoliver.hader@typo3.org
<p>see <a class="external" href="http://bugs.typo3.org/view.php?id=17981">http://bugs.typo3.org/view.php?id=17981</a><br />see <a class="external" href="https://review.typo3.org/#change,1195">https://review.typo3.org/#change,1195</a></p>
<p>Since the bugfix for this issue also contains modifications in the "version" extension, it's posted here as well.<br />Once the whole issue was reviewed, it will be split up to the accordant repositories (Core and Version).</p> TYPO3 Core - Bug #12853 (Closed): Use functionality of workspaces libraries in the Corehttp://forge.typo3.org/issues/128532011-02-07T18:30:52ZOliver Haderoliver.hader@typo3.org
<p>In the TYPO3 Core there are several workspaces related SQL queries that might have accordant functions in the workspace libraries.<br />Thus, if the functionality is already there, we should use it - however it has to be ensured, that the queries are really the same.</p> TYPO3 Core - Bug #12615 (Closed): Dependencies in sysext 'version' and 'workspaces'http://forge.typo3.org/issues/126152011-01-28T14:29:29ZOliver Haderoliver.hader@typo3.org
<p>See <a class="external" href="http://bugs.typo3.org/view.php?id=17355">http://bugs.typo3.org/view.php?id=17355</a></p> TYPO3 Core - Bug #11833 (Closed): Sorting order of IRRE records is wrong after publishinghttp://forge.typo3.org/issues/118332011-01-01T19:48:47ZOliver Haderoliver.hader@typo3.org
Imagine the following scenario:
<ul>
<li>existing page record with an IRRE field (use irre_tutorial to reproduce, there's also a test case for this)</li>
<li>one child record is existing in live workspace</li>
<li>add new child records in custom workspace</li>
<li>publish them</li>
</ul>
<p>The result is, that the sorting order of those child records is wrong, since sorting is applied in t3lib_loadBDgroup->writeForeignField() which gets called when not all records have been processed. The solution is to recall writeForeignField() with a remapAction after all database operations.</p> TYPO3 Core - Bug #11218 (Closed): Workspaces Module shall be shown after Versioning Modulehttp://forge.typo3.org/issues/112182010-12-02T01:48:17ZOliver Haderoliver.hader@typo3.org
<p>Since the system extension version is required for the workspaces extension, the new workspaces module shall be shown in the navigation frame below the "versioning" module - currently it's show at the top of the "Web" modules.</p> 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 - Bug #11144 (Closed): Records that belong to a particular workspace shall be removed ...http://forge.typo3.org/issues/111442010-11-29T19:19:32ZOliver Haderoliver.hader@typo3.org
<p>Records that belong to a particular workspace shall be removed when the workspace is removed.<br />This shall be implemented as TCEmain hook, that removes records with the accordant t3ver_wsid on removing a sys_workspaces record. To be able to use the history, this shall also use TCEmain to remove those records.</p> TYPO3 Core - Bug #11143 (Closed): Editing workspaces record shows PHP warninghttp://forge.typo3.org/issues/111432010-11-29T19:15:18ZOliver Haderoliver.hader@typo3.org
<p>PHP Warning<br />PHP Warning: parse_url(/typo3/alt_doc.php?returnUrl=http://myhost.com/typo3/mod.php?M=web_WorkspacesWorkspaces&workspace=2&tx_workspaces_web_workspacesworkspaces%5Baction%5D=index&tx_workspaces_web_workspacesworkspaces%5Bcontroller%5D=Review&id=0&edit[pages]<sup><a href="#fn212">212</a></sup>=edit) [function.parse-url]: Unable to parse URL in typo3/alt_doc.php line 216</p>
<p>-> returnUrl shall be URL encoded</p> TYPO3 Core - Bug #11142 (Closed): The 'All' tab throws Exception 'No such workspace defined'http://forge.typo3.org/issues/111422010-11-29T19:09:09ZOliver Haderoliver.hader@typo3.org
<p>Select the 'All' tab and get an Exception 'No such workspace defined' thrown in tx_Workspaces_Service_Workspaces::getWorkspaceTitle<br />The precondition is that there are records which belong to a workspace that does not exist anymore.</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> TYPO3 Core - Bug #15850 (Closed): Symbolic link to tslib in dummy package is missinghttp://forge.typo3.org/issues/158502006-03-17T19:30:21ZOliver Haderoliver.hader@typo3.org
<p>I'm using TMENU_LAYERS and included the necessary file with<br />"page.includeLibs.tmenu_layers = media/scripts/tmenu_layers.php" in TypoScript.</p>
<p>In 3.8.1 dummy package there were several symbolic links in the root of that package:<br />media -> tslib/media<br />tslib -> typo3_src/tslib</p>
<p>Since the file structure changed in 4.0rc1 there are two ways to work around:</p>
<p>1) create the symlinks<br />media -> tslib/media<br />tslib -> typo3_src/typo3/sysext/cms/tslib</p>
<p>2) use "page.includeLibs.tmenu_layers = typo3_src/typo3/sysext/cms/tslib/media/scripts/tmenu_layers.php" in TypoScript</p>
<p>(issue imported from #M2911)</p>