Project

General

Profile

Actions

Bug #57601

closed

Upgrading 6.2: PHP Fatal error: Uncaught exception 'TYPO3\\Flow\\Package\\Exception\\PackageStatesFileNotWritableException

Added by Alexander Opitz over 10 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Install Tool
Target version:
-
Start date:
2014-04-03
Due date:
% Done:

0%

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

Description

PHP Fatal error:  Uncaught exception 'TYPO3\\Flow\\Package\\Exception\\PackageStatesFileNotWritableException' with message
'We could not update the list of installed packages because the file [...]/typo3conf/PackageStates.php is not writable.
Please, check the file system permissions for this file and make sure that the web server can update it.' in
[...]/typo3-src/typo3/sysext/core/Resources/PHP/TYPO3.Flow/Classes/TYPO3/Flow/Package/PackageManager.php:933
Stack trace:
#0 [...]/typo3-src/typo3/sysext/core/Classes/Package/PackageManager.php(717): TYPO3\\Flow\\Package\\PackageManager->sortAndSavePackageStates()
#1 [...]/typo3-src/typo3/sysext/core/Classes/Package/FailsafePackageManager.php(101): TYPO3\\CMS\\Core\\Package\\PackageManager->sortAndSavePackageStates()
#2 [...]/typo3-src/typo3/sysext/install/Classes/Controller/StepController.php(336): TYPO3\\CMS\\Core\\Package\\FailsafePackageManager->forceSortAndSavePa in [...]/typo3-src/typo3/sysext/core/Resources/PHP/TYPO3.Flow/Classes/TYPO3/Flow/Package/PackageManager.php on line 933

Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #57723: PackageStates.php may cannot be written due to invalid pathClosed2014-04-07

Actions
Related to TYPO3 Core - Bug #61317: PackageManager caches absolute paths for different PATH_siteClosed2014-09-02

Actions
Actions #1

Updated by Andreas Fernandez over 10 years ago

I can confirm this bug. In my case, in Install Tool the system tries to access

/var/www/virtual/XXXX/html/typo3conf/../../typo3conf/PackageStates.php

which is obviously wrong.

Actions #2

Updated by Alexander Opitz over 10 years ago

@Andreas Otto †

if the path is wrong, then you have another issue. You should open an issue report about this, with some more information about your directory structure.

Actions #3

Updated by Riccardo De Contardi over 9 years ago

  • Status changed from New to Needs Feedback

Is this bug still valid with the latest version? (6.2.12)

Actions #4

Updated by Helmut Hummel over 9 years ago

  • Status changed from Needs Feedback to Rejected

Duplicate of #57723 which is closed

Actions #5

Updated by Alexander Opitz over 9 years ago

  • Status changed from Rejected to Closed

Not a duplicate of #57723 which was closed by myself after speaking with Andreas.
But it is resolved by one of the catch exception patches in EM.

Actions

Also available in: Atom PDF