cnelsonjeffers

[UPDATE] Divi developer Elegant Themes was able to troubleshoot and provide a solution:

Add CSS:

.et-l–header {
position: relative;
z-index: 1000;
}

This appears to have resolved the issue in my case.

An update on this issue, which has been resolved. Glen was able to identify the issue and provided an update that fixed it. The plugin works great! Perfect for my needs.

IMO the Pro version is worth paying for, as the added ability to specify saving files in custom folders makes organization and retrieval of uploaded files much, much easier!

In my case I am getting uploads from registered and logged-in users, so a folder with the username is perfect. Otherwise a time-stamped folder or static custom folder are great options, as is the random-character folder option.

Will do. Thanks.

The Membee developers do need to update their documentation, as they are still recommending WordPress Access Control which hasn’t been updated in 3 years, making it a tad confusing where their setup instructions refer to WPAC settings.

Glad to know though that AAM works with Membee and Membee Login. I had downloaded it before reading your post as it appeared to have similar functionality, but haven’t gotten too far with it yet.

I had the same problem with a mySQL database. Not sure if this is the root problem but I found in the mvc/v.php file which creates the admin form, the form (about line 21) wants to post to a URL using the https:// protocol.

Since my site runs on https and in fact forces all internal links to re-write to https, I guessed that redirects or some other incompatibility in posting using http might be the problem.

OR – the settings were saved, but couldn’t be re-read, making them appear to disappear.

I simply changed the hard-coded http to be https and voila! The settings remained displayed as saved.

If it’s as simple as that hopefully it can be resolved and the plugin updated with the fix, since otherwise the next time it updates I’m probably going to be scratching my head trying to remember what I did to fix it this time.

On the live site with ALL plugins disabled except LWA and 2BC Form Security, the LWA sidebar widget showed that pesky additional but empty input box and NO reCaptcha, so I guess it’s a theme issue.

The theme is WooTheme’s Storefront. I will attempt to connect with the author of the 2BCFS plugin to see if it’s something he can address.

Okay – tried it on a totally clean installation of WP with the default Twenty Sixteen them, with JUST LWA and 2BC Form Security plugins running, and the combination seems to be working fine there. SOOO … I will do some more troubleshooting to see which plugins are causing the issue or if it is the theme, and report back.