Nina Meiers
 Posts:41

| | 01/23/2004 10:51 PM |
| Hi
I'm raising this question because I have I have lovingly installed this fantastic technology of CSS skinned sites on my website.
While I love this technology, I also installed the speerio container manager on the site as well, and having problems with it.
I have the container manager running on another site, with no CSS manager on it, and no problems at all.
I'm now wondering what to do.. because each module is great, but this makes me wonder if I need to start setting up different dnn databases that incorporate only some features and not others.. it's all a bit frustrating because i'm starting to get small errors that I never noticed before and I'm not in a position to modify each module I purchase. I was hoping that the installs I buy are just a simple click and install, upload a few files and away you go..
Any comments shedding some light on these quirks would be greatly appreciated.
Nina
| | Nina
http://www.xd.com.au http://www.skincovered.com
....Make sure you last words are sweet.. you never know when you have to eat them... | |
|
|
|
John Mitchell
 Posts:355

| | 01/24/2004 5:09 PM |
| I'm not sure what errors you are getting Nina. I also have the Speerio Container manager and the CSS Skins module on the same host and haven't noticed any problems.
There may be a javascript confilct, or Namespace issue, but I think we all try to keep things as unique as possible.
One easy and quick way to see if the CSS Skins module may or may not be playing nice is to copy the original DesktopDefault.aspx & EditModule.aspx back over the ones that were included in the module. This will change everything back to using the default DNN classes.
When you find out that it wasn't the CSS Skins module ( hopefully ), you can just copy those two pages back to turn it back on again.
Also, If you post some of the errors I might be able to help more. | | | |
|
Nina Meiers
 Posts:41

| | 01/25/2004 8:24 AM |
| Thanks for the reply John. I'll try that and and keep you posted.
:-)
Nina | | Nina
http://www.xd.com.au http://www.skincovered.com
....Make sure you last words are sweet.. you never know when you have to eat them... | |
|
janet Fox
 Posts:2

| | 01/27/2004 10:15 PM |
| hm...
I have sperio container manager on my site with css skins too.
My issue is this. My skin keeps reverting back to classic Dnn skin.
I purchase the gradient green skin and loaded it. I then logged on as the host and applied my new skin. It looked great! I then called my son and had him have a look....
He could only see the classic dnn skin. So then I cleared my cach and looked again and sure enough there was the blased classic dnn....
I've reloaded the site...recomplied then reloaded. I do not get the same issue on local host even with cach clear. I am stumped.
Is there a conflict with these two module??? Please say no and that I've just loaded something wrong....
Thanks,
Janet | | | |
|
John Mitchell
 Posts:355

| | 01/27/2004 10:26 PM |
| Hi Janet,
The administrator can change skins and will be able to see the effects without changing the site for the rest of the visitors because the skin selection is saved in a cookie for the administrator only. This allows tweaks to be made on a live site without "going public".
Once the administrator is satisfied, the skin can be made available for all to see by clicking on the "apply" link next to the skins drop-down list box.
| | | |
|