Per Nergård (MVP)
OMVPSaaS CMS Developer CertificationCommerce Connect 13 Developer Certification +2
Feb 16, 2012
visibility 4256
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
Surviving a Dirty Feed. Part 3: Error Handling and Event Batching

Committing a 250,000-row Optimizely catalog import row by row, returning a per-row failure report, and coalescing catalog events into one per batch.

Stanisław Szołkowski | Oct 16, 2026 |

Building UI Extensions for Optimizely SaaS CMS

Introduction Developers have been extending the functionality of Optimizely PaaS CMS for years using addons built in C# and deployed as NuGet...

Mark Stott | Oct 15, 2026

Cheapskate AI Translator: Because Translation Should Not Require a Second Mortgage

There is a particular kind of software project that begins with a detailed architecture document, a product roadmap, and a carefully assembled...

Linh Doan Cuu | Oct 15, 2026

Computed Fields in CMS 13 Content Contracts with Optimizely Graph

Content Contracts in Optimizely CMS 13 allow different content types to share a common structure when querying Optimizely Graph. But what if the...

Mardy | Oct 14, 2026