#18 closed defect (worksforme)
Scripts dropdown menu?
Reported by: | guest | Owned by: | somebody |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | component1 | Version: | |
Keywords: | script menu | Cc: |
Description
Using eCS 2.0 rc4 and WPSWizard 0.6.1a2.
A menu item 'Scripts' is added to the menu bar of every folder. In version 0.5.2, there would be a dropdown menu when this was clicked on consisting of the items in the 'Scripts for Folders' folder in the 'Menu Configuration' folder.
Now (0.6.1a2) there is no drop down menu when 'Scripts' is clicked.
Change History (4)
comment:1 by , 17 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
comment:2 by , 17 years ago
I checked those items you mention... they are set as you describe. The trashcan is clean and I have uninstalled and re-installed several times - each with no apparent problems. Scrubbed the INI files in between each install - all functions seem to work fine except this one.
I decided to make a fresh install of eCS on a blank partition (on a different machine), then installed WPSWizard and indeed it does work properly. There must be something I have installed that interferes with the 'Scripts' dropdown....
comment:3 by , 17 years ago
OK... I have to apologize - this falls into the 'Stupid user tricks' category. I did not have the 'Extended context menu' item checked in the configuration. Sorry...
comment:4 by , 17 years ago
Keywords: | script menu added |
---|
I changed the check box text from "Extended context menu" to "Extended menus" to make clearer that the script menu will also be affected (I already forgot about that).
In addition the script menu item won't be shown in the menubar at all when either the feature is disabled or no items are available.
The package is not properly installed on the system. There were no changes wrt scripts since v0.5.x.
-Check if the folder "Scripts for Folders" exists in the "Menu Configuration Folder"
-Check if this folder has the ID "<SKRIPTS_WPFolder>"
If the ID is lost reassign it. You may just run the installation again to try to resolve the issue. There is no need to uninstall first.
Check if you have some older configuration folder floating around left over from an old WPS-Wizard installation still taking the ID.
This old config folder may perhaps reside in the XWP trashcan.