We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Within the event listener \Crossmedia\Fourallportal\EventListener\TablesDefinitionListener the SQL schema is modified.
\Crossmedia\Fourallportal\EventListener\TablesDefinitionListener
This leads to the issue "Array to string conversion" in function \TYPO3\CMS\Core\Database\Schema\SqlReader::getTablesDefinitionString (line 75).
\TYPO3\CMS\Core\Database\Schema\SqlReader::getTablesDefinitionString
The function expects the data from the event a one dimensional array, however the event listener puts a multidimensional array into the event.
How to reproduce
Run command typo3 database:updateschema "*.add,*.change" --verbose
typo3 database:updateschema "*.add,*.change" --verbose
Environment
Extension version: a9e85d3 TYPO3 12: v12.4.17
The text was updated successfully, but these errors were encountered:
fix: return one dimensional array of sql strings for TYPO3
fc458bd
Refs: mia3#26
fix: return one dimensional array of sql strings for TYPO3 (#27)
3e00a60
Refs: #26
Solved with #27
Sorry, something went wrong.
No branches or pull requests
Within the event listener
\Crossmedia\Fourallportal\EventListener\TablesDefinitionListener
the SQL schema is modified.This leads to the issue "Array to string conversion" in function
\TYPO3\CMS\Core\Database\Schema\SqlReader::getTablesDefinitionString
(line 75).The function expects the data from the event a one dimensional array, however the event listener puts a multidimensional array into the event.
How to reproduce
Run command
typo3 database:updateschema "*.add,*.change" --verbose
Environment
Extension version: a9e85d3
TYPO3 12: v12.4.17
The text was updated successfully, but these errors were encountered: