I've been using EPiServer's built-in subscription functionality on a few 4.61 projects with no problems... when i tried it on my first version 5 one i had a few issues - namely the subject and read more links were in Swedish and i couldn't set the mail from address... Here's how i fixed them:

1. Swedish Text - Default language was set to Swedish (based on the demo content added at install time i think) - thanks EPiServer support for helping me with this.
2. "From" Email Address (and the "Read More", email "body text" etc) In 4.61 these were set on the Subscription page type, in version 5 this is done on the page that is marked for subscription (has EPSUBSCRIBE property) - you add the following properties (should be fairly obvious what they're for):
   • MailFrom
   • MailSubject
   • MailBody
   • MailReadMore

The change in point two is great - as now you can set different email address/email bodies per subscription area!

If, like me you've developed an EPiServer site using their new Visual Studio 2005 Project you may have become frustrated when coming to install it on your Live server using EPiServer Manager. For those of you that haven't, i'm referring to the bit of the install where it asks you which Module you want to install. Module? What's a Module? If you don't select one you need to install the demo site - which no one wants to do when they've just spent time creating their real site in a development environment.

After a bit of digging (i couldn't find any info on EPiServer's site) i worked out that a Module was simply a zip file! So i Zipped up my ASP_Theme folder, all my user controls, pages and language files (i left the web.config out) and copied it to the server. Then at the end of install through EPiServer Manager I chose "install module" and selected my zip - then hey presto it installed my developed site!

The next annoyance to overcome was the "now you must install basic content" option ( /admin/setup.aspx) which will only let you select to install the demo site's data... after more digging i found that this is simple too. Login to the admin page of your development site and export all data (pages types, tabs, categories etc etc) Then save the export file (give it a meaningful name) into "[WEBSITE]\Util\setup\" folder (you will probably need to create the folder) then refresh the setup page - and hey presto again - you'll now have the option to install your data rather than the demo!

In fact i'd recommend adding the .episerverdata created via the export tool to your original zip file to make the process even more streamlined.

Out of interest does anyone know how to disable the setup.aspx page from appearing? until you've ran it you can't see your page as IIS serves the setup.aspx instead (even if you've restored a database or pointed it to an exiting one)

I've recently created an EPiServer 5 project in Visual Studio, then came to deploy it to IIS and experienced none of my uploaded images (and documents) being displayed. At first i thought i'd got my Virtual Path Provider (VPP) settings wrong in the Web.Config. However i double checked and they were fine - i also was able to upload new images/documents so the path (and permissions) were fine.

I realised it must have been a problem with IIS serving the images, so after comparing the EPiServer Demo site's IIS properties i discovered the solution - i needed to enable a wildcard mapping for aspnet_isapi.dll.

This can be done by clicking the Configuration Button on the Home Directory tab of the offending site's IIS site properties. (see below)



The next screen is different if you use XP - which only has one box, but allows the extension of * to be added, Windows 2003 (shown below) separates it into two boxes



The file to add is typically located here:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll

Make sure you DO NOT check the "Verify that file exists" checkbox



Then hey presto and all my images were displayed!

I've recently had problems trying to upload multiple files to the file management console in EPiServer 5 CMS. The item in the context menu was disabled and drag and drop wouldn't work either. It turned out the user account i was using didn't have permission to drag/drop. Once i'd added it, via Admin > Permissions for functions.