http Compression for css-Files and another question

Rate this topic:

Please Register to post a reply. Another benefit of registration is the ability to subscribe to and recieve notifications of new posts.

Author

Messages

Patrik

Posts:42

01/29/2007 2:58 AM
Hi Our website got quite fast now by PageBlaster 2.0. Is there any way how one could compress the css-Files as they are quite large? Do you plan to integrate css-File compression into the next version of PagePlaster? There is another question which doesn't belong here. It's a DotNetNuke question which I asked it at www.dotnetnuke.com but never got an answer. It would be great if you could provide me with a short answer. For my website (DNN 4.4.0) I'm using a Portal and an Admin Skin. The Admin Skin is showing the Solpart Menu (with the Admin and the Host Menu) and the Logoff Button. Whereas the Portal Skin is using the Sixxac Menu-Modul and doesn't display the Login . When I login as Admin or Host the Portal Skin gets used instead the Admin Skin. When I click into one of the Control Panel Icons (Portal, Users, etc) the Admin Skin gets loaded and I get access to the Admin and Host Menu and to the Logoff Button. When I worked with DNN 3.0 the behaviour was different. I'm very interesting to know whether this behaviour is normal state in DNN 4.4.0 or quite unusual. Thanks in advance for any help Patrick

John Mitchell
Posts:3085

01/29/2007 7:41 AM
Hi Patrick, Yes I do plan on an doing something with CSS and JS for a future version. I don't know if it will be the next version, but if not it will be within the next couple of months. For the admin skin question, I have not noticed a different behavior in 4.4. The admin skin is only used when you are doing administrative functions like editing settings, etc. Feel free to use my DotNetNuke Support site anytime that you cannot get a question answered elsewhere.

Patrik

Posts:42

01/29/2007 10:09 AM
Hi Mitchell Thanks a lot for your fast reply as always! I'm looking forward for the next version of PageBlaster. Concerning my DotNetNuke question and your answer: When I log into DotNetNuke as Admin. I get the Portal skin first and when I use an administrative function within the Admin environement (like editing settings) then I get the Admin Skin. For me it sounds a bit strange that the Admin Skin doesn't get loaded from the beginning when someone has logged into DotNetNuke. I'm not happy about this because I don't use the solepart menu and the login/logout button on the portal skin. Thanks for your support Patrick

John Mitchell
Posts:3085

01/29/2007 10:19 AM
Yes it is strange, but DNN has always worked that way. I could point you to several posts where I suggested that Admin & Portal skins where just too confusing and should be combined into a simpler method (same with Host Level and Site Level skins). You may be interested in a recent skin switcher I did for Skincovered.com subscribers that allows users in different Roles to be assigned a different skin. Also on the Skincovered site is a free NavList SkinObject I released just for the purpose of putting an Admin Menu on skins where you are using an alternate navigation system.

Please Register to post a reply. Another benefit of registration is the ability to subscribe to and recieve notifications of new posts.

Forums >Snapsis Product Support >PageBlaster > http Compression for css-Files and another question