Try with : /.*/ instead.
You need to write it as a literal regular expression, so you can include flags if needed.
1 Like
Thanks for the quick response! That was the problem and it will save and match patterns for me now.
However, one more issue.. When I tried using a flag (s for dotAll), it failed in the same way.
For example, the pattern /^(.{0,30}).*$/s doesn't work and is automatically cleared if I try to use it.
Is my usage of the flag incorrect?
Unfortunately you can only use flags that are supported in JScript (i,g, .etc).
If the regex can't be parsed it will be removed.
Not tested, but something like this might work:
Regex: /^([\s\S]{0,30}).*$/
Replace: $1
1 Like
Ahh I see, I was looking at general javascript flag support, not JScript so that makes sense. No problem!
Thanks, using a slightly modified version of your pattern, it seems to be working perfectly!
Regex: /^([\s\S]{0,30})[\s\S]*$/
Once one clicks the Configuration / Gear icon in the Script Management window, the script management window can no longer be moved, or minimized.
Can you please make it possible to move or minimize the the Script Management window of your wonderful Script?
EDIT: I got it working again, but I'm not sure how!
I cannot get OpusExifTool columns to display data!A few days ago some data was displayed, but inconsistently and only after a long wait.Same with ExifTool Columns-Plugin (I know it's not your Plugin)OpusMediaInfo columns are fine.I am trying to figure out any possible reasons.
Is it correct that ExifTool does not have to be installed because the DOpusScriptingExtension?
I do have ExifTool Installed but have not updated it in a long time.
Does ExifTool GUI dialog work?
Is it correct that ExifTool does not have to be installed because the DOpusScriptingExtension?
Yes, DOpusScriptingExtension comes with its own version of ExifTool. You can see it in C:\Program Files\DOpusScriptingExtensions\exiftool
Thank you.
Please include the version number in the zip filename.
If both have issues, then it might be the DLL.
If you have the latest version of DOpusScriptingExtensions installed, try downgrading to another version, such as v21. I think there have been some issues with some antivirus detecting it as malware.
You can also paste the script debug info here so I can troubleshoot the issue.
First go to Preferences / File Operations / Logging / Script/FTP and check everything in the Prefix section.
Then, in the Script About window, change ScriptLog to DEBUG.
Finally, in a folder with a few sample files, reproduce the problem and then paste the log from the ScriptLog pane.
You can also use both OpusExifTool and OpusMediaInfo with the .exe only. It's explained in the first post.
However, it's a bit slower as it is now. But since I recently discovered a new way to make Opus add-ins work faster, and I was also tired of using an Access database for the cache, so I have an early version that's (very) fast, doesn't need the DLL anymore, and has a proper DB now. That version might eventually become the new base.
Thank you, but the ExifTool Columns-Plugin (by lxp) does not use the DOpusScriptingExtension, and it's not working either.
FYI: I have commands that use Exiftool, and they are working, so that means the issue is not Exiftool itself.
I thought you were talking about this other add-in.
Commands that runs Exiftool using the DLL plugin by PolarGoose? I was talking about that.
Feel free to post the info I mentioned then. I can take a look later.
That is what I was referring too.
In the Scripts dialog, it's called ExifTool Columns-Plugin. It's not working either and does NOT use use the DopusScriptingExtension. So I find that odd.
I use MS-DOS commands that use exiftool but NOT using DopusScriptingExtension, and they work.
I'm still working on your instructions.
I rolled back to DopusScriptingExtension v.21, and that didn't work. now I'll try an even earlier version.
That's not the one from lxp 
.
That one also uses exclusively the DOpusScriptingExtensions DLL 
.
I think you're understanding something very different from what I'm suggesting.
Oh! So Sorry!
However, I like yours (OpusExifTool) so let's forget about the others.
I have the Script log. Shall I send it to you by private message? I'm not sure how much of it to include.
I tried DDL versions 21, 20, and 19. No security warnings for 20 or 19. But that didn't help.
2026-08-31_MegMac_Script Output.txt (27.9 KB)
Update:
I disabled ExifTool Custom Columns 2 by PolarGoose, named ExifToolColumns-Plugin in the Script Management window, and suddenly this script started working again!
Then (because I was curious) I enabled it again and both now work!
There are several warnings like:
=> Error converting to JSON: Syntax error
That's likely because we're receiving something that can't be parsed.
Try this button and check if you get the same syntax error. You need to select a file so ExifTool will dump its metadata using the same arguments as the script does.
Exiftool test.dcf (1.8 KB)
@MegMac any news about this? I'm kind of intrigued by the issue, since I couldn't reproduce it on my end, even after reverting to v1.4.1 and DOpusScriptingExtensions v25.
As I commented previously, I think the problem was caused by having 2 ExifTool Scripts enabled and displaying a column for IPTC Keywords for both Scripts - to see if there was a difference in what was displayed.