My company has a Kentico v11 site with 6 subdomains. We are planning on adding about 5 more in the near future. The site is made up of one Kentico instance and one set of pages to be served. We simply change the styling of the site based on the subdomain, and we filter the data to only show the appropriate information per subdomain. Up until now, we have been getting a new Kentico license for each subdomain but, that is getting a little burdensome. My question is this: Do we need to get a separate license for each subdomain? If we don't, then how do I avoid the licensing error when I try to access a new subdomain on the site?
Thanks in advance for whatever information you can provide.
You are already following the correct procedure, generating a new license for each subdomain.
I would highly recommend that you discuss anything license related directly with Kentico Xperience sales (sales#xperience.io) or with your account manager.
Kentico 11 support ends on November 30, 2021, I would recommend upgrading your installation to Kentico 12 so you have extended support through fall 2023.
Related
Noob poster: I'm trying to set up a Joomla 4 site with four distinct functions 1) Blog 2) Social 3) Mobile and 4) Site development. I plan to add the Gantry 5 framework and Gantry 5 Helium template. Each site function has to share data bidirectionally with the others (e.g. signon and workflow). I have a hosting provider and have been conversing with the hosting techs. There seems to be no definitive answer on whether to set up subdomains or use subdirectories for each of the functions. To lessen the impact of higher volume potential and a contained workflow I was favouring the subdomain route. On this approach the last word was I needed to install Joomla on each subdomain, followed on each by the Gantry 5 framework and then the Gantry 5 template. There appear to be pros and cons on each approach and we haven't been able to determine if subdomains or subdirectories would ultimately give me what I need. The tech suggested I post here. NOTE: There is no additional cost from my provider for using subdomains.
Activity so far: Reading what I can find on subdomains and subdirectories. I'm a designer so I've been reading then conversing then more reading then more conversing with the hosting techs trying to figure out the best way of going. It's taken a few days and now I'm chasing my tail.
Thanks.
I'm a member of a small society with an html website (cmyf.org.uk) built many years ago -most of the information is static and very rarely edited but we would like to add blogging and other functionality. My question is, should we set up a CMS site under a new domain name, or is there a way to combine the existing static site and a new section with modern CMS under the same domain name, without needing to import existing content into the new CMS? We are working with a very small budget so would like to save on domain hosting costs.
You can easily create a dedicated subdomain, i.e.blog.cmyf.org.uk, and set up any cms just for blogging purposes (e.g. WordPress or Ghost CMS). Ask your domain provider or server admin for help - by definition creating and configuring a subdomain is free (in comparison to registration a new domain).
Most of the common off the shelf CMS/blogging software can be relatively easily configured to run from a subdirectory under the webroot.
That would be one way to have both sites co-exist happily, on the same webhosting package and domain.
There may well be other or more desirable ways to accomplish the same thing but they all depend on the details (which software/blogplatform, what webhostingcompany and what kind of features they offer, etc.)
The question is pretty clear I think, but I will elaborate on why I'm asking it.
I created a little blog engine based on OneNote. Basically, the blog configuration asks for an access to OneNote. Then the user chooses a section under which the blog posts are stored.
There is a cron script that will use all these informations to automatically get new pages, fetch the medias and cache every, and finally display the posts.
I chose OneNote because I own three Windows 8 computers and a Windows Phone, so OneNote was an easy choice, as I didn't want to get an other application to manage my blog.
There is still a lot to do (as always with softwares...), but I want to make this more or less an open source project, so that other people can install it on their websites and link it directely to OneNote.
The only "big" obstacle for this now is that authentication in the OneNote API needs to register the application on the Live Connect, and specify a redirect domain. So every user wishing to use this blog engine on their server will have to register their own application... That will look complicated just for a blog, especially if you're not tech-savvy.
Is there a way to "skip" or work around this requirement, even if it requires the user to make the section public (as it is for a blog, this doesn't seem too much to ask) ?
Thank you in advance,
Cheers
Sounds like an awesome project! When you get it released be sure to let us know at #OneNoteDev.
Unfortunately, at this time there's no way to circumvent the requirement for Live Connect OAuth configuration. You could offer a hosted variant so only you need to worry about the LiveID configuration.
I have a windows store app which I built about two years ago. I released it as a free app, but now I'm thinking about switching to a trial / paid model. After the trial expires, the app would return to the free functionality and the user could pay to upgrade
My question is, can I replace a free app with a paid one?
By replace I mean, change the existing app to require payment, and keep the reviews etc. Is this possible?
Yes. You will need to follow the normal update process. Your new update should have the paid/trial functionality and when you upload the new version you can set a price. You can find help here http://msdn.microsoft.com/en-gb/library/windows/apps/hh694065.aspx. If you want existing users to buy the app then you can look at in app purchasing.
I am developing a login and account system for use with an existing website, this will run on a subdomain under the main site url.
I would like to use a subdomain that is generic enough so it isn't tied to an account system but not off-putting to users.
I was thinking of www2 but I am concerned people will see this and think its not "legitimate".
Thanks
Some more context.
The new site is currently used for the login and account system but I will eventually migrate the whole website to the new system, this means the services and pages served by the subdomain will very a lot so it can't be specific to one thing.
Try something generic in the interest / knowledge domain of the existing website. What does the existing website do or provide? This can help you determine a proper subdomain.
Some generic examples:
info.domain.com
account.domain.com
auth.domain.com
app.domain.com
to.domain.com
Providing a better subdomain is going to require some more context.