0 0

Cheap Kentico Xperience 13 Hosting Recommendation

Kentico is the only fully integrated ASP.NET CMS, E-commerce, and Online Marketing platform that allows you to create cutting-edge websites and optimize your digital customers’ experiences fully across multiple channels. Kentico saves you time and resources so you can accomplish more.

Giving you the power to improve and refine your digital strategy, align it with the needs of your customers, and create unique user experiences, Kentico Xperience 13 accelerates customer loyalty through new technologies. With improved campaign management and even faster website development possibilities, Kentico Xperience 13 lets you run highly optimized campaigns and deliver exceptional customer experiences, all from one location. And with Web Farm Support, completely rebuilt from the ground up, you can be sure that you are engaging your customers with consistent content, no matter where they access it from, driving customer loyalty and giving your brand the global reach you desire.

System requirement changes

• The minimum required version of Microsoft .NET Framework is now 4.8 (for the Xperience administration application and MVC 5 live site projects).
• Ended support of Internet Explorer (11) for the Xperience administration interface and live site components.
• Microsoft SQL Server for Xperience databases:
  • Version 2008 R2 is no longer supported (2012 or newer is required)
  • Added support for version 2019
• Server operating systems:
  • Ended support for: Windows 7, Windows 8 (8.1 remains supported), Windows 2008 R2
  • Added support for Windows Server 2019

New features

ASP.NET Core

• Added support for developing live site applications using ASP.NET Core.

Content management

• Page URLs and routing
  • New content tree-based URL routing mode. The system can now automatically generate URLs for pages based on their position in the content tree and the configuration of their page types. See Content tree-based routing.
    • If you want to switch from custom routing based on URL patterns to content tree-based routing while preserving the former URLs, you can do so by manually executing a prepared code snippet. See Enabling content tree-based routing.
  • Added support for configuring the format of URLs on multilingual sites using the content tree-based routing mode. For multilingual URLs, you can use separate domains or language prefixes. See Configuring URLs for multilingual websites.
  • New Former URLs application, which enables automatic tracking of changes made to the URL paths of pages (e.g. by changing a URL slug). Old URLs are stored and the system handles redirection to the current URLs. See Managing page URLs.
• Added support for creating linked pages on MVC and ASP.NET Core sites. Linked pages allow content to be reused in various scenarios, for example to simplify editing in the content tree when data stored in a page is displayed within multiple parts of the website.
• New navigation feature for page types and individual pages, which allows content editors to choose which pages are displayed in navigation menus. For more information, see Building website navigation.
• Improved support for editing and handling metadata for pages. The new metadata feature for page types allows administrators to control which pages provide metadata editing, and developers can use new extension methods to render metadata tags when displaying page content.
• Added settings and support for reflecting page permissions on the live site. Page-level permissions are now automatically reflected on sites using the content tree-based routing mode. It is also possible to create authenticated sections that are enforced on the live site.
  • On sites using custom routing, developers can utilize methods from the Xperience API to check page permissions and authentication and authorization of users to access pages. See Implementing page permission checks.
• The language version comparison mode used for viewing and editing two different language versions of pages side-by-side is now supported for MVC and ASP.NET Core sites.
• MVC and ASP.NET Core sites now support validation of HTML, CSS, links, and accessibility for pages via built-in validators.
  • The CSS validator now checks CSS definitions used on pages against the CSS3 standard.
• New security web.config key for accepting all certificates when validating website code or accessibility (e.g. CSS validation) using a 3rd party validation service over a secured protocol (HTTPS): CMSValidationAcceptAllCertificates. See Reference – Web.config application keys.

Content API

• New IPageRetriever service that simplifies loading of page data within live site applications. Supports dependency injection, automatically provides caching, and ensures default parameterization of the resulting page query for common scenarios.
• Page URLs and routing
  • Improved API for getting the live site URLs of pages from the Xperience content tree (new IPageUrlRetriever service and extension methods). For more information, see Displaying page content.
  • New system constraint SiteCultureConstraint that automatically detects and sets the current culture for each request on multilingual websites that use custom routing based on URL patterns. The constraint has a property HideLanguagePrefixForDefaultCulture that enables hiding language prefixes for default content culture URLs.
  • New Kentico().PageCanonicalUrl() extension method that helps developers render Canonical link elements for pages with alternative URLs or for linked pages. The method replaces the PageMainUrl() extension method used previously for this purpose. As a result, the PageMainUrl() method is now obsolete.
• Media libraries – Improved API for retrieving and configuring URLs of media library files. For more information, see Displaying content from media libraries.
• Page attachments – Improved API for retrieving and configuring URLs page attachments. For more information, see Displaying page attachments.

Page builder

• The system now provides the Rich text widget out-of-the-box (for Kentico 12, the widget was available through a NuGet package as an extension). The Rich text widget allows content editors to add stylized text content to pages. See Using the Rich text widget. The same rich text editor can also be used by developers within custom components, as described in Configuring the rich text editor for page builder.
• Development
  • Developers can now limit which sections are allowed in page builder editable areas (in addition to limiting widgets). See Creating pages with editable areas.
  • New API for rendering widgets directly within the views of pages or other page builder components. For more information, see Rendering widgets in code and Extending widgets.
  • The API now allows developers to add visibility conditions to the properties of page and form builder components (widgets, page templates, personalization conditions, etc.). For more information, see Adding visibility conditions for builder component properties.
  • Added support for accessing the data of the current page within custom controller actions that handle POST requests (for both pages and page builder components, such as widgets, sections, and page templates). When handling such requests, the persisted page data can be accessed via the new IPageDataContextRetriever service. For more information, see Developing widgets, Developing page builder sections, Developing page templates.
  • Added support for accessing the properties of page builder components (widgets, sections, page templates) from within custom controller actions that handle POST requests. For more information, see Defining widget properties.
  • Two new selectors for page builder component properties: URL selector and Attachment selector. The JavaScript API of all selectors has been unified into a single configurable content selector API.

Form builder

• New Multiple choice form component that offers checkbox options, and allows users to select multiple options at the same time. See Reference – System form components.
• Development – Added dependency injection support for classes that implement form components. Components can now automatically resolve dependencies from the application’s service container.

Platform

• Site domains
  • Domain aliases can now specify alternative Presentation URLs for the live site (MVC). See Setting domain names for sites.
  • You can now specify a Preview presentation URL for each Administration domain name alias. The Preview presentation URL is then used when previewing live site content within the scope of the administration interface. This can be useful, for example, when preparing environment for content staging.
  • The system now validates the Presentation URL of sites for uniqueness. Different running sites (or their domain aliases) can no longer have matching Presentation URL values.
• Membership
  • All Membership & Security and Passwords settings set via the Settings application now also affect the configuration of the Xperience membership OWIN integration API used by the live site application. Password policies, password reset token validity intervals, cross-site user account sharing, and other features can now be controlled directly from the Settings application without the need to synchronize such changes with the configuration of the live-site application.
  • New API for managing user avatars. See User avatars for more information.
  • The Kentico.Membership.User object used by the system’s ASP.NET Identity integration now also maps the ‘UserInfo.FullName‘ property. See Adding custom fields to users.
• Licensing – Reworked how Xperience controls the maximum number of web farms allowed by site license keys. The number of allowed web farm servers is now counted separately for the live site and administration applications. For example, a license key for a live site hosted on domain.com that allows up to 3 web farm servers allows you to scale the corresponding application to up to three instances. To scale the connected administration instance (e.g., hosted on admin.domain.com), you need a license key for admin.domain.com with its web farm allowance. In previous versions, the scaling model enabled arbitrary distribution of web farm servers allowed by a single license across both applications. See How licensing works for more information and examples illustrating various hosting configurations.
• Added SameSite mode configuration options for cookies. Due to stricter enforcement of the SameSite configuration of cookies adopted by major browsers, it is now possible to configure the SameSite mode of cookies set via the system’s API (for both system and custom cookies). By default, Xperience uses the Lax mode for all system cookies, which is sufficient if the live site and administration are hosted on a single domain. However, if the applications comprising your site are hosted across multiple domains, you need to explicitly force the None mode to ensure the preview mode functionality and all dependent features, such as the page builder, work correctly. See:
  • Configuring cookie SameSite mode to learn how to configure the SameSite mode for system cookies depending on your hosting environment.
  • Working with cookies to learn how to configure the SameSite mode for custom cookies set via the Xperience API.
•  Macros
  • Updated the available macro methods to allow resolving by both the administration and live site application (with the exception of methods that only have a specific function within the administration interface). Certain methods that are no longer relevant were removed and others were made obsolete. To learn about the current macro methods, refer to Reference – Macro methods.
  • The macro report available in System -> Macros -> Report was extended to report occurrences of removed or obsolete macro methods used in the administration application. See Searching for macros.
• Scheduled tasks – The system now allows scheduling and running of site-specific tasks on the side of the live site (MVC) application. For example, you can use this option for tasks that work with the application memory or the local file system. See Processing scheduled tasks on the live site.
• Search
  • Improved the functionality of Pages crawler indexes to allow better usability on sites presented by a separate live site application (MVC or ASP.NET Core). See Defining local page indexes.
  • Added support for Pages crawler indexes in combination with Azure Cognitive Search.
• Event log – It is now possible to specify custom event logging destinations via event log writers. See Customizing event logging for more information.
• REST
  • When generating URLs with hash parameter authentication for REST requests, the system now allows administrators to set an expiration date for individual URLs.
  • Hash parameters generated for authenticating REST requests can now be invalidated.
• Caching
  • New CacheAsync method added to the CacheHelper API that allows loading and caching of Xperience data in asynchronous code. See Caching in custom code.
  • New IProgressiveCache service that provides a full alternative to the static CacheHelper API. Supports dependency injection and makes it easier to cache data within the code of unit tests.
• Performance – The general performance of ObjectQuery calls was slightly improved (such calls are used to load object data within the system and in custom code).
• SharePoint integration – New API that allows developers to retrieve the URLs of SharePoint files and display the files on the live site.
• Added automatic registration of secured (HTTPS) endpoints for the WCF services used by the marketing automation designer and advanced workflow designer (when the administration application is running over HTTPS). Manual configuration is only required in scenarios with advanced environment configurations. See Configuring Windows Communication Foundation for more information.
• Data API
  • The API now contains interfaces (services) for most InfoProvider classes, which are used for basic loading and management of Xperience objects. For example, IUserInfoProvider for UserInfoProvider. The new services can be added using dependency injection or accessed through the Provider property of the corresponding Info class. The original static InfoProvider methods that have replacements are now obsolete. See Database table API.
  • Xperience objects can now be loaded asynchronously using the GetAsync method of the new IInfoProvider interfaces.
  • The DocumentQuery and ObjectQuery classes provide a new GetEnumerableTypedResultAsync method, which allows asynchronous execution of queries that load Xperience pages or objects.
  • The query parameterization methods available for the DocumentQuery and ObjectQuery API are now virtual. This allows developers to call the methods when creating mocked data in automated unit tests (for example when using Substitute.For with query objects).

On-line marketing

• Marketing automation
  • New and improved visual design and overall interface for the automation process designer. The steps for managing the flow of processes (conditions, etc.) were simplified and streamlined.
  • New Time-based triggers, which can be used to start automation processes. Such triggers schedule the process to run for a specified set of contacts, either once at a specified time or recurring based on a set interval.
  • Automation processes can now be saved as templates and then later used as a starting point for creating new processes. The system provides several predefined templates to help quickly create processes that cover common scenarios (Send birthday message, Re-engagement campaign, Abandoned cart reminder). See Managing automation process templates.
  • Improved editing interface for process triggers – triggers are now displayed and managed directly within the process designer interface as part of the Start step.
  • Improved analytics for automation processes, including reports showing the demographics of contacts handled by the process, and a visual representation of the journey that individual contacts have taken through the steps of the process.
  • Marketers can now document and annotate automation processes by adding notes to the process graph. See Working with the automation process designer for more information.
  • Action steps can now retrieve data and display the resulting information to users in the automation process designer interface. For example, the system’s default Send marketing email action step loads and displays available statistics for the related email (number of sent emails, open and link click rate). For more information about implementing data retrieval for custom steps, see Developing custom marketing automation actions.
  • The automation process designer newly displays a warning icon and message for steps with required parameters that are not configured.
  • Users can now duplicate steps within an automation process, including their current configuration.
• The Web analytics feature is now supported for MVC and ASP.NET Core sites. Allows marketers to measure and analyze key metrics of websites directly in the Xperience administration interface.
  • New and improved API for developers who wish to log custom events as web analytics. See Adding custom web analytics.
• Email marketing
  • Emails can now be cloned (copied) between different email feeds. See Composing marketing emails.
  • Emails that have A/B testing enabled can now be selected and sent by marketing automation processes (using Send marketing email action steps).
• The Custom table form submit activity is now supported for MVC and ASP.NET Core sites (logged automatically when calling the appropriate custom table API).
• New macro rules:
  • Rule that evaluates whether a contact has their birthday on the current, preceding or following day.
  • Rule that evaluates whether a contact has been inactive for a specified number of days (i.e. was created at least X days ago and has not performed any activities in the last X days).
• Personas – The staging, export/import, and continuous integration features now support persona data. If you want to synchronize, import or export data of personas that use custom activities in their rule definitions, you need to make sure each custom activity has its Activity item object type configured in Contact management -> Configuration -> Activity types -> Edit -> Scoring rule configuration section. Additionally, you need to manually resave all scoring rules that use such custom activities.

General

• Published the Kentico Xperience item on the Azure Marketplace, which can be used to quickly deploy and evaluate a sample website as an Azure Web App. See Deploying a sample Xperience application from the Azure Marketplace.

Are you looking for Cheap Kentico Xperience 13 Hosting? Finding a high quality Cheap Kentico Xperience 13 Hosting provider is crucial for your web application. Your Kentico Xperience 13 application can only run smooth if it will be hosted on a server which can provide a higher up time & plenty of computing resources. There’re thousands of web hosting providers which offer asp.net hosting, but choosing Cheap Kentico Xperience 13 Hosting provider is a time consuming task. To make your buying decision easy we’ve concluded 3 Best yet Cheap Kentico Xperience 13 Hosting providers which are reliable and offer affordable Kentico Xperience 13 Hosting so that every one can afford it.

Cheap Kentico Xperience 13 Hosting Recommendation

How to Choose Cheap Kentico Xperience 13 Hosting Recommendation

Reliability and Speed of Access

Not only should the web host be reliable and fast, it should guarantee its uptime (the time when it is functional). Look for a minimum uptime of 99%. In fact, even 99% is actually too low — it really should be 99% or higher. The host should provide some sort of refund (eg prorated refund or discount) if it falls below that figure. Note though that guarantees are often hard to enforce from your end — especially if the host denies there was any downtime. However, without that guarantee, the web host will have little incentive to ensure that its servers are running all the time.

Data Transfer (Traffic/Bandwidth)

Data transfer (sometimes loosely referred to as “traffic” or “bandwidth”) is the amount of bytes transferred from your site to visitors when they browse your site.

Don’t believe any commercial web host that advertises “unlimited bandwidth”. The host has to pay for the bandwidth, and if you consume a lot of it, they will not silently bear your costs. Many high bandwidth websites have found this out the hard way when they suddenly receive an exorbitant bill for having “exceeded” the “unlimited bandwidth”. Always look for details on how much traffic the package allows. I personally always stay clear of any host that advertises “unlimited transfer”, even if the exact amount is specified somewhere else (sometimes buried in their policy statements). Usually you will find that they redefine “unlimited” to be limited in some way.

In addition, while bandwidth provided is something you should always check, do not be unduly swayed by promises of incredibly huge amounts of bandwidth. Chances are that your website will never be able to use that amount because it will hit other limits, namely resource limits.

To give you a rough idea of the typical traffic requirements of a website, most new sites that don’t provide video or music on their site use less than 3 GB of bandwidth per month. Your traffic requirements will grow over time, as your site becomes more well-known, so you will need to also check their policy when you exceed your data transfer limit: is there a published charge per GB over the allowed bandwidth? Is the charge made according to actual usage or are you expected to pre-pay for a potential overage? It is better not to go for hosts that expect you to prepay for overages, since it is very hard to forsee when your site will exceed its bandwidth and by how much.

Disk space

For the same reason as bandwidth, watch out also for those “unlimited disk space” schemes. Many new sites (that don’t host videos or music) need less than 20 MB of web space, so even if you are provided with a host that tempts you with 10 GB (or “unlimited space”), be aware that you are unlikely to use that space, so don’t let the 10 GB space be too big a factor in your consideration when comparing with other web hosts. The hosting company is also aware of that, which is why they feel free to offer you that as a means of enticing you to host there.

Technical support

Does its technical support function 24 hours a day, 7 days a week (often abbreviated 24/7), all year around? Note that I will not accept a host which does not have staff working on weekends or public holidays. You will be surprised at how often things go wrong at the most inconvenient of times. Incidentally, just because a host advertises that it has 24/7 support does not necessarily mean that it really has that kind of support. Test them out by emailing at midnight and on Saturday nights, Sunday mornings, etc. Check out how long they take to respond. Besides speed of responses, check to see if they are technically competent. You wouldn’t want to sign up with a host that is run by a bunch of salesmen who only know how to sell and not fix problems.

Email, Autoresponders, POP3, Mail Forwarding

If you have your own site, you will probably want to have email addresses at your own domain, like sales@yourdomain.com, etc. Does the host allow you to set up whatever email addresses you want on your domain, so that mail can be forwarded to your current email address, or placed into a mail box on your web hosting account itself? Can you set an email address to automatically reply to the sender with a preset message (called an autoresponder)? Can you retrieve your mail with your email software?

Control Panel

This is called various names by different hosts, but essentially, they all allow you to manage different aspects of your web account yourself. Typically, and at the very minimum, it should allow you to do things like add, delete, and manage your email addresses, and change passwords for your account. I will not sign up with a host where I have to go through their technical support each time I want to change a password or add/delete an email account. Such tasks are common maintenance chores that every webmaster performs time and time again, and it would be a great hassle if you had to wait for their technical support to make the changes for you.

Web Server and Operating System

Is the type of operating system and server important?

In general, most people will want to sign up for a web host offering a Unix-based system (like Linux, FreeBSD or OpenBSD) and running the Apache web server. Most web-based software assume your website is running on such a system, and you will usually experience fewer compatibility issues with it. There are also a lot of guides available on the Internet on configuring such systems, so finding help when you need it is easier as well.

In my opinion, the only time when you will want to use a Windows server is if you’re running Windows-specific programs, like ASP scripts. But even then, you’ll probably be better off looking for a PHP-equivalent, and using a Unix-based system.

Price

I was actually hesitant to list this, but I guess it’s futile not to. However, I would caution that while price is always a factor, you should realise (“realize” in US English) that you often get what you pay for, although it’s not necessarily true that the most expensive hosts are the best.

Monthly/Quarterly/Annual Payment Plans

Most web hosts allow you to select an annual payment plan that gives you a cheaper rate than if you were to pay monthly. My current personal preference is to pay monthly with all new web hosts until I’m assured of their reliability and honesty. Paying monthly allows me to switch web hosts quickly when I find that the current host does not meet my requirements: this way, I’m not tied down to a bad web host because I have prepaid for an entire year. I do this even if the new web host guarantees that they will refund the balance if I’m dissatisfied, since at the point I sign up, I have no assurance that they will honour their guarantee. Later (usually after a couple of years), when I’m satisfied with the host, I may change payment plans to the discounted annual plans.

Resellers?

Not all hosting companies own or lease their own web servers. Some of them are actually resellers for some other hosting company. The disadvantage of using a reseller is the possibility that you are dealing with people who don’t know much about the system they are selling and who take longer to help you (they have to transmit your technical support request to the actual hosting company for it to be acted upon). However, this also depends on both the reseller and the underlying hosting company. It is thus wise not to rule out all resellers; there are a number of reliable and fast ones who are actually quite good and cheap. In fact, a number of resellers sell the same packages cheaper than their original hosting company. If you find out that a particular company is a reseller, you will need to investigate both the reseller and the real hosting company.

International

If you don’t stay in the USA, you have the option of hosting your site with some local provider. The advantage here is the ease of dealing with them (they are after all easily accessible by phone call or a visit), your familiarity with the local laws and easy recourse to those laws should it be necessary. It should be your choice if your target audience is local (eg a local fast food delivery service). On the other hand, hosting it in USA has the advantage of faster access for what is probably the largest number of your overseas visitors (particularly if you have an English-speaking audience). You also have a large number of hosting companies to choose from, and as a result, cheaper prices too.

About Post Author

Anjali Punjab

anjalipunjabb@gmail.com

Happy

0 0 %

Sad

0 0 %

Excited

0 0 %

Sleepy

0 0 %

Angry

0 0 %

Surprise

0 0 %