Bug #86150
closedProblem when page tree for site is deleted and site configuration remains
100%
Description
I think that there is a problem when the site configuration remains in /config/sitename, but the site in the page tree is deleted.
I did the following steps:
- Created page structure for site A (site with site root)
- Created site configuration for that site in sites module
After that i wanted to recreate the page structure in a second tree (but with the goal to use the same domain as for site A because i want to replace that later).
- Created page structure for site B
- Deleted page structure for site A (because i did't not need it anymore)
- Created site configuration for site B
In the end i got a page not found error in the frontend, but the configuration in the backend looked correct (page structure for page B and site configuration for siteB). In the end i recognized, that the pagetree for page A was deleted, but the site configuration in the config folder still exists. But the site configuration for siteA was not visible anymore in the backend.
I think it would be good if the unused site configurations are somehow visible in the backend, or the site configuration is deleted when the tree for that site get's deleted.
Updated by Georg Ringer about 6 years ago
- Category set to Site Handling, Site Sets & Routing
- Status changed from New to Accepted
Updated by Gerrit Code Review about 6 years ago
- Status changed from Accepted to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/58192
Updated by Georg Ringer about 6 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 249b52379ef6e5a3001e16b9a58650c72853e00e.