Changing to an invalid skin

This is the place to report bugs and get support. When posting in this forum, please always provide as much detail as possible.

Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum, do not report it as a bug.

This is the place to report bugs and get support

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.
Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum.
This thread is closed to new posts. You must sign in to post in the forums.
7/18/2007 11:07:38 AM
Gravatar
Total Posts 68

Changing to an invalid skin

Hi,

I tested what would happen if I changed to an invalid skin after install, in this case .svn. Of course it shows an error, but the thing is that it's hard to get back to a workable site again. You either have to change the skin in the datebase or copy an existing skin to the invalid skin folder.

Some mechanism for handling this would be nice. For exemple, if layout.Master (and maybe other critical files) doesn't exist in that folder, don't change.

Thanks,

Christian

7/18/2007 6:32:05 PM
Gravatar
Total Posts 18439

Re: Changing to an invalid skin

I will put this on my to do list and get to it when I can.

Thanks,

Joe

7/23/2007 8:11:05 AM
Gravatar
Total Posts 488

Re: Changing to an invalid skin

I also came across with this problem. In my case I had to change the database.

7/23/2007 9:00:49 AM
Gravatar
Total Posts 18439

Re: Changing to an invalid skin

I did add this to my list, but understand that even if I check for the existence of layout.master that doesn't gaurantee the skin is valid. If layout.master doesn't have the correct content it can still break the site by setting to the skin.

Best is to preview the change before saving to make sure the skin is good. Any skin can be previewed by adding skin=skinname to the url

Joe

You must sign in to post in the forums. This thread is closed to new posts.