Bug #37998
Errormessage if someone updates from powermail 1.x to 2.x
| Status: | Rejected | Start date: | 2012-06-13 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | Alex Kellner | % Done: | 0% |
|
| Category: | Frontend Plugin | |||
| Target version: | 2.x | |||
| Votes: | 0 |
Description
ERROR: Content Element type "powermail_pi1" has no rendering definition!
Update is not possible, but anyways it should not come up any errors like this...
History
Updated by Alex Kellner 11 months ago
- Target version changed from 2.0.1 to 2.0.2
Updated by Alex Kellner 11 months ago
Another message from Scheibo:
The default controller can not be determined. Please check for Tx_Extbase_Utility_Extension::configurePlugin() in your ext_localconf.php.
Updated by basti 10 months ago
Sorry, but I think this update process to 2.0 is definitely a no-go! All forms are deleted and after downgrading zu 1.6.8 it´s the same. There is no hint in the extension manager that you can´t use old forms, mails and the old forms will be deleted!
Updated by Alex Kellner 10 months ago
Sorry, that's not true
I added hints to this places- I added a hint at the TER upload as a comment (see screenshot)
- I added hinto to the manual
- A jump from 1.x to 2.x should sharpen your sense
Updated by Stefan Padberg 10 months ago
I'm not happy with this upgrade policy either: I've got a meesage from my provider that powermail 1.6.6 is unsecure and that "it is strongly recommended to update" the extension. The next version I found was 2.0.something, and as I was doing the update with the extension manager in the backend, I didn't see any warning of some kind. It cost me half a day to find out what was going on and to find an old powermail version ready to re-install!
I remmeber when 'tt_news' jumped to 2.x it produced big warnings in the extension manager, so you still could decide whether to go on or to stop the procedure.
I dont know how to realise this but strongly recommend this kind of policy.
Updated by Alex Kellner 10 months ago
I'm sorry, but I don't know about giving a hint to the updater - please join the developing and provide me with the needed information.
I will include it.
Updated by Alex Kellner 9 months ago
- Target version changed from 2.0.2 to 2.x
Updated by Alex Kellner 7 months ago
- Status changed from Under Review to Rejected
No idea how to fix that because this is related to the TYPO3 core and the way how the plugin is implemented in TYPO3.
At the moment there is only the "manual" way to create new plugins after an update from 1.x to 2.x