We've been testing out your Newsletter Studio and it seems great. I just have a few questions to help us move our project forward:
What is the upgrade process from 1.4.1 to 1.4.2?
Is 1.4.2 compatible with the forthcoming release of Umbraco 6.2? In particular, is it compatible with the new Umbraco Membership API?
Can the tree name be changed? By default, it reads "Newsletter Studio", but it would make more sense to our users if we could rename it to "Communications".
1. You should just be able to install the package "over" the old installation. Or just replace the DLL. There is two types that you'll miss if you go with the replace-strategy but no functionality. (http://support.newsletterstudio.org/customer/portal/articles/1053104-change-log)
2. No, not at the moment but it will probably be quite soon after the release of the new API. I'm not sure if they will break the old API or rewrite that to be backwards compatible? Since Newsletter Studio is based on a provider model we'll only need to implement a new subscription provider for the new API. (http://support.newsletterstudio.org/customer/portal/articles/1052901-subscription-providers). Any way - its just a metter of 10-15 mins to build a provider for the new API.
3. You could probably do that in the language file in /umbraco/config/lang/ (or something like that) under the sections-section.
I hope that this helps you - just let me know if I can do anything else for you and your team.
1.4.1 to 1.4.2 upgrade, Umbraco 6.2 compatibility, changing tree name
Hi Markus
We've been testing out your Newsletter Studio and it seems great. I just have a few questions to help us move our project forward:
Hi!
Nice to hear that you like the package!
1. You should just be able to install the package "over" the old installation. Or just replace the DLL. There is two types that you'll miss if you go with the replace-strategy but no functionality. (http://support.newsletterstudio.org/customer/portal/articles/1053104-change-log)
2. No, not at the moment but it will probably be quite soon after the release of the new API. I'm not sure if they will break the old API or rewrite that to be backwards compatible? Since Newsletter Studio is based on a provider model we'll only need to implement a new subscription provider for the new API. (http://support.newsletterstudio.org/customer/portal/articles/1052901-subscription-providers). Any way - its just a metter of 10-15 mins to build a provider for the new API.
3. You could probably do that in the language file in /umbraco/config/lang/ (or something like that) under the sections-section.
I hope that this helps you - just let me know if I can do anything else for you and your team.
/ m
is working on a reply...