-
Injecting slugs in EPiServer URL for multi language websites
My current client has a need to inject region information at the start of the URL’s path in one of their EPiServer websites. For the Stockholm region, this may look like /Stockholm/path/to/page. However, the website is also in multiple languages causing EPiServer to inject it’s own slugs for language management: /so-SO/Stockholm/path/to/page (Somali). My collegue Svante…
-
Virtual pages in EPiServer using partial routing
As mentioned in a previous article about storing data in EPiServer’s blob storage, we had the need to create around 18k worth of virtual pages. Using the ID-slug mappings talked about in the article, we implemented a partial router. The virtual pages are retrieved from a third party system, and their titles occasionally changes. When…
-
Storing your own data in EPiServer’s blob store
One of the things that you need to consider when deciding where to store your data is the performance of accessing it. Will it be accessed rarely? Will you be updating it frequently? We recently created access for around 18k worth of virtual non EPiServer pages which are retrieved from a third party system. The…
-
Useful safety check for the property and content type subset functionality
In the articles Different subsets of properties in different EPiServer multi sites using same content type model and Different subsets of content types in different EPiServer multi sites with all types in one assembly you can read about adding subsets of properties and content types to different EPiServer installations that run on the same code.…
-
Different subsets of content types in different EPiServer multi sites with all types in one assembly
As I explained in my previous article Different subsets of properties in different EPiServer multi sites using same content type model my current client is building a common platform for 7 websites spread over 3 EPiServer installations. As the platform grew the need for restructuring grew as well. It was no longer viable to keep…
-
Different subsets of properties in different EPiServer multi sites using same content type model
For my current client we are building 7 websites spread over (at least) 3 EPiServer multi site installations. Rather than seeing each of them as separate entities, they all consume the same base code from a common platform (such as infrastructure, EPiServer content types, and so on). An issue that you’re facing when using the…
-
Page instance based EPiServer Output Cache
For a client’s website there was a need to implement EPiServer‘s output cache with different expire times not based on PageType, but rather page instance. After weighing pros and cons we decided on a solution with a number of ContentArea properties on the website’s settings page. Pages dropped in each area would then get different…
-
EPiServer Content Delivery Api only returns 404 NotFound
Lately I spent some time investigating 404 NotFound responses from an EPiServer Content Delivery Api installation. While the SiteDefinition Api URL worked just fine, the problem was that the API returned 404 NotFound for all contents requested. Here are some pointers to determine possible reasons. Thanks to Svante Seleborg for helping out with debugging. EDIT:…
-
React and EPiServer: Removing properties from output in EPiServer.ContentDeliveryApi
If you read my previous article React and EPiServer: Aggregated output with EPiServer.ContentDeliveryApi you saw a way of including your own aggregated data through properties in the content model classes. Since the JOS Content Serializer also has a very useful ignore attribute, ContentSerializerIgnoreAttribute, I’d love the EPiServer Content Delivery Api to have one as well.…
-
React and EPiServer: Aggregated output with EPiServer.ContentDeliveryApi
If you read my previous article on React and EPiServer: Moving to EPiServer Headless (EPiServer.ContentDeliveryApi) with friendly URLs – Quick POC, you’ll know I wanted to output EPiServer Content information by friendly URL to a page rather than using the headless API’s own paths. This I did, but what about aggreagated information? You know, the…
-
React and EPiServer: Moving to EPiServer Headless (EPiServer.ContentDeliveryApi) with friendly URLs – Quick POC
So EPiServer released a beta version of the ContentDeliveryApi. Nice. My current client uses the JOS Content Serializer for creating JSON data from EPiServer pages for view, preview and on-page-editing with React, as described in previous articles. However, sooner or later it will be neccessary to start using EPiServer’s own methods for this. I had…
-
EPiServer’s ServiceLocator will not prevent you from doing proper unit testing
I often hear people saying things like “Don’t use the ServiceLocator, you can’t write unit tests with it”, or “EPiServer‘s ServiceLocator will really cause problems in your unit tests”. It really will not though, and it’s quite easy to set up. Simple base class for unit testing with EPiServer’s ServiceLocator Quite often the argument is…
-
React and EPiServer – Generic pass-through property handler for JOS ContentSerializer
In a previous article I wrote about React and EPiServer – Custom rendering of EPiServer block in XhtmlString field without partial block controller, as we’re using the JOS Content Serializer to make JSON of our EPiServer content. This is in order to pass it to React. We were using the version 2.0.1, and it differs…
-
Adding custom valid child tags to EPiServer TinyMCE
In an attempt to prevent TinyMCE from splitting up the p-tags when dropping an EPiServer block into an XHtml property field in edit mode, I tried adding div as a valid child to p within the editor. As we have added custom rendering of your blocks for JSON output (see article React and EPiServer –…
-
EPiServer TinyMCE 3 Wrapping selection in unsupported aside tag
For my current client, we had a need to allow EPiServer editors to wrap XHtmlSting field content in aside tags in a user friendly manner. The first most obvious thought went to the styles drop down list and EPiServer’s editor.css file, however after a few tries and a bit of Ilspy‘ing I realized that the…
-
React and EPiServer – Getting friendly URLs in EPiServer’s XHtml fields using JOS.ContentSerializer for React support
So just a follow up on the previous article React and EPiServer – Custom rendering of EPiServer block in XhtmlString field without partial block controller in regards to friendly URLs. We noticed that all our internal EPiServer links in the XHtml field properties remained on the internal form ~/link/{guid}.aspx, even in the view mode. The…
-
Blank page in Umbraco site after installing Vega IT’s uSiteBuilder
I ran into some trouble after installing Vega IT‘s uSitebuilder NuGet package on my newly created Umbraco website. The whole site suddenly went blank, and all I could get from the network traffic was a 500-error without body. Nothing was being written to the logs either. I’ve seen blank pages before, and sometimes they’re caused…
-
React and EPiServer – Custom rendering of EPiServer block in XhtmlString field without partial block controller
For my current client we’re building a component based platform as a common feature hub for serveral large EPiServer websites. For this, we have stripped away the default Razor based rendering that is normally used for the view and edit modes, and replaced it with React all the way through. Having React render blocks through…
-
EnvInject plugin variables not getting injected from properties file in Jenkins build step
Today I had a bit of a struggle with the Jenkins EnvInject Plugin while trying to inject custom variables from a properties file into my MSBuild step. Everything that I added to the Properties Content field was successfully injected, and looking at the log, the EnvInject reported successfully injecting my file envVars.properties variables as well.…
-
EPiServer Forms: JavaScript error – cannot read property ‘validate’ of undefined
I saw this JavaScript error earlier this week, and thought I’d write a few lines about it. It appears as you try to submit a form created with the EPiServer Forms functionality, that likely has custom validators on some of it’s fields. As EPiServer Forms tries to run it’s client side validation on the fields…