Knowledge Base support case for AllWebMenus, abstracted and stripped of all user’s private info.


Initial Email From:
David
Initial Email Subject: Problem with AWM 5
Support Case Month: September 2012

Dear Likno,

Since upgrading our AWM from V4 to V5, we have experienced problems with our sites utilizing the “styleswitcher.js” javascript file.  When we click to switch style sheets to text only, all menu item reside on the same vertical and horizontal plane.  Since they all occupy the same space, you can’t read or use the menu.  When we reverted back to the old AWM 4 files, the problem was corrected.  Apparently there is some sort of incompatibility issue between styleswitcher.js and the AWM 5 files but, not so, for AWM 4.  We need your help in resolving this since we only have 1 employee who retained the old AWM 4 software after we upgraded.  Your assistance is greatly appreciated.  The AWM files currently on the site were created on AWM 4, thus, they work fine.

David

Reply From: Likno Customer Support

Hello,

Can you please give me some more information on the “styleswitcher.js” file? Is this your own custom script file? What exactly is it supposed to do?

I checked your page and it seems that when I click “Text Only” the menu simply disappears. Is this the expected behavior? And does this not happen with v5?

Regards,
Kostas
Likno Customer Support
www.likno.com
Create any type of javascript menu (CSS menu, drop-down menu, sliding menu), button, html tree, modal window, tooltip, accordion, tab, scroller, jQuery slider or design for your websites!
Like us on Facebook – Follow us on Twitter

Reply From: David

Dear Kostas,

Sorry it took so long to get back to you.  In response to your question, no, this is not the expected behavior.  We think you probably used a browser other than IE.  In IE, when you click “text only” (upper top corner), the page looks like “Example 1” (zipped attachments), at least when compiled with AWM 4.2.  When compiled with AWM 5.3, we get “Example 2” and can’t figure out why it fails to work correctly.

I’ve attached the html for the home page of this site (index.html), as well as the styleswitcher.js (shareware) file created for this function (switching between 2 or more style sheets) and both style sheets for the text and graphic versions of the site.   The folder contains the compiled AWM files for the menus in both 4.2 and 5.3 versions.

We trust this is all the information you require to tell us how to resolve this ongoing problem we’ve had since upgrading to version 5.3.  Please contact me if you require further information.  In the interim, we appreciate your assistance in this matter.

Website: http://www.ilponline.org/

David

Reply From: Likno Customer Support

Dear David,

I checked your page and I see that the Menu Linking Codes are not exactly after the <body> tag as expected, but instead they are within other page tags (specifically the DIVs with IDs “to” and “gv”).

The recommended solution is to move the Linking Codes outside of these tags. If however this is not possible, you can still resolve the problem by selecting the following Project Property in AllWebMenus:

linking code within tags

Please let me know if this corrected the problem.

Regards,
Kostas
Likno Customer Support
www.likno.com
Create any type of javascript menu (CSS menu, drop-down menu, sliding menu), button, html tree, modal window, tooltip, accordion, tab, scroller, jQuery slider or design for your websites!
Like us on Facebook – Follow us on Twitter

Reply From: David

Hi Kostas,

Did as you suggest with the results attached.  As you can see, now both menus are visible in either mode with the graphic (white text menu) on top.  The ID’s “to” and “gv” stand for text only and graphic version.  Working with the styleswitcher file and both style sheets, they are either set to display or hide the menu when switched between style sheets.  That’s why each AWM menu is within these tags.

Example 3 displays the submenu panel from the text only (black text) version showing

Example 4 shows the graphic menu white text covering part of the black text in the text only menu in the lower part of that menu. 

So, unfortunately, this is not the solution to our problem.  Somewhere between AWM version 4.2 and our current version, the way AWM builds these menus changed.  That is why 4.2 seems to work flawlessly with this configuration and the new version does not.  Will await any further ideas.  Thanks Kostas

David

Reply From: Likno Customer Support

Dear David,

I did not realize that you were just hiding these DIVs. In this case, maybe you should try using Element Positioning and adding the positioning DIVs inside the “to” and “gv” DIVs respectively.

Let me know how this works out.

Regards,
Kostas
Likno Customer Support
www.likno.com
Create any type of javascript menu (CSS menu, drop-down menu, sliding menu), button, html tree, modal window, tooltip, accordion, tab, scroller, jQuery slider or design for your websites!
Like us on Facebook – Follow us on Twitter

Reply From: David

Hi Kostas,

I don’t understand what positioning would have to do with the problem which is that all the AWM web menu items in the column are compressed one on top of the other into 2 or 3 horizontal lines (they’re squished down) on the text only version.  Interestingly, if the web page opens up on the text only version and you switch to graphics version, then that is the menu that is compressed (squished).  It’s always the version that you switch to after the page is opened that displays the problem compressed menu.  But only with AWM 5.3

Reply From: Likno Customer Support

The “squishing” part may be caused because the Linking Code is within tags. If you put it outside it should work.

However you want the menu to show/hide. This can also be achieved by showing/hiding the positioning element. Hence the solution I suggested. Not 100% sure that it will work, but it is worth a try.

Indeed several things have changed since v4 and this is why the Linking Code must always be a direct child of the <body> in v5 to avoid possible problems such as the “squishing”.

Regards,
Kostas
Likno Customer Support
www.likno.com
Create any type of javascript menu (CSS menu, drop-down menu, sliding menu), button, html tree, modal window, tooltip, accordion, tab, scroller, jQuery slider or design for your websites!
Like us on Facebook – Follow us on Twitter

Reply From: David

Well, it was worth a try.  Unfortunately, it didn’t work.  Same results (squished on text only).  Await next step.

Reply From: Likno Customer Support

Can you send me your two menu projects so that I can run a couple of tests here? (to save time)

This is what you should do to export your project into a ZIP file and then email this ZIP to us.

export menu project

Regards,
Kostas
Likno Customer Support
www.likno.com
Create any type of javascript menu (CSS menu, drop-down menu, sliding menu), button, html tree, modal window, tooltip, accordion, tab, scroller, jQuery slider or design for your websites!
Like us on Facebook – Follow us on Twitter

Reply From: Likno Customer Support

Hello again,

I tested my theory with your projects in a test page and it seems to work just fine!

Are you sure you did this correctly? Did you move the Linking Code directly under the <body> as I asked you?

Please check the test I am sending you and let me know if this works in your case.

(starts with both visible – then use buttons)

Regards,
Kostas
Likno Customer Support
www.likno.com
Create any type of javascript menu (CSS menu, drop-down menu, sliding menu), button, html tree, modal window, tooltip, accordion, tab, scroller, jQuery slider or design for your websites!
Like us on Facebook – Follow us on Twitter