Bug #103000
closed
Running the cli command extension:setup causes duplicated fileadmin
0%
Description
The following procedure in the dev setup of my extension leads to the wrong behaviour:
- composer install
- run through the installation wizard
What do i expect at this point:
In my extension i have a Initialisation/Files folder with several assets, that are required for the system to work properly. I expect the new installation's fileadmin to contain those files after the setup. But they are not there...
So i tried the following:
.Build/bin/typo3 extension:setup
No error at this point, but typo3 created another fileadmin. Its identical to the fileadmin with id 1. It even has the same tstamp value. So the database row was duplicated. My Initialization files have not been imported though...
What do i expect:
The same behaviour as in V11 - TYPO3 should correctly import my Initialisation files and should NOT create a second fileadmin record.
I can not share the source code of my extension as it is not open source.
I dont add any relevant hooks or event handlers, that could cause this problem.
Updated by Philipp Wrann 8 months ago
This also happens when i remove the Initialisation folder.
Updated by Philipp Wrann 8 months ago
May also happen without running the setup command by simply going through the installation routine :-/
Updated by Philipp Wrann 7 months ago
Background: I suspected my "wrong" development setup to be the cause of this issue, see the following link:
https://talk.typo3.org/t/extension-development-v12-update-what-do-i-miss/5160/8
But after changing the setup to a classic project structure the problem with 2 fileadmin storages still persists
Updated by Riccardo De Contardi 5 months ago
- Related to Bug #103232: fileadmin is created 2 times in new setup added
Updated by Stefan Bürk 5 months ago
The same behaviour as in V11 - TYPO3 should correctly import my Initialisation files and should NOT create a second fileadmin record.
Can you elaborate what you excatly mean by "import my initialisation files" ?
Updated by Georg Ringer 4 months ago
I can't reproduce the issue, therefore I am closing the issue.
feel free to open a new issue if still relevant - however please test with v12 as v11 might not be get full attention anymore for non critical issues
Updated by Georg Ringer 4 months ago
- Status changed from Needs Feedback to Closed