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

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
Opti ID overview

Opti ID allows you to log in once and switch between Optimizely products using Okta, Entra ID, or a local account. You can also manage all your use...

K Khan | Jul 26, 2024

Getting Started with Optimizely SaaS using Next.js Starter App - Extend a component - Part 3

This is the final part of our Optimizely SaaS CMS proof-of-concept (POC) blog series. In this post, we'll dive into extending a component within th...

Raghavendra Murthy | Jul 23, 2024 | Syndicated blog

Optimizely Graph – Faceting with Geta Categories

Overview As Optimizely Graph (and Content Cloud SaaS) makes its global debut, it is known that there are going to be some bugs and quirks. One of t...

Eric Markson | Jul 22, 2024 | Syndicated blog

Integration Bynder (DAM) with Optimizely

Bynder is a comprehensive digital asset management (DAM) platform that enables businesses to efficiently manage, store, organize, and share their...

Sanjay Kumar | Jul 22, 2024

Frontend Hosting for SaaS CMS Solutions

Introduction Now that CMS SaaS Core has gone into general availability, it is a good time to start discussing where to host the head. SaaS Core is...

Minesh Shah (Netcel) | Jul 20, 2024

Optimizely London Dev Meetup 11th July 2024

On 11th July 2024 in London Niteco and Netcel along with Optimizely ran the London Developer meetup. There was an great agenda of talks that we put...

Scott Reed | Jul 19, 2024