I'm experiencing a problem where my dropbox right-click menu items are not displayed within Opus.
Specifically, the Dropbox shell extension offers three additional right-menu items when right clicking on files or folders that are inside the dropbox folder ("Share Dropbox Link"; "View on Dropbox.com"; and "Share this Folder...").
When I right-click on a dropbox file or folder inside Windows Explorer, I see these three items on the right click menu. However, within Directory Opus, right-clicking on the very same files or folders presents a right-click menu without these three options.
I enabled the debug_context_menu mode. In the debugview output, in the "shell context menu start" section, it shows that the DropboxExt extension is called, along with a number of other extensions that I've installed. However, while the other extensions show their menu items on the right click menu in opus, Dropbox does not.
Why am I seeing the context menu items in Explorer but not in Opus? I've verified that the dropbox extension is not listed in "ignore context menus" (this Preferences item is completely blank), and I've verified that the "hide windows items on file context menus" is unchecked.
Opus Version: Opus 10.5.4.0, x64. I've confirmed that the DropboxExt extension is also 64 bit.
Difficult for us to say from our side. If the debug output shows the DropboxExt is being called, but it's choosing not to add any items to the menu, then it's probably something only Dropbox (or someone with the Dropbox extension's source) could explain.
It's also worth seeing if you get the Dropbox menu items in other programs (e.g. via their File Open dialogs), in case Dropbox simply suppress their menu items outside of Explorer.exe.
Same as my previous answer: The debug output shows Opus is asking the DropBox shell extension if it wants to add any items, and it's apparently choosing not to add any. At least from what we can see so far, Dropbox are the best people to explain why.
[quote="jon"]Are you accessing your Dropbox folder through its real location or is it via a junction or link (or Library)?
I've been able to reproduce this if I access mine through a junction to the real directory, but accessing the real folder itself works ok.[/quote]
You are correct. I just confirmed this behavior. Thanks for pointing out the solution!