Patrick Johanneson

If you’ve got access to the database, you could do this:

SELECT * FROM wp_login_fails; for a full list of failed login attempts

SELECT * FROM wp_lockdowns; for a full history of locked IPs.

It wouldn’t be difficult to write a plugin to deliver this information, but I haven’t seen anywhere that the Login Lockdown plugin will allow you to display it.

If you’re using WP v. 3.7 or higher, you can use wp_get_sites(), which obviates the need to use $wpdb.

Edited to add: Sorry, I mis-read the question. I missed the part where you need this to work on a multi-network installation. Still, wp_get_sites() might be of some help.

I’m glad you’re getting use out of my post. I keep thinking I should get back to work on it — I think there’s probably a bunch of new stuff in the plugin that should be highlighted.

It worked fine with 3.7.1 and it’s working fine with 3.8.1 Multisite for me.

I’ve got it working against AD using WordPress 3.7. Are you trying to authenticate an administrative account? v.1.5.4 appears to automatically bypass LDAP for administrators and sign in instead using WordPress credentials. Try authenticating an Editor (or Author, Subscriber…) against LDAP and see if that’s the issue.

Yep, I noticed that too. It’s an easy fix, fortunately.

Resolved in 1.5.3.

I think the join() error might crop up if there’s only one LDAP server; join() expects an array but I don’t know if it’s getting a string instead if there’s only one LDAP server in the list.

What about something like:

add_action( 'wp_enqueue_scripts', 'xyz_remove_admin_bar_css', 21 );
add_action( 'admin_enqueue_scripts', 'xyz_remove_admin_bar_css', 21 );
function xyz_remove_admin_bar_css() {
    wp_dequeue_style( 'admin-bar' );
    wp_dequeue_style( 'admin-bar-min' );
}

Codex: wp_dequeue_style()

I hadn’t thought of that. Thanks!

I’m one of those people that thinks that if you need to use !important in a stylesheet, you’ve done something wrong. That’s where I like override stylesheets — especially considering you can tell WordPress what order they need to be loaded in.

I don’t know how expensive file_exists() is — according to a quick Google search, not very.

But in all honesty, you’re probably right — for a simple plugin, override stylesheets are probably overkill.

You’re welcome. (It’s not my vid, though — I’m just a user, same as you. ?? )

Well, if nothing else, it should show up in your Google Analytics dashboard. Not in your WordPress installation, but here: https://www.google.com/analytics/

I get the same issue whether it’s Network Activated or set up in the Must-Use Plugins folder. I’d like to know if there’s a way I can add it to all sites simultaneously.

OK, I got it working (at least as far as my userbase goes):

I added this to the .htaccess file:

# BEGIN file lockdowns
RewriteCond %{HTTP_COOKIE} !^.*wordpress_logged_in.*$ [NC]
RewriteRule ^sitename/files/.*\.(pdf|docx?)$ /sitename/not-allowed [R=302,L]
# END file lockdowns

(as seen in the top-frog.com posting from vjpo above)

— and then made a page at /sitename/not-allowed that asks the user to please log in.

This won’t block people from going after the /wp-content/blogs.dir/[blog_id]/[filename].pdf file, but it’s sufficient to keep accidental viewing of private files locked down.