Quick Nav:  Online Store   |   Login | Register

Will Snapsis CSS menu solve my problem?

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.
AuthorMessages
Steve Malkin
<20 Posts
Posts:4


07/30/2007 8:15 AM  

Hi,

I am using the Standard DNN 4.5.3 "Blue -Full Width" skin with the standard horizontal Solpart menu.

The problem I have is that the javascript <script> tags which are written to the page to include the menu functionality do not include a 'type=text/javascript' attribute

(Ie when I right click on the page and do 'View Source' I see:  <script src="/js/dnn.controls.dnnmenu.js"></script>  in the page source.

This causes me a problem because the client for this site is a government agency and their security policies do not allow their browsers to load any scripts which do not have the type/language specified. When they view the site from their PCs the standard menu fails to load.

I have tried to locate the place in the DNN code where the script tag gets written, so that I could change it to make it include the type attribute, but it must be burried somewhere in the depths of the source code and I can't find it.

So my questions are:

  1. Can I use the Snapsis CSS menu as a replacement for the standard DNN one?
  2. Do I have to create a whole new skin to do this or would it be possible to 'plug in' the Snapsis menu to the standard DNN skin?
  3. If I use the Snapsis menu will it suffer from the same behaviour that is causing the standard menu to fail ie no type attributes in the script tags?

I hope the Snapsis menu will be able to do what I'm looking for, it might really dig me out of a hole!!

Cheers

Steve

John Mitchell
Posts:3478


07/30/2007 9:48 AM  

Hi Steve,
The Snapsis CSS Menu is not a direct replacement for Solpart, you will still need to define your styles to get it to look like the solpart one.  This menu will give you much more control over the output though and is standards compliant.  You don't have to create a whole new skin, just replace the references to the menu in your current skin.

If you just want to make that script output compliant you may also be interested in using PageBlaster to correct the output of the page before it is sent to the browser.

Steve Malkin
<20 Posts
Posts:4


07/31/2007 1:38 AM  

Thanks for the information,

I like the idea of using the PageBlaster module to correct the output of the pages on the fly and tried downloading the free evaluation version to check out if I can make it work.

I went through the 'mock' purchase process and got to the end of that expecting there to be a "Download" link to get the module, but I can't see one.

How does the delivery process for the evaluation version of the module mork? 

Cheers

Steve

John Mitchell
Posts:3478


07/31/2007 10:03 AM  
Hi Steve,
It works just like a real order. If you login to the site and go to the "My Orders" page, then click on the order details for that order, you will find a download icon for each item that has a download available.
Steve Malkin
<20 Posts
Posts:4


07/31/2007 11:20 AM  

Hi John,

I found the download link (obvious once you'd pointed it out) and it seems to be doing the job perfectly.

I will place the order for the full version as soon as I can persuade my pointy haired boss to crack open his wallet...

One question:

I have set it up at the moment with about 10 different 'Replacement Rules' to modify each of the <script> tags I have identified as needing the "type" attribute adding.

Would there be a significant performance improvement if I were to devise a single rule thet could identify any <script> tag that didn't contain "type=text/javascript" and use that instead?

My knowledge of regular expressions is practically nill and I wouldn't want to put the time and effort into trying to do that unless it was likely to give a noticable speed improvement.

Many Thanks once more for your help with this

Steve

John Mitchell
Posts:3478


07/31/2007 11:42 AM  
Hi Steve,
Yes it can be faster to use the RegEx engine with a multiple rule than it is to run seperate rules.
For the text/javascript and text/css I do it in two steps by first removing all the types and then adding them back like this:
<searchFor><![CDATA[<(style|script)(.*?)(type=.*?)(\s|>)(.*?)>]]></searchFor><replaceWith><![CDATA[<$1$2$4$5>]]></replaceWith><searchFor><![CDATA[<(script.*?)>]]></searchFor><replaceWith><![CDATA[<$1 type="text/javascript">]]></replaceWith><searchFor><![CDATA[<(style.*?)>]]></searchFor><replaceWith><![CDATA[<$1 type="text/css">]]></replaceWith>
Steve Malkin
<20 Posts
Posts:4


07/31/2007 12:05 PM  

Wow!

Thanks John, that works perfectly, and much neater than the way I was doing it.

You're a real star.

Thanks

Steve

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 >CSS NavMenu > Will Snapsis CSS menu solve my problem?



ActiveForums 3.7
Powered by: Snapsis Software