• I’ve recently installed this plugin in a fairly new WordPress 4.0 installation, and it doesn’t seem to function as suggested.

    I have enabled the “Login form protected by Login LockDown.” message, so am sure the plugin is active. All of the other options have been left at the default value, except for the option to track invalid users.

    I’ve checked the database, and can’t see any new tables, which some others have mentioned are created by the plugin. Perhaps that is a clue to the problem?

    https://www.ads-software.com/plugins/login-lockdown/

Viewing 15 replies - 1 through 15 (of 19 total)
  • I’ve checked the database, and can’t see any new tables

    That would be an issue. It creates 2 new tables on activation. Is this a multi-site installation of WordPress? And were there any errors on activation? Can you double check that there are not 2 tables with the format of $wpdb->prefix . “login_fails” and $wpdb->prefix . “lockdowns”? If there definitely are not, can you try deleting the plugin and starting over, see if any errors occur? Lastly, where are you hosting? Is there a way to see if the database user has create table permissions?

    -Michael

    I’m having this same issue, and the tables are definitely not being created. Tried deleting and reinstalling, no luck. My host has some weird permissions settings, as I have to install plugins and updates manually. Can I create the necessary database tables manually – and will this fix the problem?

    You can try, although that should never be necessary. These are the mysql commands to create the tables, assuming that your db prefix is wp_:

    CREATE TABLE wp_login_fails (
    	'login_attempt_ID' bigint(20) NOT NULL AUTO_INCREMENT,
    	'user_id' bigint(20) NOT NULL,
    	'login_attempt_date' datetime NOT NULL default '0000-00-00 00:00:00',
    	'login_attempt_IP' varchar(100) NOT NULL default '',
    	PRIMARY KEY  ('login_attempt_ID')
    );
    
    CREATE TABLE wp_lockdowns (
    	'lockdown_ID' bigint(20) NOT NULL AUTO_INCREMENT,
    	'user_id' bigint(20) NOT NULL,
    	'lockdown_date' datetime NOT NULL default '0000-00-00 00:00:00',
    	'release_date' datetime NOT NULL default '0000-00-00 00:00:00',
    	'lockdown_IP' varchar(100) NOT NULL default '',
    	PRIMARY KEY  ('lockdown_ID')
    );

    Where is it you are hosting? And did you have to set the database user permissions manually? This obviously would only work if the db user has create table permissions. I should do a check for that on install and give a message if it fails.

    -Michael

    doume

    (@doume)

    Hello,

    Same problem here, table creation OK on production, NOK on dev server.

    Production 1 (OK): MySQL 5.0.67 + PHP 5.4.26
    Production 2 (OK): MySQL 5.1.73 + PHP 5.4.34
    Dev server 1 (NOK): MySQL 5.5.36 + PHP 5.4.31 (xampp)
    Dev server 2 (NOK): MySQL 5.6.21 + PHP 5.5.19 (xampp)
    WP 4.0.1 with Login Lockdown 1.6.1 on all servers

    On dev servers all privileges configured.
    On both production and dev servers I already use other plugins which create tables.

    D.

    mvandemar

    (@mvandemar)

    @doume – are there any errors when you activate the plugin? Do you have debugging enabled?

    -Michael

    doume

    (@doume)

    Sorry I forgot it.

    [Table ‘xxxxxx.yyyyy_lockdowns’ doesn’t exist]
    SELECT lockdown_ID, floor((UNIX_TIMESTAMP(release_date)-UNIX_TIMESTAMP(now()))/60) AS minutes_left, lockdown_IP FROM yyyyy_lockdowns WHERE release_date > now()

    mvandemar

    (@mvandemar)

    @dourne – I meant, are there any errors when you activate the plugin?

    -Michael

    doume

    (@doume)

    No. The creation table error 1st appears when opening the plugin configuration page.

    I just redo the test on my Dev Server 2 starting with a brand new WP 4.0.1 + twenty twelve theme + WP_DEBUG=true:
    1/ Creation table error confirmed.
    2/ No problem with WP Maintenance Mode plugin which successfully creates its own table.

    D.

    mvandemar

    (@mvandemar)

    @doume – I mean, is there a visible error related to the failure of the tables being created? Anything either on screen or in the error logs when you first activate the plugin that would give some insight as to why it failed?

    -Michael

    mvandemar

    (@mvandemar)

    @doume – I do not see any substansive differences between my create table statement and the on in WP Maintenance Mode, although they do include both a dfeault charset and set auto-increment to 1. If you run the raw mysql command in a query browser on the server is the table created then?

    -Michael

    doume

    (@doume)

    Nothing related to creation failure. If there are ways to make Xampp show more errors I don’t know them.

    This raw SQL request works (had to remove quotes):

    CREATE TABLE yyyyy_lockdowns (
    	lockdown_ID bigint(20) NOT NULL AUTO_INCREMENT,
    	user_id bigint(20) NOT NULL,
    	lockdown_date datetime NOT NULL default '0000-00-00 00:00:00',
    	release_date datetime NOT NULL default '0000-00-00 00:00:00',
    	lockdown_IP varchar(100) NOT NULL default '',
    	PRIMARY KEY  (lockdown_ID)
    );

    Perhaps installing Xampp 5.5.19 (multi platform) Dev Server yourself would help? I use a raw installation.

    mvandemar

    (@mvandemar)

    @doume – could you try replacing the loginLockdown_install() function that starts at line 91 with this one, see if that make any difference? Using pastebin since the forums won’t allow the code to format correctly:

    https://pastebin.com/2eRnAqRN

    -Michael

    doume

    (@doume)

    No difference, sorry.

    Same experience as couple of others. Tables not created, no error messages on install. Added the tables via SQL (without the single quotes) and now works fine.

    Also, Add the Credit Link without “link juice” doesn’t remove the juice. Do not display does work.

    Version v1.6.1
    WordPress 4.0.1

    @riricher – what system are you running on?

    -Michael

Viewing 15 replies - 1 through 15 (of 19 total)
  • The topic ‘Simply doesn't seem to lock out after specified number of attempts’ is closed to new replies.