WordPress.org

Plugin Directory

Changeset 1655488


Ignore:
Timestamp:
05/11/17 21:58:02 (7 months ago)
Author:
gilzow
Message:

update changelog for 1.9.3

File:
1 edited

Legend:

Unmodified
Added
Removed
  • wpdirauth/trunk/readme.txt

    r1644142 r1655488  
    44Requires at least: 2.2 
    55Tested up to: 4.7.4 
    6 Stable tag: 1.8.1 
     6Stable tag: 1.9.3 
    77WordPress directory authentication plugin through LDAP and LDAPS (SSL). 
    88== Description == 
     
    3636 
    3737== TO-DO's == 
    38 More filters and actions to hook into. LDAP instances can vary widely so trying to 
     38+ Internationalization 
     39+ Refactor to a class 
     40+ More action/filter hooks 
    3941 
    4042== Source and Development == 
     
    6870 
    6971== Changelog == 
     72= 1.9.3 = 
     73+ Action/Filter hooks now available. Documentation: http://www.gilzow.com/_wpdirauth/hooks/ 
     74+ Cookie time-out. The authentication cookie's time-out can now be set in the settings panel. Time entered shoudl be in hours. Default is still one hour. 
     75+ Added PHP 5.2.X support (broken in previous versions), but this will likely be the last version that supports PHP versions less than 5.3 
     76+ CSS Changes in the settings area 
     77+ Fixed bug from 1.8.1 that allowed certain AD-authed users to still authenticate when directory authentication was disabled 
    7078= 1.8.1 = 
    7179+ I had forgotten that wp-login.php, for some odd reason, triggers the login/authenticate functions/filters when a user arrives to the page via GET method, even when the action parameter isn't set. This was causing wpDirAuth to generate a WP_Error object when a user initially visited the page. If you were using another plugin that records login failures (e.g. anti Brute Force) this would result in two failed attempts for every single actual failed attempt.  Or if you are monitoring for failed attempts (e.g. Sucuri, iThemes Security) then you would receive false warnings of a failed login attempt using an "Unknown" username. 
Note: See TracChangeset for help on using the changeset viewer.