Per Nergård (MVP)
+2
Feb 16, 2012
visibility 4213
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
Composition Over Inheritance: Why Your Content Contract Is Not a Base Class

Inside the structural conformance pattern in SaaS CMS — from server-side inheritance to pipeline governance. A contract in Optimizely SaaS CMS is...

Vipin Banka | Sep 19, 2026

Optimizely Opti ID Integration: Why the API Key Was Missing from the DXP Management Portal

While working on an Optimizely CMS 12 Opti ID integration recently, we ran into an issue that initially appeared to be related to SSO authenticatio...

Madhu | Sep 18, 2026 |

Extending a Contract: What You Can Override

Contracts share fields across content types — but not every field setting can be overridden. Push the same contract onto several components, and CM...

Chirag Khanna | Sep 18, 2026 |

Building a Blazor Server UI Inside the Optimizely CMS 13 Admin Shell

What I learned shipping a Blazor Server UI inside Optimizely CMS 13 — Razor components in a NuGet package, the Blazor hub next to MapContent(),...

Stanisław Szołkowski | Sep 17, 2026 |