TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692019-08-20T13:57:15ZTYPO3 Forge
Redmine TYPO3 Core - Feature #88985 (Closed): Add more descriptive message than "There are no records on ...http://forge.typo3.org/issues/889852019-08-20T13:57:15ZPascal Quernerpq@paskl.de
<p>Having a page with multiple records of different types (say ext:news, together with tt_content) and you delete all items of any record type, the information message you get from \TYPO3\CMS\Recordlist\Controller\RecordListController::main is "There are no records on this page"</p>
<pre><code class="php syntaxhl" data-language="php"> <span class="nv">$flashMessage</span> <span class="o">=</span> <span class="nc">GeneralUtility</span><span class="o">::</span><span class="nf">makeInstance</span><span class="p">(</span>
<span class="nc">FlashMessage</span><span class="o">::</span><span class="n">class</span><span class="p">,</span>
<span class="nv">$lang</span><span class="o">-></span><span class="nf">getLL</span><span class="p">(</span><span class="s1">'noRecordsOnThisPage'</span><span class="p">),</span>
<span class="s1">''</span><span class="p">,</span>
<span class="nc">FlashMessage</span><span class="o">::</span><span class="no">INFO</span>
<span class="p">);</span>
<span class="cd">/** @var \TYPO3\CMS\Core\Messaging\FlashMessageService $flashMessageService */</span>
<span class="nv">$flashMessageService</span> <span class="o">=</span> <span class="nc">GeneralUtility</span><span class="o">::</span><span class="nf">makeInstance</span><span class="p">(</span><span class="nc">FlashMessageService</span><span class="o">::</span><span class="n">class</span><span class="p">);</span>
<span class="cd">/** @var \TYPO3\CMS\Core\Messaging\FlashMessageQueue $defaultFlashMessageQueue */</span>
<span class="nv">$defaultFlashMessageQueue</span> <span class="o">=</span> <span class="nv">$flashMessageService</span><span class="o">-></span><span class="nf">getMessageQueueByIdentifier</span><span class="p">();</span>
<span class="nv">$defaultFlashMessageQueue</span><span class="o">-></span><span class="nf">enqueue</span><span class="p">(</span><span class="nv">$flashMessage</span><span class="p">);</span>
</code></pre>
<p>Since this page may have more records of other types that message is not really true. (It does not have records of type %s any more)</p>
<p>In \TYPO3\CMS\Recordlist\RecordList\DatabaseRecordList::generateList the htmlCode gets generated and checked of course only for this table you currently selected is having any records. The result is null, and therefore the information text is displayed.</p>
<p>Steps to reproduce:</p>
<p>1) Create page and create multiple records of different record types (example ext:news and normal content elements living in tt_content)<br />2) In Web->List view select you want to see only records of type X <br />3) Delete all records (via clipboard manager or deleted one by one)<br />4) You will see the information message "There are no records on this page"</p>
<p>Debugging:</p>
<p>Use GeneralUtility::_GP('table') to get the wanted table name, normalize it (somehow) and printf it to the information message.<br />Or \TYPO3\CMS\Recordlist\RecordList\DatabaseRecordList::generateList knows the wanted tablename(s), too.</p>
<pre><code class="php syntaxhl" data-language="php"> <span class="c1">// Checking if the table should be rendered:</span>
<span class="c1">// Checks that we see only permitted/requested tables:</span>
<span class="k">if</span> <span class="p">(</span><span class="nv">$this</span><span class="o">-></span><span class="n">table</span> <span class="o">&&</span> <span class="nv">$tableName</span> <span class="o">!==</span> <span class="nv">$this</span><span class="o">-></span><span class="n">table</span>
<span class="o">||</span> <span class="nv">$this</span><span class="o">-></span><span class="n">tableList</span> <span class="o">&&</span> <span class="o">!</span><span class="nc">GeneralUtility</span><span class="o">::</span><span class="nf">inList</span><span class="p">(</span><span class="nv">$this</span><span class="o">-></span><span class="n">tableList</span><span class="p">,</span> <span class="nv">$tableName</span><span class="p">)</span>
<span class="o">||</span> <span class="o">!</span><span class="nv">$backendUser</span><span class="o">-></span><span class="nf">check</span><span class="p">(</span><span class="s1">'tables_select'</span><span class="p">,</span> <span class="nv">$tableName</span><span class="p">)</span>
<span class="p">)</span> <span class="p">{</span>
<span class="nv">$hideTable</span> <span class="o">=</span> <span class="kc">true</span><span class="p">;</span>
<span class="p">}</span>
</code></pre> TYPO3 Core - Bug #88973 (Rejected): ext:seo does not work for complex extbase routeenhancershttp://forge.typo3.org/issues/889732019-08-18T12:48:48ZPascal Quernerpq@paskl.de
<p>This issue is partially related to <a class="external" href="https://forge.typo3.org/issues/87016">https://forge.typo3.org/issues/87016</a><br />However, I am creating a new issue because its missing that the comlex routeEnhancers do not work, when you use a field (like year) which results from a data row you can not simple fetch from the database (instead is fetched from crdate field, which must be converted from timestamp to year only)</p>
<p>My proposed change was <a class="external" href="https://review.typo3.org/c/Packages/TYPO3.CMS/+/61505">https://review.typo3.org/c/Packages/TYPO3.CMS/+/61505</a><br />However, as Andreas Fernandez said in the code review, this opens the application to execute any functions which are programmed into the typoscript snippet.</p>
<p>Question now is, since its security related, how do we handle this?<br />I could make the PR read out an additional (GLOBALS) array which contains valid function names to be used, but that would only shift the issue to a new place imho. An attacker can modify that array and still use everything he wanted.<br />However, an attacker can do anything with typoscript, access, and php anyway.</p>
<p>Why is this needed anyway?<br />The easiest example I can think of, is the usage of ext:news. In this, you can routeEnhancer your URLs to contain the year/month/date values. You must set "hrdate" to "1" in the ts of ext:news for the extensions viewhelper to produce such URLs in the frontend (to include the GET parameters for month, year and date).<br />If you have that, ext:seo typoscript is unable to parse, or add that to the GET parameters for typoLink to build the URL properly.</p>
<p>Why?<br />Because month/date/year is build not from a column found in the database row. Instead its build from the "crdate" (timestamp) and formatted to only contain the month. Because /seo/Classes/XmlSitemap/RecordsXmlSitemapDataProvider.php is only able to fetch column data, but not perform any logic on it, I proposed the change previously mentioned.</p>
<p>Snippets:<br />RouteEnhancer config which will enhance ext:news URI to be year/month/date/newstitle</p>
<pre><code class="yaml syntaxhl" data-language="yaml"> <span class="na">News</span><span class="pi">:</span>
<span class="na">type</span><span class="pi">:</span> <span class="s">Extbase</span>
<span class="na">extension</span><span class="pi">:</span> <span class="s">News</span>
<span class="na">plugin</span><span class="pi">:</span> <span class="s">Pi1</span>
<span class="na">routes</span><span class="pi">:</span>
<span class="pi">-</span>
<span class="na">routePath</span><span class="pi">:</span> <span class="s1">'</span><span class="s">/{tag-name}'</span>
<span class="na">_controller</span><span class="pi">:</span> <span class="s1">'</span><span class="s">Tag::show'</span>
<span class="na">_arguments</span><span class="pi">:</span>
<span class="na">tag-name</span><span class="pi">:</span> <span class="s">tag</span>
<span class="na">requirements</span><span class="pi">:</span>
<span class="na">tag-name</span><span class="pi">:</span> <span class="s1">'</span><span class="s">^[a-zA-Z0-9].*$'</span>
<span class="pi">-</span>
<span class="na">routePath</span><span class="pi">:</span> <span class="s1">'</span><span class="s">/page-{page}'</span>
<span class="na">_controller</span><span class="pi">:</span> <span class="s1">'</span><span class="s">News::list'</span>
<span class="na">_arguments</span><span class="pi">:</span>
<span class="na">page</span><span class="pi">:</span> <span class="s1">'</span><span class="s">@widget_0/currentPage'</span>
<span class="na">requirements</span><span class="pi">:</span>
<span class="na">page</span><span class="pi">:</span> <span class="s">\d+</span>
<span class="pi">-</span>
<span class="na">routePath</span><span class="pi">:</span> <span class="s1">'</span><span class="s">/{date-year}/{date-month}/{date-day}/{news-title}'</span>
<span class="na">_controller</span><span class="pi">:</span> <span class="s1">'</span><span class="s">News::detail'</span>
<span class="na">_arguments</span><span class="pi">:</span>
<span class="na">news-title</span><span class="pi">:</span> <span class="s">news</span>
<span class="na">date-month</span><span class="pi">:</span> <span class="s">month</span>
<span class="na">date-year</span><span class="pi">:</span> <span class="s">year</span>
<span class="na">date-day</span><span class="pi">:</span> <span class="s">day</span>
<span class="pi">-</span>
<span class="na">routePath</span><span class="pi">:</span> <span class="s1">'</span><span class="s">/{date-year}'</span>
<span class="na">_controller</span><span class="pi">:</span> <span class="s1">'</span><span class="s">News::list'</span>
<span class="na">_arguments</span><span class="pi">:</span>
<span class="na">date-month</span><span class="pi">:</span> <span class="s">overwriteDemand/month</span>
<span class="na">date-year</span><span class="pi">:</span> <span class="s">overwriteDemand/year</span>
<span class="na">page</span><span class="pi">:</span> <span class="s1">'</span><span class="s">@widget_0/currentPage'</span>
<span class="na">requirements</span><span class="pi">:</span>
<span class="na">date-year</span><span class="pi">:</span> <span class="s">\d+</span>
<span class="pi">-</span>
<span class="na">routePath</span><span class="pi">:</span> <span class="s1">'</span><span class="s">/{date-year}/page-{page}'</span>
<span class="na">_controller</span><span class="pi">:</span> <span class="s1">'</span><span class="s">News::list'</span>
<span class="na">_arguments</span><span class="pi">:</span>
<span class="na">date-year</span><span class="pi">:</span> <span class="s">overwriteDemand/year</span>
<span class="na">page</span><span class="pi">:</span> <span class="s1">'</span><span class="s">@widget_0/currentPage'</span>
<span class="na">requirements</span><span class="pi">:</span>
<span class="na">date-year</span><span class="pi">:</span> <span class="s">\d+</span>
<span class="na">page</span><span class="pi">:</span> <span class="s">\d+</span>
<span class="pi">-</span>
<span class="na">routePath</span><span class="pi">:</span> <span class="s1">'</span><span class="s">/{date-year}/{date-month}'</span>
<span class="na">_controller</span><span class="pi">:</span> <span class="s1">'</span><span class="s">News::list'</span>
<span class="na">_arguments</span><span class="pi">:</span>
<span class="na">date-month</span><span class="pi">:</span> <span class="s">overwriteDemand/month</span>
<span class="na">date-year</span><span class="pi">:</span> <span class="s">overwriteDemand/year</span>
<span class="na">page</span><span class="pi">:</span> <span class="s1">'</span><span class="s">@widget_0/currentPage'</span>
<span class="na">requirements</span><span class="pi">:</span>
<span class="na">date-month</span><span class="pi">:</span> <span class="s">\d+</span>
<span class="na">date-year</span><span class="pi">:</span> <span class="s">\d+</span>
<span class="pi">-</span>
<span class="na">routePath</span><span class="pi">:</span> <span class="s1">'</span><span class="s">/{date-year}/{date-month}/page-{page}'</span>
<span class="na">_controller</span><span class="pi">:</span> <span class="s1">'</span><span class="s">News::list'</span>
<span class="na">_arguments</span><span class="pi">:</span>
<span class="na">date-month</span><span class="pi">:</span> <span class="s">overwriteDemand/month</span>
<span class="na">date-year</span><span class="pi">:</span> <span class="s">overwriteDemand/year</span>
<span class="na">page</span><span class="pi">:</span> <span class="s1">'</span><span class="s">@widget_0/currentPage'</span>
<span class="na">requirements</span><span class="pi">:</span>
<span class="na">date-month</span><span class="pi">:</span> <span class="s">\d+</span>
<span class="na">date-year</span><span class="pi">:</span> <span class="s">\d+</span>
<span class="na">page</span><span class="pi">:</span> <span class="s">\d+</span>
<span class="na">defaultController</span><span class="pi">:</span> <span class="s1">'</span><span class="s">News::list'</span>
<span class="na">defaults</span><span class="pi">:</span>
<span class="na">page</span><span class="pi">:</span> <span class="s1">'</span><span class="s">0'</span>
<span class="na">date-month</span><span class="pi">:</span> <span class="s1">'</span><span class="s">'</span>
<span class="na">date-year</span><span class="pi">:</span> <span class="s1">'</span><span class="s">'</span>
<span class="na">aspects</span><span class="pi">:</span>
<span class="na">news-title</span><span class="pi">:</span>
<span class="na">type</span><span class="pi">:</span> <span class="s">PersistedAliasMapper</span>
<span class="na">tableName</span><span class="pi">:</span> <span class="s">tx_news_domain_model_news</span>
<span class="na">routeFieldName</span><span class="pi">:</span> <span class="s">path_segment</span>
<span class="na">tag-name</span><span class="pi">:</span>
<span class="na">type</span><span class="pi">:</span> <span class="s">PersistedAliasMapper</span>
<span class="na">tableName</span><span class="pi">:</span> <span class="s">tx_news_domain_model_tag</span>
<span class="na">routeFieldName</span><span class="pi">:</span> <span class="s">slug</span>
<span class="na">page</span><span class="pi">:</span>
<span class="na">type</span><span class="pi">:</span> <span class="s">StaticRangeMapper</span>
<span class="na">start</span><span class="pi">:</span> <span class="s1">'</span><span class="s">1'</span>
<span class="na">end</span><span class="pi">:</span> <span class="s1">'</span><span class="s">25'</span>
<span class="na">date-month</span><span class="pi">:</span>
<span class="na">type</span><span class="pi">:</span> <span class="s">StaticValueMapper</span>
<span class="na">map</span><span class="pi">:</span>
<span class="na">januar</span><span class="pi">:</span> <span class="s1">'</span><span class="s">1'</span>
<span class="na">februar</span><span class="pi">:</span> <span class="s1">'</span><span class="s">2'</span>
<span class="na">maerz</span><span class="pi">:</span> <span class="s1">'</span><span class="s">3'</span>
<span class="na">april</span><span class="pi">:</span> <span class="s1">'</span><span class="s">4'</span>
<span class="na">mai</span><span class="pi">:</span> <span class="s1">'</span><span class="s">5'</span>
<span class="na">juni</span><span class="pi">:</span> <span class="s1">'</span><span class="s">6'</span>
<span class="na">juli</span><span class="pi">:</span> <span class="s1">'</span><span class="s">7'</span>
<span class="na">august</span><span class="pi">:</span> <span class="s1">'</span><span class="s">8'</span>
<span class="na">september</span><span class="pi">:</span> <span class="s1">'</span><span class="s">9'</span>
<span class="na">oktober</span><span class="pi">:</span> <span class="s1">'</span><span class="s">10'</span>
<span class="na">november</span><span class="pi">:</span> <span class="s1">'</span><span class="s">11'</span>
<span class="na">dezember</span><span class="pi">:</span> <span class="s1">'</span><span class="s">12'</span>
<span class="na">date-year</span><span class="pi">:</span>
<span class="na">type</span><span class="pi">:</span> <span class="s">StaticRangeMapper</span>
<span class="na">start</span><span class="pi">:</span> <span class="s1">'</span><span class="s">2019'</span>
<span class="na">end</span><span class="pi">:</span> <span class="s1">'</span><span class="s">2030'</span>
<span class="na">date-day</span><span class="pi">:</span>
<span class="na">type</span><span class="pi">:</span> <span class="s">StaticRangeMapper</span>
<span class="na">start</span><span class="pi">:</span> <span class="s1">'</span><span class="s">01'</span>
<span class="na">end</span><span class="pi">:</span> <span class="s1">'</span><span class="s">31'</span>
</code></pre>
<p>Proposed TS code for ext:seo to make the proposed PR work:<br /><pre><code class="text syntaxhl" data-language="text">plugin.tx_seo.config {
xmlSitemap {
sitemaps {
news {
provider = TYPO3\CMS\Seo\XmlSitemap\RecordsXmlSitemapDataProvider
config {
table = tx_news_domain_model_news
additionalWhere =
sortField = sorting
lastModifiedField = tstamp
pid = 26
recursive = 2
url {
pageId = 25
fieldToParameterMap {
uid = tx_news_pi1[news]
}
fieldToParameterMapDynamic {
day {
field = crdate
func = strftime
param = %e
as = tx_news_pi1[day]
}
month {
field = crdate
func = strftime
param = %-m
as = tx_news_pi1[month]
}
year {
field = crdate
func = strftime
param = %Y
as = tx_news_pi1[year]
}
}
additionalGetParameters {
tx_news_pi1.controller = News
tx_news_pi1.action = detail
}
useCacheHash = 1
}
}
}
}
}
}
</code></pre></p> TYPO3 Core - Bug #88950 (Closed): Cooke "fe_typo_user" is set when widget.autocomplete is usedhttp://forge.typo3.org/issues/889502019-08-12T11:11:32ZPascal Quernerpq@paskl.de
<p>Hey,</p>
<p>I have a site which needs the user consent before any cookies can be set. (Opt-In instead of Opt-Out)<br />However, the Cookie for "fe_typo_user" is still set, even tho it should not be the case anylonger (issue <a class="external" href="https://forge.typo3.org/issues/84866">https://forge.typo3.org/issues/84866</a>).<br />If you happen to use the widget "autocomplete" it will generate you the cookie.</p>
<p>Tested against a page with multiple plugins inserted and only the autocomplete widget triggers the cookie.<br />I tried debugging the issue but I could not see any middleware adding the cookie or somewhere around request.</p>
<p>Any help is appreciated.<br />Tested against 9.5.8 with PHP 7.3. <br />I've installed the extension "gdpr" in the hopes it would fix the issue, but it didnt.</p>
<p>~Pascal</p> TYPO3 Core - Bug #88929 (New): TCAM:N relation -> leave record with unsaved changes redirects to ...http://forge.typo3.org/issues/889292019-08-07T15:34:32ZPascal Quernerpq@paskl.de
<p>Hey,</p>
<p>changing items on a TCA m:n table relation and then trying to add create new items from a specfic type (the "+" button) will show the modal "you are leaving the page with unsaved changes". If you click "save and close" you expect to go to the wizard which will enable you to create a new item. you will get redirect to the list view instead.</p>
<p>I've shot a video which I think can describe this better</p>
<p>Possibly related to <a class="external" href="https://forge.typo3.org/issues/88875">https://forge.typo3.org/issues/88875</a>, however I have not yet tried the fix.</p>
<p>- Pascal</p> TYPO3 Core - Bug #88875 (Closed): Modal Page altered not shown everytimehttp://forge.typo3.org/issues/888752019-08-01T10:02:16ZPascal Quernerpq@paskl.de
<p>When you alter data in a CE and leave the CE via "Close" button, it shows a modal with "You have unsaved changes, would you like to save and close, continue editing, or discard them".</p>
<p>However, this is not always shown.</p>
<p>So far I have not identify when it shows and when not, however It works on some flexform fields and on some it doesnt.<br />For instance the ext:news (version 7.2.0) adds a flexform field "Max width for media elements" for FE Plugin "List of selected items". If you enter data in there and decide to close the CE, it shows the modal.</p>
<p>If you enter data via the wizard for the field "PageId for single news display" however, the modal is not shown and you simply silently discard the changes to the plugin - leaving the CE without saving.</p>
<p>So my best guess its some kind of flexform wizard thing maybe.</p>
<p>Tested versions:<br />Standard ext:news 7.2.0<br />TYPO3 9.5.8<br />nginx-fpm with php 7.2.19</p> TYPO3 Core - Bug #88358 (Closed): CLI Scheduler not evaluating extbase overwritten classeshttp://forge.typo3.org/issues/883582019-05-15T11:01:04ZPascal Quernerpq@paskl.de
<p>We overwrite couple of classses of pxa_social_feed [1] to extend functionality like so:</p>
<pre>
config.tx_extbase {
persistence {
classes {
Pixelant\PxaSocialFeed\Domain\Model {
subclasses {
0 = snip\snip\Domain\Model\PxaFeed
}
}
snip\snip\Domain\Model\PxaFeed {
mapping {
tableName = tx_pxasocialfeed_domain_model_feed
# recordType = 0
}
}
}
}
objects {
Pixelant\PxaSocialFeed\Controller\FeedsController.className = snip\snip\Controller\PxaFeedsController
Pixelant\PxaSocialFeed\Domain\Repository\FeedRepository.className = snip\snip\Domain\Repository\PxaFeedRepository
}
}
</pre>
<p>And we also add a new task for ext:scheduler which is extending the import task of ext:pxa_social_feed [0] (we simply call our taskutlity there and not the original, but keep all the original functionality (like getting the configuration)).</p>
<p>In ImportTaskUtility.php of ext:pxa_social_feed (a php class which is used for ext:scheduler) a new model is either fetched from the database or created for you via objectmanager [2].<br />This works all well in CGI mode, when you call that scheduler manually. However, in CLI mode the fetched class is of original type (of ext:pxa_social_feed) and not of extended type, and therefore will be ignored to add with exception code 1248363335 .[3]</p>
<p>As a hotfix I delcared the method 'saveInstagramFeed' of ext:pxa_social_feed protected in a fork which allowed me to overwrite it (and ask the objectmanager to fetch my model always). [4]</p>
<p>Is there something I did wrong with extending the classes or does CLI just not care about extbase config?</p>
<p>I've only tested this against TYPO3 9.5.5 and 9.5.6, no earlier versions.</p>
<p>[0] <a class="external" href="https://github.com/pixelant/pxa_social_feed/blob/v1.10.0/Classes/Task/ImportTask.php">https://github.com/pixelant/pxa_social_feed/blob/v1.10.0/Classes/Task/ImportTask.php</a><br />[1] <a class="external" href="https://github.com/pixelant/pxa_social_feed">https://github.com/pixelant/pxa_social_feed</a><br />[2] <a class="external" href="https://github.com/pixelant/pxa_social_feed/blob/v1.10.0/Classes/Utility/Task/ImportTaskUtility.php">https://github.com/pixelant/pxa_social_feed/blob/v1.10.0/Classes/Utility/Task/ImportTaskUtility.php</a>#<br />[3] <a class="external" href="https://github.com/TYPO3/TYPO3.CMS/blob/v9.5.5/typo3/sysext/extbase/Classes/Persistence/Repository.php#L77">https://github.com/TYPO3/TYPO3.CMS/blob/v9.5.5/typo3/sysext/extbase/Classes/Persistence/Repository.php#L77</a><br />[4] <a class="external" href="https://github.com/pixelant/pxa_social_feed/blob/v1.10.0/Classes/Utility/Task/ImportTaskUtility.php#L418">https://github.com/pixelant/pxa_social_feed/blob/v1.10.0/Classes/Utility/Task/ImportTaskUtility.php#L418</a></p> TYPO3 Core - Bug #87711 (Closed): Site Management site not working when you delete only available...http://forge.typo3.org/issues/877112019-02-14T09:54:45ZPascal Quernerpq@paskl.de
<p>Hey,</p>
<p>I know this sounds weird and should never be really an issue. But when having a single language TYPO3 instance with a working site configuration and you delete the only language configuration from that it won't let you save the site configuration because "Available languages for this site" is empty and cannot be (re)added.<br />If you remove that language configuration it should be readded back to the list.</p>
<p>The only workaround for this is to completely delete the site configuration and start over.</p>
<p>Tested only on TYPO3 9.5.4 running nginx with PHP 7.3.</p> TYPO3 Core - Bug #86565 (Closed): "Dump autoload" reports green when in composer modehttp://forge.typo3.org/issues/865652018-10-04T10:26:44ZPascal Quernerpq@paskl.de
<p>When in composer-mode with TYPO3 9.5 LTS trying to "dump autoload" from the Install Tool webview, the response is "Skipped generating additional class loading information in composer mode." but is reported as "green".</p>
<p>I suggest changing the green reponse to yellow to indicate a warning that nothing had been done, because its not possible to dump autoload with composer usage.</p>
<p>OR</p>
<p>Better yet, hide that option all togehter (as it does nothing).</p> TYPO3 Core - Bug #51917 (Closed): Recursively delete folder in file module, marker didnt get repl...http://forge.typo3.org/issues/519172013-09-11T15:54:30ZPascal Quernerpq@paskl.de
<p>Hello core team,</p>
<p>heres an odd bug and easy to reproduce:</p>
<p>In the file module I want to recursively delete an folder. That works by the way, but I get this as an result page:<br />Folder deleted<br />The folder "images" was successfully deleted.<br />Folder not found.<br />The folder "1:/user_upload/images/examples/" cannot be accessed. Trying to use parent folder(s).</p>
<p>You can see that one better in this screenshot:<br /><a class="external" href="http://abload.de/img/typo3bugrecursivedeleoepgc.png">http://abload.de/img/typo3bugrecursivedeleoepgc.png</a></p>
<p>Note that a marker is not replaced and the error message.</p>
<p>TYPO3 6.1.4</p> TYPO3 Core - Bug #51784 (Closed): Pages of top level menu are displayed even if thes are hidden i...http://forge.typo3.org/issues/517842013-09-05T17:36:53ZPascal Quernerpq@paskl.de
<p>If you create some sites in your top menu root, they may be displayed if their id's are written in <em>menu.top.pages</em>.</p> TYPO3 Core - Feature #51432 (Closed): Response when for example deleting pages from BEhttp://forge.typo3.org/issues/514322013-08-28T11:30:00ZPascal Quernerpq@paskl.de
<p>Hello,</p>
<p>I think there should be some sort of response when e.g deleting pages from BE.<br />If I delete a pagetree with some child pages which contain couple of pagecontents (30 for example) I know it will take a few seconds until they're deleted, but I would like to see some sort of "response". Even if its the loading image we know from the extension manager. Better (but probably unneeded) would be a progressbar with %.</p>
<p>Tell me what you think.</p>
<p>~Pascal</p> TYPO3 Core - Bug #49421 (Closed): Trouble login to two different typo3 6.1 instanceshttp://forge.typo3.org/issues/494212013-06-25T21:02:05ZPascal Quernerpq@paskl.de
<p>Hello,</p>
<p>I am having the problem with my Browser (tested Google Chrome, Version 27.0.1453.116 m) that when I want to login into two different backends of TYPO3 6.1 instances it wont let me login to the second instance.<br />When I try to enter my credentials (they fit, I have them in my keepass file and they work if i use them in another browser) I will just get redirected to the login page again. The cookies are set however. If I hit F5 i have to relogin, which will not work, just like the first time.</p>
<p>My other customers have different TYPO3 version running (4.5 and 4.3) and there wasnt any problem when I try to login to both BE with the same browser (different window).</p>
<p>If I however see the BE for a short moment it will kick me out again without a message. Sadly the other instance will bug out and say the session expired. If I enter my password it will disappear and I can work, for roughtly 10 seconds until the window pops up again. When I logout and relog to the instance it will not work. I have to clear browser cache and cookies - then it will work again - for one instance of course.</p>
<p>Now I have 2 local TYPO3 instances running, both 6.1 and it wont work. (XAMPP).</p>
<p>Could this be some kind of bug?<br />Tell me what info you need, I will reply as fast as possible.</p>
<p>~pascal.</p> TYPO3 Core - Bug #47990 (Closed): FE Error when Upgrading from 4.5.x to 4.5.26http://forge.typo3.org/issues/479902013-05-06T17:35:02ZPascal Quernerpq@paskl.de
<p>Hello Core Team,</p>
<p>I was upgrading my TYPO3 4.5.16 to 4.5.26 but it throws an error in FE:<br />The error:</p>
<blockquote>
<p>Warning: Unexpected character in input: '\' (ASCII=92) state=1 in /home/p.querner/public_html/xxxx/typo3_src-4.5.26/typo3/sysext/extbase/Classes/Persistence/Storage/Typo3DbBackend.php on line 854 Warning: Unexpected character in input: '\' (ASCII=92) state=1 in /home/p.querner/public_html/xxxx/typo3_src-4.5.26/typo3/sysext/extbase/Classes/Persistence/Storage/Typo3DbBackend.php on line 854 Parse error: syntax error, unexpected T_STRING in /home/p.querner/public_html/xxxx/typo3_src-4.5.26/typo3/sysext/extbase/Classes/Persistence/Storage/Typo3DbBackend.php on line 854 ></p>
</blockquote>
<p>In line 854 of said file is this:</p>
<blockquote>
<p>throw new \TYPO3\CMS\Extbase\Persistence\Generic\Exception\InconsistentQuerySettingsException('Missing storage page ids.', 1365779762);</p>
</blockquote>
<p>I changed it to</p>
<blockquote>
</blockquote>
<p>throw new TYPO3_CMS_Extbase_Persistence_Generic_Exception_InconsistentQuerySettingsException('Missing storage page ids.', 1365779762);></p>
<p>And it seems to be working fine. (5 minutes testing, FE and BE)</p>
<p>Please have a closer look at this, because I dont know why exactly it caused the problem. My guess is because of namespace which isnt available in PHP 5.2.<br />I did not test the code on PHP 5.3 systems.</p>