Home > General > Call for Issues

Call for Issues

I plan to put some time into working on some of the outstanding issues over the next week or two. However, I have received issues via just about every method of communication out there.  To make sure nothing is getting missed, if you are aware of an active issue that is NOT posted here – please either post it on the SourceForge tracker or reply back with a comment.

Categories: General Tags:
  1. Sam Margulies
    September 7th, 2011 at 16:25 | #1

    When you go to the Users page, the “Add New” button that displays next to the heading links to the default WordPress Add Users page.
    If you are interested, I have a patch to redirect the user-new.php WordPress page to your plugin’s version to avoid accidentally adding users locally.

  2. James Revillini
    November 29th, 2011 at 09:23 | #2

    I have a problem in that my AD does not contain e-mail addresses for all accounts, such as test accounts, as well as users in a certain OU. I wrote a dirty fix which jams a fake e-mail into the account and immediately prompts the user to go update their e-mail. It has “allow users to fix their e-mail when it’s blank” as an admin option. How can I get this to you?

  3. Jussi Sivonen
    January 9th, 2012 at 01:49 | #3

    When enabling WordPress’ debug mode, I get 2 different errors from the WMPU-LDAP plugin:

    Notice: WP_User->id was called with an argument that is deprecated since version 2.1! Use WP_User->ID instead. in /home/testiwp/www/wp-includes/functions.php on line 3551

    Notice: has_cap was called with an argument that is deprecated since version 2.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in /home/testiwp/www/wp-includes/functions.php on line 3551

    While the path points to the error message -generating bit of code instead of the actual error in the plugin, I’d say these sound the kinda bugs that should be fixed :)

  1. No trackbacks yet.