Update: I was able to resolve most of the problems by creating another version of my skin on the server this way:

     1. Create a new empty folder for another skin on the server.

     2. Copy the entire contents of the original jqueryui-1 skin (old one, not the new one) to the new folder on the server (from development PC).

     3. Overlay the layout.Master, style.css, stylemenu.css and style-reset.css from my new skin from development PC to server.

So now all the old files from jquery-ui-1 are there except the 4 files I changed.

Now almost all the html generating from SiteMenu and SiteTitle is correct, so my new styling is there.

Still one problem though...when there are sub menu items (pages) under a top menu item, the triangle that points down and renders to the right of the menu item is not generating on the html side. This is causing the width of the menu items with children to be narrower and if a child page title is longer (then the top menu item title) it wraps, but the height of the sub menu item is not long enough to handle it and the text overflows.

On development I have (for my second menu item (currently inactive) - starting from the <li>:

     <li class="sf-with-ul">
                <a href="/our-properties" class="inactive sf-with-ul">
                    Our Properties<span class="sf-sub-indicator"> »</span></a>

                <%the submenu ul, etc is here%>

On the server I get this:

          <li class="sf-with-ul">
                <a href="/friendwelldemorevisedpublish1/our-properties" class="inactive">
                    Our Properties</a>               

                  <%the submenu ul, etc is here%>

So I'm missing one class on the <a> tag and the entire <span> along with it's content.

I was hoping that if I created the pages now on the server, it would correct the problem, so I created a subpage for a top item page that did not have subpages. However this did not do it.

The site is here for reference: dmendoza.net/friendwelldemorevisedpublish1

In general, I followed the advise in the documentation by starting with a copy of an existing skin that had a layout closest to the look of what I was aiming at for my new skin, and then modifying the css, testing each modification as I went. I got great results from this in my development environment, but I'm getting hung up on deploying the skin to the server. My deployment situation is further complicated by the fact that I like to first deploy to a subfolder, but eventually need to re-deploy from the staging/subfolder site to the final site that uses a root folder (no subfolder). So would really appreciate some general advise also on the best way to deploy new skins!

Thanks

Dan 
 

Yes, thanks. I just found it also. The <portal:SiteScript> link was also missing the subfolder.

What do you think of the second method I used to deploy the new skin? (Deploy a copy of the old one first, then overlay only the files that were changed). Why does this appear to be necessary for SiteMenu and SiteTitle to generate right?

Thanks

Dan

Hi Joe,

Thanks for your comments; they are really helpful. I had 2 other problems, but was able to find them using the Firefox console.

I have another question though. I modified jqueryui-1 so I'm using a horizontal superfish. I have the situation where two of the top level menu items are only there to allow for drop downs for child menu items. I made them unclickable per your instructions for treeview menu, and now they do not go to any page when clicked. However, when they are clicked, the content that was in the main part of the page (the CMS part) goes away (except a small sliver of white). Is that normal for a mojoPortal unclickable menu item? I was expecting for them to do nothing at all, leaving the main part of the page alone that was rendered from the prior clicked menu item. (Also the Firefox console is clean after clicking the unclickable menu item, except for a bunch of CSS warnings I'm always seeing).

Thanks

Dan

Hi Joe,

Sorry I got confused about the flex menu. I have the unclickable now. I had to adjust my styles a bit with the new rendering, but looking much better now!

Thanks for all your help,

Dan