Home › Forums › Campus Pipeline

Luminis IV.0.2.0 headaches

Thu, 2008-02-07 14:24 — Howler72

We just upgraded to Luminis IV.0.2.0 and are experiencing a new issue. The deployskintemplate script no longer functions properly. Prior to IV.0.2.0 we had succesfully deployed new skins, however after the upgrade this is no longer the case. When going throught the script it creates the directory structures and files, we then enabled the skin. When going to the system admin menu and applying the skin the name we gave the skin is missing from the drop down list. Very frustrating. I noticed that one of the configman values is missing the values of the skins we created.

skin.available.list=classic

Anybody else experience this?

0
No votes yet
‹ Person_3 Documentation or access a user's roles Removing / clearing user customizations (channel layout) ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Wed, 2008-02-13 16:26 — andrusp

Yes - same problem

I went in and added the new skin to the list with configman
configman -s skin.available.list "classic myskin"
and bounced the web server and it now shows

Fri, 2008-03-28 17:57 — wjdennen

Thanks!

Thank you for this. I ran into this same problem with a fresh IV.0.2 install.

Your fix worked.

Anyone know how to change the default skin to be the new skin?

deployskintemplate used to ask you if you wanted the newly deployed skin to be the new default, but it doesn't ask that now.

Thu, 2008-04-24 12:50 — jestyr

we are having the same

we are having the same problem. anyone have any thoughts on this?

Thu, 2008-04-24 20:45 — wjdennen

hotfix

Looks like this is fixed in the recent IV.0.2 hotfixes:

hotfix 11 - deployskintemplate was not adding the skin to the skin.activelist.