We have a site w/a top level domain "http://surgery.ucsf.edu" and a large number of subdomains, ie. pediatric.surgery.ucsf.edu etc. Would the license cover those subdomains. I assume they would. When we licensed Umbraco complete, we simply used ucsf.edu for our domain. That would be most expedient here. Would that work?
Right, all of these sites are in the same instance. Here's the Umbraco tree. ? Umbraco HQ led us take a license for "ucsf.edu" for Umbraco complete. Perhaps we could do the same w/you. We are a single Department - surgery and our newsletters would be about dept related news.
I'll have to check with HQ how to create a license like this. But as I said, if you logon to umbraco from "yada.mysite.com/umbraco/" all liks inside the newsletter will point to "yada.mysite.com", if you logon at "yadayada.mysite.com/umbraco" that subdomain would be used. All newsletters are shared cross all domains as well.
Licensing Question
We have a site w/a top level domain "http://surgery.ucsf.edu" and a large number of subdomains, ie. pediatric.surgery.ucsf.edu etc. Would the license cover those subdomains. I assume they would. When we licensed Umbraco complete, we simply used ucsf.edu for our domain. That would be most expedient here. Would that work?
Richard Barg
Hi!
Is it the same instance?
I would recommend you to use one of the domains for sending newsletters as the send out engien uses the current url to build the links.
// M
Right, all of these sites are in the same instance. Here's the Umbraco tree. ? Umbraco HQ led us take a license for "ucsf.edu" for Umbraco complete. Perhaps we could do the same w/you. We are a single Department - surgery and our newsletters would be about dept related news.
Hi!
I'll have to check with HQ how to create a license like this. But as I said, if you logon to umbraco from "yada.mysite.com/umbraco/" all liks inside the newsletter will point to "yada.mysite.com", if you logon at "yadayada.mysite.com/umbraco" that subdomain would be used. All newsletters are shared cross all domains as well.
// m
is working on a reply...