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
Sorry, GoodNews 2.x currently has no upgrade path! It's already on my list. As GoodNews 2 is a complete rewrite (code base) and has a complete new file structure (composer based) running an upgrade on v1.x will be much more complicated then just renaming the classes.
But it's great that you did this step. Yes the class keys needs to be changed beside many other things.
It would be great if you could report any other problems you can find.
gadgetto
changed the title
Error upgrade to MODX3 class_key is not renamed
Upgrade GoodNews 1.x to 2.x not possible
Mar 13, 2023
I did a few tests.
First the new subscribers were not added to the groups/categories.
But this is due to the parsing of the input/output modifiers. Its a bug in MODX3.
I'm using &defaultGroups and &defaultCategories.
The output of
Then after subscription the user was not redirected to the &submittedResourceId. But this is due to my &postHooks snippet.
because use of: $modx->mail->set(modMail::MAIL_BODY,$message);
This had to be reworked due to this post of @BobRay from the forum.
After upgrading to MODX3/GoodNews2, the content of the contexts with GoodnewsContainers is not displayed.
In my opinion the problem is that the existing documents with the old DocumentType are not renamed during the installation of GoodNews 2.0.0-alpha2.
I did the renaming manually. Then the resource tree is displayed again.
The text was updated successfully, but these errors were encountered: