http://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692019-01-15T21:54:28ZTYPO3 ForgeTYPO3 Core - Bug #87452: Page Slug generation doesn't take path of parent SysFolders into accounthttp://forge.typo3.org/issues/87452?journal_id=3936322019-01-15T21:54:28ZJosef Glatzjosef.glatz@typo3.org
<ul><li><strong>Subject</strong> changed from <i>Page Slug generation doesn't take path of SysFolders into account</i> to <i>Page Slug generation doesn't take path of parent SysFolders into account</i></li></ul> TYPO3 Core - Bug #87452: Page Slug generation doesn't take path of parent SysFolders into accounthttp://forge.typo3.org/issues/87452?journal_id=4008192019-05-14T12:48:43ZWolfgang Twarochwt@plan2.net
<ul></ul><p>A solution for respecting all page types in URL generation and adding a checkbox at page level to exclude this can be found at <a class="external" href="https://github.com/b13/masi">https://github.com/b13/masi</a></p> TYPO3 Core - Bug #87452: Page Slug generation doesn't take path of parent SysFolders into accounthttp://forge.typo3.org/issues/87452?journal_id=4053192019-08-30T15:16:27ZFrank Näglerfrank.naegler@typo3.org
<ul></ul><p>SlugHelper::resolveParentPageRecord is skipping the folder, the comment of the method says:</p>
<blockquote>
<p>Fetch a parent page, but exclude spacers, recyclers and sys-folders and all doktypes > 200</p>
</blockquote>
<p>I am not sure if this behavior is intended.</p> TYPO3 Core - Bug #87452: Page Slug generation doesn't take path of parent SysFolders into accounthttp://forge.typo3.org/issues/87452?journal_id=4053212019-08-30T15:21:42ZAnonymous
<ul></ul><p>"Is it really necessary to exclude parent sysfolder pages from the automatic page slug creation?" <br />Well realURL did so. If we migrate a project from realURL we can not simply take the folders into the path!</p>
<p>At least there has to be a setting to enable it, OR Folders should not have slugs at all! Because they are not used but blocking pages from getting the path.</p>
<p>Contact[folder] -> Slug: /contact</p>
<blockquote>
<p>Contact[page] -> Slug: /contact-1</p>
</blockquote> TYPO3 Core - Bug #87452: Page Slug generation doesn't take path of parent SysFolders into accounthttp://forge.typo3.org/issues/87452?journal_id=4212342020-03-31T11:06:54ZChristian Eßl
<ul><li><strong>Related to</strong> <i><a class="issue tracker-1 status-5 priority-4 priority-default closed" href="/issues/86456">Bug #86456</a>: Skip special doktype parent pages in slug generation</i> added</li></ul> TYPO3 Core - Bug #87452: Page Slug generation doesn't take path of parent SysFolders into accounthttp://forge.typo3.org/issues/87452?journal_id=4212362020-03-31T11:07:04ZChristian Eßl
<ul><li><strong>Related to</strong> <i><a class="issue tracker-2 status-1 priority-3 priority-lowest" href="/issues/86216">Feature #86216</a>: Allow empty slug for root pages and sysfolders</i> added</li></ul> TYPO3 Core - Bug #87452: Page Slug generation doesn't take path of parent SysFolders into accounthttp://forge.typo3.org/issues/87452?journal_id=4218062020-04-04T15:53:40ZChristian Eßl
<ul></ul><p>The changes made in <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: slide of cObj CONTENT stops if sysfolder in rootline (Closed)" href="http://forge.typo3.org/issues/18079">#18079</a> now lifted the restrictions in PageRepository that were present for all doktypes > 200.<br />This should also be lifted for SlugHelper::resolveParentPageRecord() that currently excludes any page >= 199.</p>
There are some special doktypes, that should still be respected in the check:
<ul>
<li>DOKTYPE_SPACER (199)</li>
<li>DOKTYPE_SYSFOLDER (254)</li>
<li>DOKTYPE_RECYCLER (255)</li>
</ul>
<p>However I think it should be configurable for DOKTYPE_SYSFOLDER, if a sysfolder slug should be added to a child page or not. Currently, pages of doktype sysfolder even show the "slug" field, although it is not used...</p> TYPO3 Core - Bug #87452: Page Slug generation doesn't take path of parent SysFolders into accounthttp://forge.typo3.org/issues/87452?journal_id=4218102020-04-04T16:01:18ZChristian Eßl
<ul><li><strong>Related to</strong> <i><a class="issue tracker-4 status-5 priority-4 priority-default closed" href="/issues/90947">Task #90947</a>: Lift doktype restrictions in SlugHelper::resolveParentPageRecord</i> added</li></ul> TYPO3 Core - Bug #87452: Page Slug generation doesn't take path of parent SysFolders into accounthttp://forge.typo3.org/issues/87452?journal_id=4264372020-06-03T15:19:15ZBenni Mackbenni@typo3.org
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Rejected</i></li></ul><p>Hey all,</p>
<p>the behaviour as defined is intended. If you want to have sysfolders as part of the slug that is generated for a subpage included, check out Extensions such as EXT:masi <a class="external" href="https://github.com/b13/masi">https://github.com/b13/masi</a> - 80% of the sysfolders are folders like "Meta navigation" etc where a slug added is tedious and a pain to reconfigure. However, EXT:masi provides such as solution.</p>
<p>The point is: TYPO3 Core is flexible enough to support such features, however it does not ship all features that people need, in order to reduce the number of "options" available for regular editors.</p>