TYPO3.Flow

TYPO3 Flow Base Distribution Doctrine 2 Symfony.Component.DomCrawler Symfony.Component.Yaml TYPO3.Flow TYPO3.Fluid TYPO3.Kickstart TYPO3.Party TYPO3.Welcome Packages Applications

Bug #32552

PackageStates are saved on each request

Added by Bastian Waidelich over 1 year ago. Updated over 1 year ago.

Status:

Resolved

Start date:

2011-12-14

Priority:

Must have

Due date:

Assignee:

Robert Lemke

% Done:

100%

Category:

Package

Target version:

PHP Version:

Complexity:

Has patch:

FLOW3 version affected:

Git master

Votes:

1 (View)

Description

\TYPO3\FLOW3\Package\PackageManager::initialize() always invokes loadPackageStates() which contains the lines

if ($this->packageStatesConfiguration === array() && $this->bootstrap->getContext() !== 'Production') {
    $this->scanAvailablePackages();
    [...]

scanAvailablePackages() in turn calls savePackageStates() which deletes all shortcut paths and recreates them.

If I get it right this means, that all shortcut paths are recreated for each request. Is this intended?

Related issues

related to TYPO3.Flow - Feature #32333: Modular and configurable bootstrap

Resolved

2011-12-06

Associated revisions

Revision 8634aaec
Added by Christopher Hlubek over 1 year ago

[BUGFIX] Update package states only when needed

While scanning of available packages will still happen on every request
in non-production contexts, the package state will only be saved if
there has actually been a change.

Change-Id: If18f9c7edebd8206348bf848059b7c37075866c4
Releases: 1.1
Resolves: #32552

History

#1
Updated by Christopher Hlubek over 1 year ago

Priority changed from Should have to Must have

I think this is a blocker for development, I always get permission problems when Shortcuts are removed etc.

I think there is a bug with the empty package state configuration triggering the reload /save on every request. We only need to scan packages on the first hit and then only if package relate actions are called (like activate / list etc.).