Blighty

Thanks for the feedback. I’m not able to recreate the error – even on a brand new install.

Can you please use the &bex_reset=1 tip as shown above and then try to authenticate with Dropbox again?

Let me know how that goes – I’d really like to get to the bottom of this problem.

Thanks!

Hi – Thanks for the feedback. The sort method implemented was just a standard string sort which caused the ordering you saw.

I’ve added functionality (v1.9.6) to allow you to select a “natural” sort in the admin settings. This will hopefully achieve what you’re looking for.

Thanks!

Chris

Thanks for the feedback! There’s an undocumented feature that should do what you’re looking for – add the attribute root="/yoursubfolder" to the bex_folder shortcode. This allows you display different folders on different pages.

Hi Albert,

Thanks for letting me know about the problem. I’ve tried to recreate the issue on my test site, but I’m not able to. A couple of questions:

1. Are you using any attributes/parameters on the bex_folder shortcode?
2. Has this worked before but then stopped when another plugin was installed?

Thanks!

Chris

Wonderful! Thanks for letting me know ??

OK – Try this:

Go to the settings page for Blighty Explorer (you’ll get the error message you’ve mentioned before).

Go the browser address bar and add &bex_reset=1 to the end of the URL

You will end up with something like:
https://********/wp-admin/options-general.php?page=blighty-explorer-plugin&bex_reset=1

Press Enter.

That should reset the plugin allowing you to authenticate with Dropbox again.

Let me know how that goes!

Thanks for your feedback. I’ll take note of this and handle it better in a future release.

In the meantime, you can manually create a folder in your Dropbox folder

/Apps/Blighty Explorer

That should get you working again.

Hi Chris,

I greatly appreciate all your testing and feedback on the problems you’ve experienced. I’ve been trying to recreate your issue with the permissions, and can acknowledge one bug, but not the main one you’ve described.

The bug that I’ve seen is when you “reset” the permissions on a folder to All/Anonymous by just selecting the folder and leaving all roles blank, then that doesn’t seem to work. I will work on a bug fix for that. The way that does work is to select just the “All/Anonymous” role AND the folders you want to apply that to.

Thanks,
Chris

The “No Access” error is normally returned when the Allow uploads to Dropbox when the WordPress user is not logged in option is not checked and the user hasn’t logged in to WordPress to upload the file. In other words, if you’re allowing anonymous users to upload files, that option should be checked.

Can you please verify? I’m happy to look into this further if you’ve done that and you’re still seeing the error.

Thanks,
Chris

Hi Chris,

Thanks for letting me know about this.

There was indeed a bug – the options were being saved, but as you stated the checkbox wasn’t reflecting it.

I’ve corrected it and just released 1.9.3 which should hopefully resolve this.

Thanks,
Chris

Just a quick update – I’m still looking at solutions to this, but it may need a rewrite of some of the code, and that may take a while.

The problem arises because the widget code doesn’t execute on an attempt to download the file, so you just end up with the blank screen you’re describing. I’m thinking over possible ways around this or how to implement a solution within the Blighty plugin to support it, but it may be a few days though before I have a chance to look at it.

Hi – thanks for your feedback.

Well, sure enough, I was able to recreate the problem you described using the same “Pages in Widgets” plugin. I hope to report back soon on a solution.

Chris

Happy to see it worked! Thank you for letting me know.

If you ever have any ideas for the future development of this plugin, please let me know that too.

Thanks,
Chris

Hi David – It’s tough to troubleshoot this one. It could be a case of the emails going to your spam folder.

You won’t see any reference to the plugin in the page’s source view as it doesn’t use any stylesheet or other references.

I’ve just uploaded 1.2.0 which now has a “debug” option. Turning this on briefly will show comments on the page where you have the bno_notify shortcode when the page is requested. It will at least identify if the code is being triggered. Don’t forget to turn it off again when you’re done.

Hope that helps!

Chris.