Project

General

Profile

Actions

Bug #99774

closed

Initialisation/data.xml not imported when creating new composer-based installation

Added by Philipp Wrann almost 2 years ago. Updated 4 months ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Install Tool
Target version:
-
Start date:
2023-01-31
Due date:
% Done:

0%

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

Description

I created a "skeleton" project, that contains a local Distribution package. It has a Initialisation/data.xml file. When doing the following steps, the data is not imported but the registry contains the value typo3conf/ext/***/Initialisation/dataImported. So there must be an error at some point.

composer install
typo3cms install:setup

All install variables are defined as environment variables. The setup works, the fileadmin data is imported, the site config is copied but the data.xml is not imported.

The data has been exported using the impexp extension in typo3 V10

Before i upgraded my skeleton to V11 (V10) it worked (did not work perfectly - mixed up ids but a basic pagetree existed)

This way the Initialisation/data.xml Distribution feature is not useful for me, i dont want to create new exports everytime i update the skeleton.

What do i miss?

edit

running the impexp:import command manually does not work either, adding a -v options tells me:

The parsedUri "http:///app/vendor/bin/typo3cms" appears to be malformed

Maybe my best option is to forget about the impexp disaster and add a simple sql dump

edit2

For the records: I dont care about this issue anymore, i decided not to use the impexp extension in that case. A sql dump performs much better and more reliable if you work on a "blank" database.

Actions #1

Updated by Philipp Wrann almost 2 years ago

  • Description updated (diff)
Actions #2

Updated by Philipp Wrann almost 2 years ago

  • Description updated (diff)
Actions #3

Updated by Georg Ringer 4 months ago

  • Status changed from New to Closed

closing issue as requested - and certainly not really too easy to debug & solve

Actions

Also available in: Atom PDF