Project

General

Profile

Actions

Bug #86593

closed

Clean install fails on missing configuration for EXT:scheduler

Added by Stefan Neufeind about 6 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Install Tool
Target version:
-
Start date:
2018-10-08
Due date:
% Done:

0%

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

Description

A clean installation of TYPO3 v9.5.0 fails with:

(1/1) #1509654728 TYPO3\CMS\Core\Configuration\Exception\ExtensionConfigurationExtensionNotConfiguredException
No extension configuration for extension scheduler found. Either this extension has no extension configuration or the configuration is not up to date. Execute the install tool to update configuration.

Actions #1

Updated by Georg Ringer about 6 years ago

  • Status changed from New to Needs Feedback

how to you install it? if composer, how does the composer.json look like?

Actions #2

Updated by Riccardo De Contardi over 5 years ago

  • Status changed from Needs Feedback to Closed

No feedback since the last 90 days => closing this issue.

If you think that this is the wrong decision or experience the issue again and have more information about how to reproduce your problem, please reopen it or ping me.

Thank you and best regards

Actions #3

Updated by Stefan Neufeind over 5 years ago

I don't know exactly anymore how to reproduce it. Happened during an install at the time when I reported it, reproducible at that time.
Afaik it was composer-based but updated from some earlier version or so. Might have been a side-effect then.
So let's leave it closed for now.

Actions #4

Updated by Andy Hausmann about 4 years ago

Got the same error today and fixed it for me via

composer dump-autoload

Error is gone and Backend is accessible.

Actions #5

Updated by Mati Sediqi almost 4 years ago

In my case I got the Exception in v10.4.12 when I deleted the PackageStates.php - purpose was that TYPO3 generates a new one since I deleted an extension from /typo3conf/ext/-directory manually (which was a composer package) rather than doing a composer remove and before that disabling it using the Extension-Manager from the backend..

Guess it happens whenever there's no /typo3conf/PackageStates.php-file available?

Actions

Also available in: Atom PDF