Project

General

Profile

Actions

Bug #104925

closed

Site Sets remain as dependency after uninstalling extension that provided them

Added by Michael Schams 2 months ago. Updated about 1 month ago.

Status:
Closed
Priority:
Should have
Category:
Site Handling, Site Sets & Routing
Target version:
Start date:
2024-09-12
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
13
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Not sure if this is a bug or missing feature or just an inconvenience.

  • New, empty TYPO3 v13.3 site.
  • Create a page and a site (Site Management => Sites), e.g. example.
  • Install an extension that provides a Site Set (e.g. foobar/extension1).
  • Go to Site Management => Sites and select the site.
  • Open tab General and locate Sets for this Site at the bottom. Select the Site Set foobar/extension1.
  • Save the configuration
  • Delete the extension foobar/extension1.
  • Go to Site Management => Settings

The site example still shows the dependency foobar/extension1 which doesn't exist anymore.
The deleted Site Set still exists in the site configuration: config/sites/example/config.yaml.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Task #103558: Add warning to site module in case set dependencies are brokenClosedBenjamin Franzke2024-04-07

Actions
Actions

Also available in: Atom PDF