Support Newletter Studio in Umbraco in sub webapplication in IIS
Hi,
I rebuild my Umbraco website in Wordpress. At the hostingprovider:
Wordpress is running at the root
Umbraco (the old website) is running at /app.
This works fine. I use Umbraco for Newsletter Studio and a few other minor things. However, there are two issues in this setup:
Newsletter Studio tries to read the newsletterStudio.config from the root application (/), and not from the current web application root (~/).
After sending emails, the unsubscribe link is https://www.my-domain.com/appplugins/newsletterstudio/pages/tracking/unsubscribe.aspx?utmsource=NewsletterStudio.... . The link should be https://www.my-domain.com/APP/appplugins/newsletterstudio/pages/tracking/unsubscribe.aspx?utmsource=NewsletterStudio.... in my case
I also needed some files from /umbraco/Config/Lang, not sure if this is Newsletter Studio related.
I solved it for now with some double configuration and redirect rules in IIS, but it would be nice if the urls are resolved to the root of the webapplication instead of the root of the host. Or are there better options to support this setup?
I'm note sure if I understand everything right but do you have a working setup at the moment or is it anything that you did not manage to solve?
What version of Umbraco and Newsletter Studio are you running?
While it could work to host the package like this, it's not something that we aim for or that we support officially. Another option might be to host your Umbraco-site on a sub domain.
I do have a working setup now. However, if you send out a test email, no tracking is used and links works fine. After that I sent 10.000 emails out and links didn't work (because of the tracking in between)... Ooops :) I think it's nice to avoid situations like this for other users.
I'm using Umbraco 7.15.3 and Newsletter Studio 2.1.9.6.
A subdomain is an option, but our current SSL-certificate doesn't support subdomains. So we need a special certificate for that, so there are more costs involved.
I'm sorry to hear that you had these issues, since there is differences between preview/test emails and real send outs I would always recommend to send a real send out to a list of test users before sending to a list of real customers.
Reg. these issues, we'll keep this in mind and try to support as much as possible but I would like to be clear that it will not be something that we commit to or officially support in the near future.
Support Newletter Studio in Umbraco in sub webapplication in IIS
Hi,
I rebuild my Umbraco website in Wordpress. At the hostingprovider:
This works fine. I use Umbraco for Newsletter Studio and a few other minor things. However, there are two issues in this setup:
I solved it for now with some double configuration and redirect rules in IIS, but it would be nice if the urls are resolved to the root of the webapplication instead of the root of the host. Or are there better options to support this setup?
Thank you.
Hi!
I'm note sure if I understand everything right but do you have a working setup at the moment or is it anything that you did not manage to solve?
What version of Umbraco and Newsletter Studio are you running?
While it could work to host the package like this, it's not something that we aim for or that we support officially. Another option might be to host your Umbraco-site on a sub domain.
// m
Hi,
I do have a working setup now. However, if you send out a test email, no tracking is used and links works fine. After that I sent 10.000 emails out and links didn't work (because of the tracking in between)... Ooops :) I think it's nice to avoid situations like this for other users.
I'm using Umbraco 7.15.3 and Newsletter Studio 2.1.9.6.
A subdomain is an option, but our current SSL-certificate doesn't support subdomains. So we need a special certificate for that, so there are more costs involved.
Hi!
I'm sorry to hear that you had these issues, since there is differences between preview/test emails and real send outs I would always recommend to send a real send out to a list of test users before sending to a list of real customers.
Reg. these issues, we'll keep this in mind and try to support as much as possible but I would like to be clear that it will not be something that we commit to or officially support in the near future.
Cheers!
// m
is working on a reply...