Recent Questions
Q: We are a registered user of deluxe menu.
We are using your Deluxe-Menu.
We have one problem we have implemented menu in our html page.
It works very well in IE but there is a problem in firefox.
It display gap between two menu.
A: 1) You can move search engine friendly code inside the NOSCRIPT tag:
<!-- Code for Deluxe Menu Items. Generated by Deluxe Tuner -->
<noscript><a href=http://deluxe-menu.com/>Javascript Menu by Deluxe-Menu.com</a>
<div class="dmlinks" style="font:normal 11px Verdana;color:#000000;text-decoration:none">
<a href="default.html">Home</a>
<a href="products.html">Products</a>
...
<a href="channel_partners.html">Partners</a>
<a href="feedback.html">Feedback</a>
<a href="http://blogs.innowera.biz">Blogs</a>
</div>
<!-- End of Code for Deluxe Menu Items -->
</noscript>
You won't see links when your page loads in that case.
2) You should specify the following parameter:
var itemSpacing="0";Q: I am afraid I am still having difficulties.
Key issue is fine, no problems there. However, I cannot seem to make this NOT showing me a window open example when the page opens. I just want to have popups upon click. What I want is to be able to create links, within the same page, that will popup windows of different content and size, all upon click (not upon page loading.
What am I doing wrong here?
In the site I have the following:
1. A www.domain.gr/deluxe-popup-window.files folder
2. A http://www.domain.gr/deluxe-popup-window.js script
3. and my test page creating the popups
So, in my sample page:
1. I do NOT want to have the 1st popup which loads automatically as the page opens
2. I want to have the 2 samples shown there, Sample 2 and Sample 3.
3. These 2 samples must show windows of different width and height.
Please help me here.
Looking forward to your answer.
A: Delete openAfter= text from the deluxePopupWindow.attachToEvent()function in the following file:
http://www.domain.gr/deluxe-popup-window.js
In that case popup window won't show till you click on the link.
deluxePopupWindow.attachToEvent(win,',,,,,')Q: I am contacting you on behalf of my client World of Envelopes as they currently use your menus. We are currently running their SEO campaign and would like to know what is search engine friendly about your new javascript hover menu?
Would it be possible for you to provide me with an example of a client that is currently using this new menu so I can assess the SEO ability of this menu.
A: You should generate search engine friendly code and install it on yourpage.
Deluxe Menu is a search engine friendly menu since v1.12.
To create a search engine friendly javascript hover menu you should add additional html code within your html page:
<div id="dmlinks">
<a href="http://deluxe-menu.com">menu_item_text1</a>
<a href="http://deluxe-tree.com">menu_item_text2</a>
...etc.
</div>
To generate such a code use Deluxe Tuner application.
Run Tuner, load your menu and click Tools/Generate SE-friendly Code (F3).
We use search engine friendly code on our website,
http://deluxe-menu.com
You can view source of the page.
Q: I have been using Deluxe Menu quite a bit, but am now running into a problem on a site I developed. When I add a submenu, it appears separated by about 100 pixels down. In this case I left it on the Menu Item “Why Maumelle” for you to look at.
Can you help me out?
A: See, the problem is that the script can't get css properties of the object if they are described in separate .css block (or file).
In other words, you can't get the value of "position" attribute of the object if the object doesn't have this property within inline style(style="position:relative"). To get the value you should move .css style into style="" attribute.
Please, try to add your
css file -> inline css, for example:
For example, you should add style="position:relative;"
to the
<DIV class=MainBody>
<DIV class=Banner></DIV>
<DIV class=Menu>
So, you'll have:
<DIV class=MainBody style="position:relative;">
<DIV class=Banner></DIV>
<DIV class=Menu style="position:relative;">
Now we have only such solution for this problem.
We'll try to fix this problem in the future versions.