You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Several documentation files were build using composer docs:db, but this command no longer works with the latest main branch installed on TYPO3 v11.
The command tries to execute Build/Documentation/dbdocs/generate.php which fails to find vendor/autoload.php (might require different paths for TYPO3 v11 and TYPO3 v12 or later).
The text was updated successfully, but these errors were encountered:
I investigated the compose docs:db command. It is used to generate the reStructuredText file Documentation/Developers/Database.rst, which has not been updated in the last 3 years.
I'm not sure why the code is located in the Build/Documentation/dbdocs directory. I guess the idea was that it isn't code that is needed at runtime. On the other hand, the code requires access to the database in order to extract information about the database schema.
In order to make this work, the generate.php somehow configures a custom typo3 environment based on the classic non-composer based typo3 directory structure, which is why there is a symbolic link Build/Documentation/dbdocs/public/typo3.
Anyway. My suggestion would be to move this code to the Classes/Command directory and register a new typo3 command kitodo:dbdocs that will trigger the generation process of the documentation file.
I added the pull request #1486 to demonstrate my proposal. What do you think?
Description
Several documentation files were build using
composer docs:db
, but this command no longer works with the latest main branch installed on TYPO3 v11.The command tries to execute
Build/Documentation/dbdocs/generate.php
which fails to findvendor/autoload.php
(might require different paths for TYPO3 v11 and TYPO3 v12 or later).The text was updated successfully, but these errors were encountered: