Closed fawmi closed 3 years ago
Thanks for contributing this PR, @fawmi! I'll review it shortly.
@oliverklee Sorry, wrong changes were committed. I fixed the changes and added a line in the changelogs file.
@oliverklee Not related to this PR, but there are a few other changes for making this extension TYPO3 10 compatible, which I would like to open a PR for. Is it possible to create a typo3-10 Branch so that I can commit my changes there?
And how is the support policy for the extension, should the version 3.3 (or whatever version it will be) support TYPO3 8 as well?
@fawmi I've moved your question to the Discussions section and replied there.
@fawmi I have no idea why the V9 tests are running on the CI for this branch. For starters, could you please check that your branch is based on the latest main
branch?
My branch is based on feature/typo3-9. Should i create a PR based on main?
My branch is based on feature/typo3-9. Should i create a PR based on main?
Yes, please, always.
(You can also rebase and force-push in order to keep this PR.)
(The version 9 branch currently is only for seeing what breaks, not for building a 9-compatible version.)
@oliverklee
In the main branch, the addPlugin
is already done in the ext_tables.php
file, which also works in TYPO3 9/10
The addPlugin
was moved to the ext_localconf in the "472261d7b214fab8180a52f675f17e998875c441".
As far as the changes from features/typo3-9 is not merged in main the plugin works. This PR is also not needed in the main
branch.
Okay, thanks for checking and reporting back! Closing then.
The TYPO3 9 plugin shows an error, when the plugin is added as content element. The error says "Invalid value [realty_pi1]" The error disappears when I move the call to the
ExtensionManagementUtility::addPlugin
method to the tt_content file. This PR moves the call toExtensionManagementUtility::addPlugin
tt_content.php file.