I like this package, but I would just like to point out how much of a pain in the ass it is to update/uninstall.
Updating
The update process chokes when it attempts to re-add lines or properties to config files or stylesheets. Once an exception occurs, it seems to halt the rest of the update install, causing unforeseen issues.
Uninstalling
Uninstalling the package not only fails to remove itself from the App_Plugins directory, but it also leaves a sticky residue in the applications and trees config. This would actually run into the same pitfall I listed above with Updating, since the installer will again choke on the existing lines in the config files.
Installing, upgrading and uninstalling is not easy with packages in Umbraco - specially when things under the hood changes.
Would you be able to share what versions you are trying to upgrade from -> to and what Umbraco versions you are running so that we can try to track down this issues?
Gladly. Umbraco packages really do seem to have some teeth.
Several months back, I had some content editors try out the package only to have them move on to other priorities. Attempting to uninstall in Umbraco 7.2.8 left some undesirable lines in multiple config files. Unfortunately, I don't recall what version of the package this was.
Now that we have time to revisit the package, I attempted to re-install the latest version on my nightly build of Umbraco (v7.4.3build3482). All the package files were added to my project, but the install blew up when it found conflicts in umbracoSettings.config.
I'm under the impression that the installer missed some crucial steps once it failed on that exception. I've uninstalled again and am now scanning my project to manually remove any trace of the package before I try to re-install it.
Great hint! We're using a built in "package action" (avoid them ;D) that don't check if there is already a task with the same name.
The URL used is the same as the domain/port used when you are installing the package. We can't know your production URL when installing - or how do you mean that we should parse the domain/ports?
I didn't expect the package to add my production domains (I'll do that myself in a config transform), I only anticipated my dev domain (localhost:44300) to be used. The issue is that the installer is adding an extra scheduled task before it adds the appropriate one (see image above).
Note that there were no scheduled tasks in the config file before I installed.
That's a good idea, might be that the installer skips other actions if one fails.
I haven't looked that this in 100% detail but from my understanding the installer should catch exceptions in individual actions and continue.
Do you know if the tinyMCE-commands was added correctly during your first try to install the package?
The tinyMCE-commands were installed properly in my first install on Umbraco 7.2.8 several months back. It seems as if the installer just isn't making it to that point because of the exception.
Trouble with Updating and Uninstalling
I like this package, but I would just like to point out how much of a pain in the ass it is to update/uninstall.
Updating
The update process chokes when it attempts to re-add lines or properties to config files or stylesheets. Once an exception occurs, it seems to halt the rest of the update install, causing unforeseen issues.
Uninstalling
Uninstalling the package not only fails to remove itself from the App_Plugins directory, but it also leaves a sticky residue in the applications and trees config. This would actually run into the same pitfall I listed above with Updating, since the installer will again choke on the existing lines in the config files.
Hi Matthew!
Thank you for the feedback!
Installing, upgrading and uninstalling is not easy with packages in Umbraco - specially when things under the hood changes.
Would you be able to share what versions you are trying to upgrade from -> to and what Umbraco versions you are running so that we can try to track down this issues?
// m
Gladly. Umbraco packages really do seem to have some teeth.
Several months back, I had some content editors try out the package only to have them move on to other priorities. Attempting to uninstall in Umbraco 7.2.8 left some undesirable lines in multiple config files. Unfortunately, I don't recall what version of the package this was.
Now that we have time to revisit the package, I attempted to re-install the latest version on my nightly build of Umbraco (v7.4.3build3482). All the package files were added to my project, but the install blew up when it found conflicts in umbracoSettings.config.
I'm under the impression that the installer missed some crucial steps once it failed on that exception. I've uninstalled again and am now scanning my project to manually remove any trace of the package before I try to re-install it.
Just to re-install after removing all references to NewsletterStudio and I'm still getting the conflict in umbracoSettings.config.
It's adding a bounce and sendout scheduled task for an empty localhost for whatever reason.
FYI, I do have SSL enabled and localhost:44300 is the debugging domain.
Hi!
Great hint! We're using a built in "package action" (avoid them ;D) that don't check if there is already a task with the same name.
The URL used is the same as the domain/port used when you are installing the package. We can't know your production URL when installing - or how do you mean that we should parse the domain/ports?
// m
I didn't expect the package to add my production domains (I'll do that myself in a config transform), I only anticipated my dev domain (localhost:44300) to be used. The issue is that the installer is adding an extra scheduled task before it adds the appropriate one (see image above).
Note that there were no scheduled tasks in the config file before I installed.
I also noticed that the install failed to add the extra commands for tinyMCE listed here: http://support.newsletterstudio.org/customer/en/portal/articles/1052799-how-to-install-newsletter-studio . This may have something to due with Umbraco throwing the exception in umbracoSettings.config.
Hi!
That's a good idea, might be that the installer skips other actions if one fails. I haven't looked that this in 100% detail but from my understanding the installer should catch exceptions in individual actions and continue.
Do you know if the tinyMCE-commands was added correctly during your first try to install the package?
The tinyMCE-commands were installed properly in my first install on Umbraco 7.2.8 several months back. It seems as if the installer just isn't making it to that point because of the exception.
is working on a reply...