Hi!
I have a number of context menus made for some filetypes via Settings->File Types->System File Types->{extension}->Edit->Context Menu. In order to migrate to another PC I need to create by hands all new context menu items for each command for each file extension, because Settings->Backup and Restore can't backup and restore these settings.
Is there a way to automate migration of DOpus-specified context menus to another PC?
Backup & Restore will backup any Opus-specific file type context menu items or file type events (double-click etc.), since they're part of your Opus config.
But file type menu items and actions which were added such that they also work in File Explorer and other software need to be written into the standard registry locations, rather than the Opus config (since only Opus understands its own config files), and won't be included in the backup.
Those things in the registry are no different to any other context menu items in the registry added manually or by other software. Even Opus itself doesn't know that they were added or edited by Opus.
The best way to back those up for transfer to a new PC is probably to use RegEdit, or manually re-create them, depending on the number and complexity of them.
Those look like Opus-specific commands.
If you want to check for sure that they're part of your config, type /dopusdata/FileTypes into the location field and find the file there corresponding to the type. Open it in a text editor and you should see the commands in there.
Anything in those files will be included in your config backup.
One thing to note, however, is that everything is tied to the file type class, not the extension. The class can depend on which other software is installed, and which software is set to open the type on double-clicks. For example, I have Foobar2000 as my music player and have assigned WAV to it, which changed the WAV file class into foobar2000.WAV. If I restored my config to a machine which didn't have WAV assigned to Foobar2000 then any commands I had added to the foobar2000.WAV class would be ignored (until Foobar2000 was installed and given the type; then they would affect things again).
There's no any pdf-related files in /dopusdata/FileTypes folder on source PC. But I found Export feature in the File menu at the top of File Types - Directory Opus window. It successfully exported pdf-related context menu to *.dft file.
However, destination PC's DOpus can't import it. File Types - Directory Opus just flashes for a while and no any context menus appears in PDF context menu...
They may be there but under a class name that you don't expect. e.g. Named after the program that handles them.
That sounds odd. So you can't use the File Types UI at all on the new machine? Could you paste a screenshot of what it looks like?
They may be there but under a class name that you don't expect. e.g. Named after the program that handles them.
Indeed, it's in Appd4nrz ... 723.orx file!
That sounds odd. So you can't use the File Types UI at all on the new machine? Could you paste a
screenshot of what it looks like?
Not so File Types - Directory Opus window works well, but when I import PDF File context menu.dft File Types - Directory Opus window hides for a while (0.5 sec), than appears again, but no result. Context menu for PDF files still absent.
I discovered new file AppXd4nrz8ff68srnhf9t5a8sbjyar1cr723.oxr in folder /dopusdata/FileTypes on new PC (maybe because of import process). How can I attach it to PDF filetype?
Those AppXd4nrz8ff68srnhf9t5a8sbjyar1cr723 type of identifiers are the awful, obfuscated names which Metro (Windows Store, UWP, whatever Microsoft are calling that garbage this year) apps use instead of readable names in the registry.
You can probably rename your old file to the new one's name to apply it on the new machine.
You can probably rename your old file to the new one's name to apply it on the new machine.
It doesn't work.
Also Import function doesn't work too...
Could you debug Import function for File Types? Must I write new post for bugreport or you consider this one?
I think the import function works, but it's importing settings for a file type class that doesn't exist on your new machine, so you won't see any difference.
So, how to create file type class manually and will it work for my purposes?
One weird thing: on source PC there is .pdf file type made by Foxit reader, on destination machine Foxit reader made .ppdf file type (and there's no any .pdf). What causes such difference?
You'd have to ask the people who make Foxit that question.
So, I’m trying to edit existing .ppdf context menu because I haven’t .pdf extension registered.
File Type editor has new item – Clear METADATA.
If I open context menu for any of .pdf file no pdf-context items are shown. No Clear METADATA at all.
Please, suggest what can I do to add .pdf context menu?
If FoxIt hasn't added a PDF type, it's probably going to cause problems outside of Opus.
I would ask FoxIt for support to get to the bottom of that first, then worry about adding extra items to the context menu.
You can create new types in Opus, using the New button under the list of types (visible in your screenshot). You can also add extensions to existing types when editing the types themselves. But something must've gone wrong with FoxIt if it didn't create a PDF type, and fixing that via FoxIt is probably the best way forward.
