Actions
Bug #89311
closed
Flaws in site configuration when creating new page on root-level
Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
Site Handling, Site Sets & Routing
Target version:
Start date:
2019-09-30
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
10
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:
Description
Scenario: Create a new site on root-level, which leads to auto-generation of site configurationin typo3conf/sites/ (or config/sites/ in composer mode)
- site configuration is not created for (nested) page having
is_siterootenabled (compare with SlugHelper) - creating a sys folder on root-level (pid: 0) and changing page type to standard later does not create site configuration
Updated by Andreas Kienast about 5 years ago
I called with Benni about is_siteroot, the current solution is done on purpose.
Updated by Oliver Hader about 5 years ago
- Related to Bug #89312: NormalizedParams->getSiteUrl() contains PHP script wrapper added
Updated by Oliver Hader about 5 years ago
- Status changed from New to Needs Feedback
Updated by Oliver Hader about 5 years ago
Andreas Fernandez wrote:
I called with Benni about
is_siteroot, the current solution is done on purpose.
Fine with focussing on root-level only. Then probably only sys folder being changed to standard page (or considered page types) remains...
Updated by Christian Eßl almost 5 years ago
- Related to Bug #90436: Some weird behaviour with autogenerated site config added
Updated by Markus Klein over 4 years ago
- Related to Bug #89485: Editing a slug field on a root page (page with SiteConfiguration) is not possible if parent uid of this root page is > 0 and TreeRoot has no site configuration added
Updated by Juan Manuel Vergés Solanas over 4 years ago
- Related to Bug #90736: Wrong slug fields for siteroots (level > 1) in multidomain environment and no possibility to modify them added
Updated by Oliver Hader almost 2 years ago
- Status changed from Needs Feedback to Rejected
Actions