Per Nergård (MVP)
+1
Feb 16, 2012
visibility 4123
star star star star star
(1 votes)

MobilePack 1.0 installation trouble

Yesterday I was going to install the new 1.0 Mobilepack for a customer demo.

I didn’t start this with plenty of time before the meeting because I thought it would go like a breeze.

But to my big surprise the installation of the .episervermodule via deployment center failed with a cryptic error message about the bulk installation failed.

So I renamed the module to a zip file and extracted it to see if I could do a manual install.

I wasn’t to happy to see that it would mean manually fixing som xml changes in web and episerver.config.

Lucky for me I started with trying to import the EPiServer demo pages and page types.

When doing this I got an error about not having a VPP with the name “SiteGlobalFiles”

So I just tried to change the name attribute of one of the VPPs and voila the installation worked as expected.

I also noted that the demo content is created for the english language although my site had globalization turned off and all content set to Swedish.

I guess this will be fixed in the near future but maybe it can help someone.

Feb 16, 2012

Comments

Jacob Khan
Jacob Khan Feb 17, 2012 04:03 PM

Thanks for the blog post, yes the sample site is built for an alloy or standard type of installation where all page types are allowed under the root/start page, a vpp for global (image gallery) and English as a language (en not en-us like in commerce). We could make an epimodule only for the page types and not import any pages if that is something that is needed from the community. We will probably not make a package for each language. If someone wants to contribute a language package they are welcome to do so on mobilepack.codeplex.com

error Please login to comment.
Latest blogs
Add more scheduled job settings from the Optimizely CMS 12 admin UI -- with OptiScheduledJob.ExtraParameters

  Optimizely (EPiServer) CMS 12 ships a great scheduled-jobs framework, but it has one frustrating gap: a job has nowhere to store its own...

Binh Nguyen Thi | Jun 25, 2026

Automated Search & Navigation to Graph Migration with Claude Code

A Claude Code plugin that scans your S&N codebase, applies Graph SDK transformations, and validates the result. Install once, run one command. CMS ...

Connor Fortin | Jun 24, 2026

Migrating from Find to Graph: Lessons Learned from a Real CMS 13 Project

While migrating a search solution from Optimizely Search & Navigation (Find) to Optimizely Graph in CMS 13, I encountered several issues that were...

Binh Nguyen Thi | Jun 24, 2026

Optimizely: Upgrade Opti-ID and .NET 10 in CMS 12

Many Optimizely customers are planning their roadmap around a future migration to Optimizely CMS 13. As a result, upgrades such as Opti ID adoption...

Madhu | Jun 23, 2026 |