your blog about Seperating Admin & Normal CSS

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

patrick1010
Posts:42

02/27/2007 10:04 AM
Hi John You wrote an article how to Put Admin only content in your DotNetNuke Skin: http://blogs.snapsis.com/PermaLink,guid,f33544f2-8275-4f1d-b72b-cacd73fea4a3.aspx I'm using it to display the Solpart Menu only on the Admin-Site as written in your article. But I noted that the /DE/controls/SolpartMenu/spmenu.js still gets included at my Website pages and is quite large 66kb. I was trying to find a way to remove spmenu.js out of my Website pages. I could do it with PageBlaster but I need the solpart menu in the Admin Portal. Do I need to go back to have a Admin and a Portal skin or do you know a way how I could make it work? I played around with the code you wrote in your excellent article in your blog about Seperate your Admin & Normal CSS for faster initial load times: http://blogs.snapsis.com/PermaLink,guid,2c5a4c45-bb33-4715-92be-578856d98661.aspx .. but it didn't worked out to remove page controls (like css, js-files). Thanks, Patrick

John Mitchell
Posts:3478

02/27/2007 10:30 AM
Hi Patrick, You can do it with PageBlaster by using a combination of the code from the blog and injecting a PageBlaster rule directly into your skin. I have attached an example skin that removes the spmenu.js from the output of your page if the user is not authenticated. You could also make it if the user is not in the admin role with the code from that article, but you may want it for logged in users to see the action menus.
Attachment: Horizontal Menu - Fixed Width.zip

patrick1010
Posts:42

02/28/2007 7:22 AM
Dear John Thanks a lot! This is an excellent feature I didn't know that I can use replacement rules even in the skin. What an amazing tool and opportunities one gets with PageBlaster! Everything works fine with only one exception (and this doesn't have to do with PageBlaster). It has to do with the Open-Search Engine: http://www.opendnn.com/nbspnbspnbspnbspOpenSearchEngine/FeaturesOSE/tabid/69/Default.aspx When someone puts a query and the result shows. The PageBlaster xml-replacement code in the skin doesn't get read. It get injected in the html output. See the attachment. I don't know why this happens. Do you know something what could help to fix this problem? Thank you, Patrick
Attachment: Problem_with_Open-SearchEngine.zip

John Mitchell
Posts:3478

02/28/2007 7:32 AM
Thanks, Yes I haven't had the time to write up tutorials on everything you can do with PageBlaster but it is getting to be a pretty powerful tool. I'll have to see why the replacements are not happenning but my guess is that the search is using a post-back. I'll look into this, but a work-around for now is to put html comments around the xml code so that it is hidden if not replaced. Another way is to put it inside a div that is no visible. < div style="display:none" > XML < /div>

patrick1010
Posts:42

02/28/2007 7:55 AM
Hi John I also like to let you know something I noted: When I use the PageBlaster ConfigCode in my skin (which is a great powerful additional opportunity) I have problems with page rules. They do not work until I remove the PageBlaster Configuration code again. Portal rules are working fine all the time. Thanks a lot for your excellent service and support! Patrick

Please Register to post a reply.

Another benefit of registration is the ability to subscribe to and recieve notifications of new posts.

Forums >DotNetNuke Support >General-DNN-Help > your blog about Seperating Admin & Normal CSS