Menu Problem SSL

John,

I recently installed and configured the SSL options for my DNN site and I received the latest version from DNN Masters SEO.

The navigation at the top of my site has a link called Ask Us. The url is being translated as undefined.aspx. I check the URL rewrite rules in DNN Masters SEO and the page is rewritten properly as ask-us.aspx. Why would the snapsis menu store the URL as undefined.aspx?

Thx for your help

Jaime

Well I know when I remove DNN Masters SEO the SSL redirect works fine, as none of the URL's are rewritten. When I re-enable DNN Masters and regenerate URL's it rewrites the "ask us" URL as undefined.aspx.  The ask us page  has ssl enabled. If I leave it alone it will redirect to unedfined.aspx,  but obviously this is undesirable. When I edit the URL rules and change undefined.aspx to ask-us.aspx the SSL redirect breaks and I get a 404 not found. The raw data in the tabs table looks fine... I wish dnn had better ssl support than this

I don't understand why it ever gets changed to undefined.aspx to start with. Is that something that happens in the DNN Masters module until you define it?

What do you need the CSS menu to do differently?

I use a javascript method to switch to SSL and back on this site.

var secureUrlPattern='login|Cart';
 if(location.protocol.toLowerCase()=='http:'&&location.href.match(secureUrlPattern))
     location.href=location.href.replace('http:','https:');
 else if(location.protocol.toLowerCase()=='https:'&&!location.href.match(secureUrlPattern))
      location.href=location.href.replace('https:','http:');

I dont want the menu to do anything differently. I assume the page name is appended to the anchor tag and a "-" is used as a replacement character. The page name should not be undefined its called ask us

Hmmm.. I just tested with my sitemap page and it works....I am going to create my ask us page again from scratch then enable ssl again and see what happens.

Looks like recreating the page did it...Something was wrong with tabid 73...not sure why but its fixed thank you for the support

John,

Well maybe I do I have a suggestion.... Your script rewrites the protocol to secure or unsecure depending on the current connection. If I am on https all my links in the css menu will be re-written using https and vice versa. This means performance will take a small hit on a redirect from the webs server. I have gotten around this on my site by hardcoding all the links to either http or https depending on whether the page is secured as defined by the pages dnn properties. I guess it would be great if the CSS menu would also look at the IsSecure field in the tabs table to determine whether to write the URL as http or https. Maybe I am looking at this too simplisticly since I have not looked at your code ( nor do I have the time ;-) ). Maybe I am missing details that you took into account when you wrote the module