Community 7 - Mentions: The requested page is not a part of the current theme.

We're experiencing the same problem. Have you already found out what the problem was?

We're experiencing the same problem. Have you already found out what the problem was?

Well, probably not the right one ;-)  The problem I'm  having is that I'm searching for a correct way to work with a team of developers on one Theme with version control. To reach this goal I tried to copy the map 'generic' in the map 'www/themes/' and rename generic to our company name. In the site theme tab it is possible to select the new theme, but when I'm navigating to the website homepage I'm receiving the folowing error:

[CSException: The requested page is not a part of the current theme.]
   Telligent.Evolution.Controls.ContentFragmentPageBase.OnInit(EventArgs e) +246
   System.Web.UI.Control.InitRecursive(Control namingContainer) +134
   System.Web.UI.Control.InitRecursive(Control namingContainer) +290
   System.Web.UI.Control.InitRecursive(Control namingContainer) +290
   System.Web.UI.Control.InitRecursive(Control namingContainer) +290
   System.Web.UI.Control.InitRecursive(Control namingContainer) +290
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +489

Bump! Did you ever resolve this issue? I'm having same problem with site loss from a UAT environment we set-up, database is fine, put back site, connected to the database and now same error, same YSOD.

Any clues much appreciated.

We did. Thing was, the page was indeed not part of the current theme ;-)

Check if your filestorage is linked correctly.

Check if the type of page (site/group/blog) has a coresponding theme file. In our case I only had a sitetheme, and no group theme files. You can always copy the fiji files for testing purposes.

Good luck

Filestorage is fine, when you mention check type of page - where do I do that - forgive my ignorance!

Mark, you mentioned in your support case that you're running in Azure.  Would you mind providing a few more details about your Azure set-up?  Are you using custom Azure VM images, Azure Web Roles, Azure Web Sites?  How are you running Solr & the Job Scheduler?

Also, are you using a custom theme.  The default page layouts for a theme are stored in the file system.  If you  were using a custom theme, and then lost your filestorage, you would have lost the default page layouts for your custom theme, even after restoring the original filestorage.

I can vouch for Mark as we're both working on same site.

Solr & Job Scheduler are running exactly as per the installation guide on c: drive, we've put the site on a separate e: drive, database on a seperate VM (web server is also a VM).

Theme was left as Fiji.

We decided to install a fresh site and database, creating a new "blank" site and new database without the config_override, thus without Job Scheduler - all worked worked fine (as in site shows up on web browser, can log in, out etc etc).

Gonig back to the original troublesome and restored site, we deleted the contents of the file storage area from the recovered site, deleted the config_override, stopped the Job Scheduler in Services, then copied across the web contents from the "blank" site except the db connection string which we left as the original and "undamaged" database.

The site suddenly worked, all content and group settings test blog posts etc intact.

We then restored the config_override, started up Job Scheduler and still everything works fine.

It's a head scratcher this one!

Just to clarify, you are using Azure VMs, rather than Azure Worker Roles / Azure Web Roles?

It seems like the problem was all caused by the removal of your filestorage folder.  Some of the theme configuration is stored there so if you loose that, you'll loose your themes.  If you need to do a restore, you'll need to restore both the /filestorage/ folder and the database.