I think I may have found a bug.
I'm using Directory Opus 13.9.2 beta
I created a command to JSON file type called Test that runs C:\Windows\System32\NOTEPAD.EXE "%1"
but when I right click and click on Test, it fails with an "Unspecified error" (my Windows in in Portuguese)
When I do the same thing, but with a BAT File Type, it works
I was wondering if it may be related to the fact that json has 4 characters and bat 3.
What happens if you run notepad.exe on the same json filepath via a Windows command prompt?
If I run
C:\Windows\System32\NOTEPAD.EXE "C:\Temp\aaa - Copy.json"
using WIN + R
or using Command Prompt
it works (opens the file in notepad)
Thanks!
Is the context menu item also visible in File Explorer? (Can depend on the type of command chosen when creating it.)
If it’s visible there and works, but doesn’t work in Opus, then it might mean something is blocking it being opened via Opus.
A screenshot of the full command definition (including command type etc.) might also reveal something.
Hm out of curiosity I tried and it gave me some error about the file not having an associated application. The extra strange thing is I do indeed have json files associated with Visual Studio code.
However it works when I create the entry to run as an Opus function:
Hi ThioJoe! Big fan!
I confirm that if I create the entry to run as an Opus function, it also works for me.
Ok I might have discovered something. Originally my JSON file type entry had the name set as something like "Adobe After Effects JSON". But I renamed it to just "JSON" and now the same command seems to work 
Also now works if I rename it to something else like "JSON Test":
So maybe try just renaming the file type description?
Edit: Another thing I just checked is that in the registry under HKEY Classes Root, it seems that the .json key has its (Default) value set to something After Effects related. So I wonder if maybe some other application has "hijacked" the association somehow. I'm not really sure how file associations work at this level in Windows, especially since again I don't even have json files associated with After Effects, it must be something AE did itself.
Another Edit:
I tried using the Export feature and while it didn't include the JSON file type's current entry and settings, it did show a duplicate copy entry of the JSON type I had made before as a test, which does indeed show the same string that's in the registry. So it must have pulled the value that After Effects set at some point which might be confusing it.
<filetype name="Adobe.AfterEffects.json.24">
<commands />
<shell>
<command name="Test2" position="0" />
</shell>
</filetype>
Though what's weird is I had deleted that duplicate entry but it still shows up in the export file.
I tried renaming the description (before it was "JSON File") to "JSON", but when I right click and click on Test, it gives me the same error as before.
Then I tried deleting the .json registry entry on HKEY Classes Root. The actions I created before on Directory Opus were gone, and even the File Types window in Directory Opus didn't show any json entry (as expected). Then I manually created a JSON entry as following:
And recreated the action:
But when I right click on the json file and click Test, it still gives me the same error
Well I definitely wouldn't have just deleted the .json entry in the registry 
I'd re-create that just to be safe. This is what it should be by default based on a fresh virtual machine I checked on:
In any case seems like maybe it's a different problem altogether.
Side note though seeing the default value does shed light on why the other error was happening on my system. I guess After Effects "redirected" the .json extension to some new filetype it called Adobe.AfterEffects.json.24:
It's ok, I created a backup before deleting. Thanks for the reply!
