Per Nergård (MVP)
Feb 16, 2012
  4019
(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

Please login to comment.
Latest blogs
Optimizely CMS 13: Why Search & Navigation Now Means Graph Migration

Optimizely CMS 13 makes Graph a required part of the platform. Here is what that means in practice for teams moving from Search & Navigation, with ...

Wojciech Seweryn | Apr 8, 2026 |

Jhoose Security Module V3.0.0 – Site-Level Security Configuration for Optimizely

Jhoose Security Module updated for Optimizely CMS 13, introducing separate packages for CMS 12 and 13 with ongoing support and enhancements.

Andrew Markham | Apr 6, 2026 |

Searchable settings page

In my current project which has been actively developed for quite some time we have a big classic settings page. Unfortunately the placement and...

Per Nergård (MVP) | Apr 6, 2026

Using Azure Devops Pipelines in Optimizely SAAS (Configured) Commerce

Introduction When working with SAAS Commerce build service v2 your currently need to use a github repo with configured branches to start deployment...

Mark Hall | Apr 4, 2026 |