As of version 10 in Kentico, if a Developer wants to host a website built using Kentico CMS using MVC, they need to purchase a license for it.

This is a barrier for developers to enter and try out Kentico CMS with MVC. Since Kentico recently announced (at the Roadshows) that MVC would become the primary development model in the next version, it makes sense to provide access to this model for new developers in that version. However as it stands, they will be forced to use one of the other, non-preferred development models (Portal, ASPX or Mixed) to evaluate the product.

The licensing issue is tied to the Kentico development model for ASP.NET MVC application since it relies on the Web Farms functionality.

It would be great if MVC is offered on the Kentico Free Edition. It will bring in developers who don’t want to work with Web forms. More developers will adopt Kentico and be advocates for it.

A developer would be keen to push his personal site or blog on Kentico CMS to showcase his expertise on that platform. If a developer has worked on MVC in a production environment (albeit a small one), it allows him to influence decision makers on larger projects.

A good example for this would be the uptake of Kentico Cloud by developers who were able to use the free edition and are now strong advocates for Kentico Cloud.

Say we have a customer that has a 10-site EMS license.
We're building MVC sites so we want the CMS in one web application and public-facing MVC site in another web application.
To separate concerns between the sites as much as possible we'd like to have a single MVC web application for each site in the CMS.
In the end though, there is only 1 physical servers involved (or Azure App Service plan) that hosts 11 web applications (CMS + 10 MVC applications).

There is 1 additional web farm server license available for free when working with MVC so right now, this requires the customer to buy a web farm node license for every site beyond the first one.
So to fill the 10-site license the customer needs to buy an additional 9 web farm nodes. At current list prices this would cost an additional 100.000 euros.

As you can imagine, this is hard to explain to customers.

Can you please reconsider the web farm licensing model to make the above architecure possible without huge additional costs?

Make a visual drag and drop editor for e-mail templates that could be used for static issues, dynamic issues, marketing automation communications, and on-line form auto-responders (basically all points of e-mail in EMS). The key to this would be to now to have to have content admins and marketers know macros to build e-mail templates.

It seems like the parts of the on-line form builder or widgets could be re-used to create this solution.

I firmly believe that this is needed for EMS to complete with other marketing automation platforms.

I know this has been looked at before and declined, but I really believe it should make it in K11.

Kentico should change its multi-factor-authentication to use industry-standard methods rather than its current custom implementation.

Kentico currently offers multi-factor authentication using the Kentico Authenticator Android application. This is a non-standard tool, and is entirely useless for people without an Android device. As a result, multi-factor authentication cannot be broadly deployed and is all-but-useless in a real-world environment.

Kentico should instead use the industry-standard TOTP method. TOTP is based on an IETF standard, and has been implemented by Microsoft, Google, DropBox, GitHub, Yahoo, and hundreds of other organizations. It supports key generation across all platforms and using hardware-based devices, including Google Authenticator, Authy, OnePassword, YubiKey and more.

While Kentico could create an iPhone/Windows Phone/Mac/PC/etc. version of its authenticator application, this would still force users to install additional software, and would be less trustworthy than a broadly supported standard endorsed by major technology and financial companies.

At the moment we have faced issues in rounding because Kentico uses the sites Main currency in all its calculations. This should be changed so that the calculations are done using the current currency and then converted to the Main Currency to store those values.

This issue has cropped up in an instance which uses 3 currencies and has seperate prices. As an example, we take the EUR price of 169 and an exchange rate to GBP of 1.2 we end up with 140.8333 in the main currency. When this 140.8333 is used in calculations it creates a rounding error depending on how many units are added. The rounding errors appear in different places depending on the values in the order, but in particular in Tax calculations.

I would personally like to see Kentico store the price per unit in the Order Currency and use that value in calculations. Then in the totals which are used for reporting apply the exchange rate to show the values in the Main Currency and not the other way round.