Project

General

Profile

Actions

Bug #55413

closed

Epic #47018: Implement Composer support and clean package manager API

[Extension Manager] - PackageStates.php empty if incompatible extension is installed

Added by Björn Jacob about 10 years ago. Updated about 10 years ago.

Status:
Closed
Priority:
Should have
Category:
Extension Manager
Target version:
Start date:
2014-01-29
Due date:
% Done:

100%

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

Description

I've got several projects already running on TYPO3 6.2beta (still under development). Since beta1 I'm experiencing an annoying problem. As soon as you install a "problematic" extension the new extension manager throws some kind of exception/ PHP error (always something different - I'll try to gather more information when the problem occurs again). When this happens the PackageStates.php is cleaned and looks like the following snippet:

<?php
# PackageStates.php

# This file is maintained by Flow's package management. Although you can edit it
# manually, you should rather use the command line commands for maintaining packages.
# You'll find detailed information about the typo3.flow:package:* commands in their
# respective help screens.

# This file will be regenerated automatically if it doesn't exist. Deleting this file
# should, however, never become necessary if you use the package commands.

return array (
  'packages' => 
  array (
  'version' => 4,
)
 ?>

Yesterday this happened to me again. I've got a fresh CMS 6.2beta4 and tried to install the current extension_builder extension.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Task #55404: Extract package dependency sorting to own classClosedThomas Maroschik2014-01-28

Actions
Actions #1

Updated by Andrea Herzog-Kienast about 10 years ago

  • Target version set to 6.2.0

Same problem occurs while uninstalling static_info_tables (newest version from forge). Seems not only to be a problem of installing, Björn. So as a workaraoud - save the PackageStates.php before doing something in the EM. If it crashes, you can load it up again. This works, if you uninstalled extensions.

Actions #2

Updated by Thomas Maroschik about 10 years ago

  • Assignee set to Thomas Maroschik
Actions #3

Updated by Björn Jacob about 10 years ago

I think the problem is not related to a specific extension. It happened the other day with one of my own extensions freshly build with the extension_builder on a 6.1 installation. But you're right Andrea. Now we put this file in our project repository among all the theming stuff and realurl_conf.php etc.

Actions #4

Updated by Thomas Maroschik about 10 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

This one should be solved by https://review.typo3.org/27101

If it isn't please say so and I'll reopen this issue.

Actions #5

Updated by Ernesto Baschny about 10 years ago

  • Parent task set to #47018
Actions

Also available in: Atom PDF