Blighty

Hi Emily,

No, not right now (it sorts by ascending filename) – but that seems like a simple enhancement. I’ll add it as a feature in the next version of the plugin.

Cheers,
Chris

Hi Emily,

Thanks for your feedback!

If I understand your question correctly, with v1.6.0 there’s an undocumented feature that may do what you’re asking, though it’s still being fully developed.

On each different page use the bex_folder shortcode with a different root attribute, e.g. [bex_folder root="/demo/membership"] on one page and [bex_folder root="/demo/committee"] on the other, etc. These then become the ‘starting folders’ for each page’s folder navigation.

Let me know how that goes, or if I misunderstood what you’re looking for.

Chris

I’ve just released a new version of this plugin (1.6.0) that provides access control to the subfolders based on WordPress user role. This may be the solution you’re looking for.

Chris

Hi – Thanks for your question. When I was originally designing this plugin, that thought had crossed my mind, but for various reasons, I decided to opt for just sharing from within the Apps folder.

There is a workaround though. If you’re able to, you could create your own Dropbox app (https://www.dropbox.com/developers/apps) to allow full access to your Dropbox account, and replace the app_key, secret and full_access parameters in blighty-explorer.php (of this plugin) with that of your Dropbox app (you wouldn’t have to publish your Dropbox app, since only you’d be using it). That should work, but you’ll have to keep updating those parameters with any further updates to the plugin Drop me a message on my site: https://blighty.net if you need further help walking through this.

I’ll also possibly add it as a future enhancement, but I’m working on other features right now, so I can’t give a timeline for when that would be done.

Hope this helps though!

Chris

Great to hear you’ve got it working. Thanks for letting me know.

I’ve also used the User Specific Content plugin to restrict access.

In a future version of my plugin, I’m adding a root folder override and user role integration, so that should hopefully meet your needs.

Thanks!

Hi. Thanks for your feedback. It should work for any WordPress user with any role, or even if a user is not logged into your WordPress installation.

Once you, as an admin, have authorised the plugin to connect to your Dropbox account, any WordPress user can view the files/folder under the folder you’ve defined as the root folder for the plugin.

I’d say check two things:

You’ve set a root folder for the plugin so it knows what folder to share to the blog.
Ensure you have the shortcode [bex_folder] in the public page.

Let me know how that goes. I’ll help you to get it going.

Chris

Thanks for your feedback. I’ve just installed the Lightbox plugin and was able to recreate the error, so that’s the first step. I’ll see if I can work up a solution. The main problem is the image links provided by the plugin are not the final Dropbox link, which is why the Lightbox plugin fails to display an image. I’m always up for a challenge though ??

Chris

Thanks for the feedback and feature request.

There’s no current way to achieve this directly with the plugin, but this functionality is something I’ve thought about as adding as a feature. I’ve also thrown around the idea of integrating it with a separate plugin that handles the roles and permissions.

Knowing your request will help me prioritise adding this feature though and I’ll update this thread once it’s there. Thanks!

Chris

v1.5.2 addresses this problem. Thanks for raising it.

Chris

Again, thanks for your input. Had popup blockers not caused problems in the first place, this is probably how it would have worked for you. Point taken though, and since everybody likes to customize options, I’ll add an option to either pop a new window or load in same page. How does that sound?

Chris

Thanks for the feedback. I’ve incorporated a fix and just uploaded v1.5.1. I think this may be an area that I’ll look at again in the next major update.

Thanks for the feedback. I’m looking to see how I can best address this in a future release.

I’ve not been able to recreate this error, so I’m closing out this thread.

Thanks.

I’m sorry you’ve ran into problems. Thanks for letting me know though; I’ll try to help.

I’ve not tried it with a localhost setup, so can’t talk to that specifically.

Could you please confirm the following for me and I’ll see what I can do:

1. What version of WordPress are you using and is it a multisite setup?
2. Have you made any changes to the database tables directly, or changed the table prefixes?

Thanks,
Chris

I believe I’ve fixed this now with version 1.3.2.

Closing this thread for now, but if you still think I’ve not answered your question, please open another thread and I’ll take a look at it again.

Thanks,
Chris