Recent Questions
Q: We're running deluxe_tree version 1.0. We are getting the following error:
_tsw is not defined
[Break on this error] String.prototype.sb=function(tss,te){return this.substring(tss,te)};String.proto...
dtree.js (line 14)
Any ideas? Should we upgrade to the latest version? If so, what it the upgrade path for us? Will we have to modify our data-tree.js file?
A: Yes, try to use Deluxe Tree v2.4.
See in Deluxe tree you should specify correct tWorkPath parameter:
<script type="text/javascript"> var tWorkPath="menudir/";</script> otn=tx/tl hre=T-"/ mt ae"ecito"cnet"nac orwbiewt it utn n e c
This parameter should point to the same folder with dtree.js file.When you use movable or floatable feature you should copy dtree_add.jsfile in the same folder with dtree.js file.
http://deluxe-tree.com/installation-info.html
Q: I've just updated my menu from 2.4 to 3.2. All is fine except two of my java script pop up menu (vertical) appear on the left instead of the right, all the others pop out to the right as before. I've tried saving it as a completely different file name, same problem, both within a browser and within your preview pane.
Any help would be much appreciated, I'm at a loss.
A: You can try to change the following parameter:
var subMenuAlign="left";
You can also send us a direct link to your website, so we can check it.
Q: All of a sudden I'm getting the 'Incorrect Copyright" on two of my sites.??
Here's what I have in the file:
<!-- Deluxe Menu, Deluxe-Menu.Com -->
<noscript><a href=http://deluxe-menu.Com/>Javascript Menu by Deluxe-Menu.Com</a></noscript>
<script type="text/javascript" language="JavaScript1.2">vardmWorkPath = "menudir/dmenu.js";</script>
<!-- (c) 2005, Deluxe-Menu.Com -->
What's wrong??
A: What version of the menu you're using?
Now we have new version of the menu v2.4. We've fixed "IncorrectCopyright" message in IE7 in it.
How to upgrade to v2.4
---------------------------------------------------------------
You can download the licensed engine .js files from the same link in your license message.
Deluxe Menu v2.4 has new parameters and features.
To upgrade to v2.4 you should do the following.
Step 1.
1.1 For Windows users
a. Install new license package. (you can download it from the same link in your license message)
b. Run Deluxe Tuner v2.4
c. Open menu data file (.js file where menu parameters are placed):
select File/Open…
d. Save the file: select File/Save, then click "No" button when the dialog box appears.
1.2 For other OS users
a. Open menu data file (.js file where menu parameters are placed) in a text editor.
b. Make sure that the following variables exist in the data file:
var keystrokes = 0;
var dm_focus = 1;
var dm_actKey = 113;
var dynamic = 0;
var smHideOnClick = 1;
var itemAlignTop = 'left';
var smSmartScroll = 1;
var dmAJAX = 0;
var dmAJAXCount = 30;
var dmRTL = 0;
var dmObjectsCheck = 0;
var menuBackRepeat = "repeat";
var menuHeight = "";
var transDuration2 = 200;
If one of the variables doesn't exist - add it at the beginning of the file.
c. Save the file.
Step 2. Now open HTML-page that contains Deluxe Menu.
Step 3. Replace existent <noscript></noscript> tags of the menu by the following code:
<noscript><a href="http://deluxe-menu.com">Javascript Menu by Deluxe-Menu.com</a></noscript>
See more info about installation here:
http://deluxe-menu.com/installation-info.html
Step 4. Save HTML-page.
Step 5. New engine v2.4 has 7 .js files.
They are:
- dmenu.js
- dmenu4.js
- dmenu_add.js
- dmenu_dyn.js
- dmenu_key.js
- dmenu_cf.js (new v2.00)
- dmenu_popup.js (new v2.00)
Replace all old .js files by the files from v2.4.
Try that.
Q: I am a software developer interested in using deluxe menu for my company’s website. One of the important features of our website is multiple language support, typically Chinese.
Does deluxe menu have support for Chinese or other Unicode characters?
A: You're able to use any characters for Deluxe Menu in the same way asyou use them for standard html page.
The only issue is that submenus can be shown in incorrect positionwhen you're using dir=rtl for your page.
Please, try a trial version.