pjbarry21

I’m having the same issue — and we have WPEngine as our host. I do not have this problem on sites with older versions of Elementor (same host). I don’t see a setting in WPEngine that allows me to clear anything (beyond standard cache — and higher level caching is disabled and we don’t have a CDN).

Well, I’m glad you took on the challenge. Regardless of the coding standards, it’s still working like a champ — 5+ days in and not a single bot has been able to attempt registration since I got it installed and configured. ?? And 228 recognized spam attempts have been blocked. ??

Thanks, again!

Sorry to hear that. Good luck.

Just ran into this with 3.2.16 and I changed one setting that seems to have fixed it.

In your WP site, go to Auth0 > Settings > Basic and just below the Client Secret key field, there’s a “Client Secret Base64 Encoded” option. I turned that off and it worked. This option doesn’t exist (at least I don’t see it in the same place) in older versions of the Auth0 plugin.

When I checked in my Auth0 account, some of my clients said they were encoded, some said they weren’t. I don’t see where I can make that change. But the site having the problem was a site/client I just set up and had the new version of the plugin.

• This reply was modified 8 years, 1 month ago by pjbarry21.

Ok. I just cleared the cache everywhere, reset all file permissions (a WPEngine thing) and made a page tweak (for forums) and the config page is now showing up (and not blank) under Settings and Community Stats in the Dashboard. Not sure what flushed it out, but it seems to be functional now.

I just installed the plugin and I’m not seeing anything in the widget or an about page (per the instructions in the readme.txt) to configure it. I’m using WordPress 4.7. The Member Stats plugin is working fine — but I was looking for stats for the community as a whole.

For us, this turned out to be caused by a “feature” of WPEngine hosting where it disables WordPress Heartbeat API (though, not all the time). We were working with a dev who was able to disable plugin’s use of the Heartbeat API to function for us and was talking about writing a plugin to override WPEngine’s settings if we found this was the final solution for us.

Not sure if this helps you, but if you use WPEngine, I suspect that this could be your issue, too.

New version of jQuery – 1.12.4-pre – didn’t change anything. Tried other browsers, cleared the cache of each browser and the server.

Additional info:

Add attachments is enabled. Other metaboxes on that page do nothing, as well.

Check the page source to see if a file at buddypress-docs/includes/js/attachments.js is being loaded via a script tag.

Nope… attachments.js is not referenced anywhere in the source (but folders.js is)

– Please share the markup for your ‘Add Files’ button. It should have the class name ‘add-attachment’.

It does show up, but see no markup related to it.

We’re noticing the same thing — with WP 4.5.2, BP and BuddyBoss theme and Docs 1.9.1. Tried using the older jquery version, but no luck with that. Same issue when trying other browsers. This is a relatively clean install and this was the first attempt at using Docs (so it didn’t break as this was the initial attempt to get it working).