pagemachine / typo3-phinx Goto Github PK

While cleaning up the DB of a TYPO3 instance I have noticed that the DB analyzer wants to delete (rename first) the table tx_phinx_log. This is because this ext. does not ship an ext_tables.sql.

I am aware that it does ease the maintenance, by not shipping it. However, it is crucial IMO that this table exist. So, my question: Should the schema be shipped along with that ext.?

I have mixed feelings towards that, because copying the schema is redundant.

When using the DataHandler in migrations/seeds, records are not created. This is due to a missing BE user authentication; the BE user (_cli_) exists and is an admin, but without initialized authentication, the necessary info is not loaded.

At the moment PHP 8.0 is not supported.

https://www.php.net/supported-versions.php

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• [TASK] Update typo3/coding-standards (^0.7.1 => ^0.8.0)

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

An exception occurs in case $GLOBALS['TYPO3_CONF_VARS']['DB']['Connections']['Default']['port'] is not specified:

[ TYPO3\CMS\Core\Error\Exception ]                                                                                                            
  PHP Warning: Undefined array key "port" in /var/www/html/vendor/pagemachine/typo3-phinx/Classes/Configuration/PhinxConfiguration.php line 34

We generally do not configure this value as the default value of 3306 is used as a fallback within Doctrine DBAL.

With TYPO3v12 extension packages are placed in the regular Composer vendor-dir (normally vendor). Migrations/seeds from these packages must be found accordingly.