The error occurs with ScriptWizard itself and several of your other scripts as well for me (e.g. SetVar = no error, StartHidden = error). It always happens when I have more than one lister open. As soon as I close all but one listers it's working fine again. If I close the last lister having only the preferences window open the error occurs again. The dialog will always open fine when started from the button you provided. Uncommenting line 139 fixes the error but probably makes other problems.
In fact I found that I only had a single script where german Umlauts didn't show correctly. Changing the character encoding from Unicode, UTF-8 to Windows 1252: Western European fixed the issue.
SW is currently not working with the german forum. I tried with the german version of FullSceenMetaEdit. The Visit Forum button is working fine but the Check Version button throws this error:
2014.11.22 07:54:55 Opening url [haage-partner.de/forum/viewtopic.php?f=45&t=4751]
2014.11.22 07:55:06 Check..
2014.11.22 07:55:06 UpdateCheck(): "Command.File_FullscreenMetaEdit.vbs.txt":
2014.11.22 07:55:06 E Error: Verweis auf eine nicht definierte Entität 'uuml'.
2014.11.22 07:55:06 E Line#: 118
2014.11.22 07:55:06 E Line : <li title="Produktübersicht"><a href="http://www.haage-partner.de/software.html">Software</a></li>
2014.11.22 07:55:06 E Failure: Resource parsing error - reason [Verweis auf eine nicht definierte Entität 'uuml'.
That sounds great although I have no idea how this could be done. I'd be glad to assist translating dialogs, column names etc. (I'm gone for some days but next friday I'll be back).
support for german h&p directory opus forum (was an easy adjustment, but still considered alpha status)
full caching of column data (alpha status, do not enable for regular use, cached data won't refresh, but is lightning fast! o)
added some default resource center urls for various add-ins
@kundal
With the updated version I get your expected results for the german forum (no downloads/no version in download details).
Which is either because there were *.zip files used or because of no version information is found in the uploaded file comments.
That 139er error you get is obscure.
I just try to get the enumerator for selected files from the sourcetab and wouldn't know why that would fail.
You say it always works when "about" is called from the button, so how do you actually run SW to get the error? Thx! o)
I just updated to v0.4.2 and the file was broken. Encoding was UTF16LE and it contained some invalid characters at lines 1190/1191. When manually downloading the file it was Windows 1252: Western European and working.
Support for the german forum seems to work now. The "Unsupported: No downloads found for script!" message is because it's a *.zip file. I'll test with a valid script file.
The error occurs when clicking the Info button of a script in Preferences=>Toolbars=>Scripts. It possibly doesn't make much sense to enumerate selected files in this case? I couldn't find anything not working when uncommenting the line. However, I don't know if this makes sense for you but changing line 144 to if (files) return { enumerator:new Enumerator(files), count:files.count}; also works fine for me.
Update from the german forum doesn't work. I always get Failure: unique version id mismatch. After deleting the uid from the local file (older version) the update succeded but the downloaded file was UTF16LE containing only some characters this forum refuses to show and PNG.
This happens if the file on the forum is UTF-8. If it's Windows 1252: Western European I get the error Systemfehler: -1072896748 which means that there is an encoding problem.
How should the Update MD5 function work? I expected that the MD5 string shown if Show Details was clicked would be added to the script but it doesn't.
upload prepared files will be automatically converted to unicode (utf16)
downloads always treated binary
Sorry Kundal! o)
Any download for a german script-resource was attempted at this site, that's why that PNG file sneaked in for no obvious reason. o)
"Show Details" does not modify a script. For the hash to update, you need to choose "Update MD5 Hash" or use "Prepare Upload" which does that automatically (only if the file was modified). But the last download was faulty in that regard, should be working again.
The "Unique version id mismatch" was caused, because a PNG file does not have that ID.
That UID-safety feature kicked in here, preventing SW from overwriting your pretious script-addin (additionally safety to the backup made).
Thanks for the link and your patience! o)
With that script of yours an update was possible for me now. I hope it works for you too.
Yeah! Everything working fine now (except the mysterious multiple lister error, now line 150). I'm glad I could help to optimize this great masterpiece.
Next weekend I'll join the party and make all my scripts fully support SW (already done but unpublished for Tagger).
For the internal english-german dictionary I think it's enough to translate dialogs and column names. German users are very used to english script output and log file contents. A dictionary is a nice idea which I can probably also use with my own scripts making it unnecessary to always maintain two versions.
I have the same problem with DO11.8 English, but German Windows 7 Professional, 64 Bit:
File Command.Generic_ScriptWizard.js.txtis renamed to Command.Generic_ScriptWizard.js and saved in ...\Directory Opus\Script AddIns as fred stated.
Any hints?
This is exactly my setup. Could you open the "Other Logs" utility panel (script log) and see what happens there, if you rename the file "Command.Generic_ScriptWizard.js(.txt)" in "/dopusdata/script addins" into "Command.Generic_ScriptWizard-Test.js"? DO will reload the file after the rename and you maybe see an error message. If the log stays clean, the add-in needs to appear in preferences / toolbars / scripts, unless there's some unknown magic going on.
Please report your findings.. o)
@fred
In case you read this, did you manage to get it working?
I normally run Opus in Windows 7 at the office or Windows 8.1 at home but I also maintain an XP virtual machine for testing purposes. When I fired up my current configuration on the XP VM, DOpus threw a couple of error messages...
..and thereafter DOpus behaved badly and had to be killed with Process Explorer. I figured it had to be a script causing the problem and after removing all and selectively restoring isolated it to Command.Generic_ScriptWizard.js
Hi aussie! o)
I can only guess where this error comes from. If you fire up DO, it will intialize ScriptWizard, which trys to delete a deprecated script in "script addins".
The deprecated script is called "Command.Generic_ScriptHelper.js(.txt)". There's no other "delete" action going on in the initialization phase of ScriptWizard.
Maybe you could try to comment out the corresponding lines and see if it cures the Problem? Search for "deprecatedScriptPath" and the two DELETE QUIET FORCE raw commands (around line 82).
I don't know why DO gives you that error, as it should not. But maybe that's the same problem user fred and opusfreak ran into.
Unfortunately, they did not report back yet. So fred and opusfreak? Please come back, so we can fix this all together! o)
The upcoming version will not use DOs DELETE command to delete the obsolete script if it's there. The mysterious dialogs should be history then. Thank you for investigating! o))
Please read the red addition in the thread-opening for update instructions. This version will use an alternative download location if updating from here fails. I'm sorry for any inconvenience, but the forum did change without me noticing an announcement or something.
Hi tbone,
Wow, you and others have been making amazing things with the script feature since DO11 came out.
Only now starting to experiment with some of the scripts. Not sure if this is directly related to ScriptWizard, but some features like "Update" are failing on my system with an error message about a semi-colon. But scripts such as SelectRandom are running properly despite the error message. Would you have any insights?
Here is a picture of the status using your columns:
fix for alternative download location not working (damn it! o)
Thanks for reporting! o)
There are two people involved in this error situation. Leo and me. o) Leo changed the FAQ link at the top, using an unescaped "&", which brakes the xml-parsing. But my fault is more severe of course. o) The alternative download feature, made for situations exactly like this, to provide required code adjustments, did not kick in, because I had a copy&paste error in the scripts internal id, arrg - I could eat my *ss. o)
You're the man Leo! o) Thank you, now it's all polished and shiny again! o)
Sorry for not revisiting earlier, I was down with influenza past week, inluding delirium - I saw colorful things and such, ugh! o)
