EPiServer Archive
When working with EPiServer sites, a not all that uncommon type of support case is the need to change text on a page which is not editable through the Edit mode. Quite often, this text is located in language files on the web server, and it may be rather tiresome for web editors having to send change requests to the support or development team just …
When a customer wants to move their site from version 4 of the EPiServer platform to a later one, the URLs will change. It is very likely that so will the ids for the migrated pages. Here is a simple method for retaining functioning bookmarks, unbroken links from other websites, keeping RSS readers happy, while at the same time feeding search engines 301 – Permanently …
A customer asked me to see what I could do for their XForm order notification e-mails today. Apparently the department handling their incoming orders was receiving really long e-mails with loads of superfluous information; this as every field in the XForm was being submitted to them, and not just the ones containing data. This is the default behaviour of the XForm functionality, which of course …
This is a follow up to my previous post about allowing web editors to dynamically change the content of their static error pages (this one). The solution I described would not let us insert any graphical elements requiring database access; such as images from EPiServer’s VPP folders. Here is a way to do it; sample code can be found at the bottom of this post. …
Some time back, I encountered the need to dynamically alter static error pages through EPiServer’s edit mode; or more specifically, edit an error page for a 500 Internal Server Error, caused by a database related failure. Since it might be tiresome for editors to change static files on a webserver, and since EPiServer tends to enjoy having a database connection retrieving pages, I needed to …