Greetings!

We used DHTML builder a couple years ago (yes, a couple years..) and it worked very nicely for us. Our website hasnt changed all that much in the past couple of years. Version 4.2 I believe.

Today, I made some changes in the menu structure (renamed and moved some things around), recompiled, re-installed the loader code, and now I cant seem to get the menus to show up on the bulk of the web pages.

The 'main' category level menus show up fine on a couple pages, and appear to function fine as well.

such as here: http://www.congressgroup.com/current.html
and here: http://www.congressgroup.com/projects.html ...

However, each page that is an 'item' on these menus.. the menu is not showing on the left hand side. Full meus should be appearing on the left side here:

Such as this: http://www.congressgroup.com/project_100arlington.html
and this: http://www.congressgroup.com/project_embassy.html
..there are about 20 or so pages like this, with no menu appearing on the left.

I also note the 3rd menu I have here - seems to work perfectly... I also did not change anything on this one. the menus show up on all the pages linked to it...
here: http://www.congressgroup.com/prin_dfs.html

Note the 'toolbar' at the top is not DHTML related code. Just the menu on the left side of the pages.
--------------

Now, I did not change ALL the item level pages in any way besides reinstalling the loader code. I renamed a few and moved a couple items from one menu group to another. Something is up.. something I overlooked. Would anyone have any help to offer? As you can see this is a live website so I cannot leave it 'broken' like this I will have to revert to the former version soon, but I thought I would leave it up for a bit to see if anyone could offer advice.

Thank you kindly! I still think this is a great product, I, sadly, just have not used it very much recently and having trouble getting past this.

Note:

I updated from 4.20.023 to 4.20.025 recompiled, reinserted, several different times... and started getting JScript errors and it got uglier, so I had to scrap it and put the site back to the way it was.

I am going to start again from scratch, maybe simply recompile the menus and make sure everything is still working before I try and reorganize them.

Hello spr,

Before you do anything, can you please check if your project is using some sort of custom code either through a custom AddIn or through the "Advanced Offset" section?

- To check if it's using an AddIn click File->Project Properties->Advanced
If it's using one, please email me that AddIn so that I can make sure that its code is compatible with the latest version (as many things have changed since pre-4.20.24 versions).

- To check if you have some custom offset settings click File->Project Properties->Advanced->Menus Offset->Advanced and see if there are any custom definitions created.
Again, if there are custom definitions, then email me the .dmb project so that I can verify the code.

Thank you for the timely response, I do appreciate it.

Coincidentally - I remembered the custom code just a little while ago. Found the problem to be the fact that I am examining the document title to conditionally hide/display these menus and something in there was not sufficintly unique or was otherwise messed up.

code: 'return document.title.indexOf("Project")!=-1;
or: 'return document.title.indexOf("Current")!=-1;

If the document titles include "Past Projects" or "Current Projects" you wll always get the 'project menu'... of course as 'Project' evaluates true in both cases.

I am still unsure why the menus at one point were not displaying, but I must have got sloppy in my naming - after doing it again, it seems to be working fine. I have not completed all of the edits I need to make but everything is appearing as it should and functioning so far... and the menus are switching correctly between 'Past Projects' and 'Investors/Current Projects' correctly.

http://www.congressgroup.com/current.html

Again, thank you.

On a different note... while I have your attention.... I see a note here that I made regarding Chrome:

*Version 4.20.017 found to be problematic in Google Chrome & Opera. Menu/toolbar does
not correctly appear until the browser window is manually resized. ** This behavior is only displayed
when ExpressionWeb interactive buttons are 'Preloaded' which generates code into the BODY 'onload' event.
Fix is to include a small hack at the end of the HTML page BODY:
( <script type="text/javascript">f7();</script> )

I am manually sending an F7 at the bottom of my page to address this. Do you know if this condition still exists? I thought perhaps you would know and save me some testing. ;-) I am happy to leave as is, but the less custom code, the better I always say.

Cheers,

Steve R.

Hello Chris,

Excuse me for the late response.

As for your last question:
This issue is not entirely related to DHTML Menu Builder. The problem is that some script developers, when they add event handlers, they do not check to see if there are other functions already attached to those events thus removing previous attachments.
This is why, some times, DHTML Menu Builder's menus are not notified when the page is loaded.

Having to use that "custom code" will depend on how other scripts on the page attach themselves to the "on page load" event handler.
If they "check" if there are other active handlers (as DHTML Menu Builder does) then it won't be required, otherwise you will need to leave it as it is.

Hello Chris,

Excuse me for the late response.

As for your last question:
This issue is not entirely related to DHTML Menu Builder. The problem is that some script developers, when they add event handlers, they do not check to see if there are other functions already attached to those events thus removing previous attachments.
This is why, some times, DHTML Menu Builder's menus are not notified when the page is loaded.

Having to use that "custom code" will depend on how other scripts on the page attach themselves to the "on page load" event handler.
If they "check" if there are other active handlers (as DHTML Menu Builder does) then it won't be required, otherwise you will need to leave it as it is.