WordPress Directory Authentication Conflict

  • Resolved edunger

    (@edunger)


    11 years, 3 months ago

    After updating to 2.0.7, our wpDirAuth plugin fails. It is automatically put into safe mode. After disabling the NextGen gallery, the plugin will function normally. We have downgraded to 1.9.3 until a new update is released.

    WordPress up to date? Yes
    – NextGEN up to date? Yes
    – What version of NextGEN Gallery did you upgrade from? (i.e. I had 1.9.3, then upgraded to 2.0.7)

    (please confirm the following, with your server host tech) :
    – MySQL up to date (at least 5.2.4) 5.5.28-cli
    – PHP up to date (at least 5.0)? 5.4.17
    – The mod_rewrite Apache module activated? On
    – PHP Safe Mode OFF? On

    Additional information that will help us find a solution:
    – Who are you hosted with? uncg.edu
    – What theme are you running? custom built theme UNCG Child Theme (see ioc.uncg.edu)
    – Which plugins do you have installed and activated?
    Allow PHP In posts and pages
    Custome sidebars
    Disable comments
    google calendar events
    gravity forms
    gravity forms PDF extended
    NextGen Gallery
    Page Navigation Widget
    Quick Cache
    Redirection
    Revisionary
    Simple Page Ordering
    Sucuri Security – SiteCheck Malware Scanner
    TimThumb Vulnerability Scanner
    Tippy
    Twitter Widget Pro
    Ultimate Maintenance Mode
    vSlider
    Wordfence Security
    WordPress SEO
    wpDirAuth
    WP PHP Widget

    – Does this error still occur if you switch your theme to the WP default, and deactivate all plugins except NextGEN Gallery? (*be sure to clear your browser cache and reload your site after deactivating) Unable to attempt.

    https://www.ads-software.com/plugins/nextgen-gallery/

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter edunger

    (@edunger)

    I tested the new update (2.0.11) and still ran into the same problems.

    This is the message I get from the wpDirAuth plugin when I updated.

    Directory Authentication Options: Plugin Conflict
    Sorry, but another plugin seems to be conflicting with wpDirAuth.

    wpDirAuth is now running in safe mode as to not impair the other plugin’s operations.’
    The wp_authenticate and wp_setcookie WordPress pluggable functions have already been redefined, and wpDirAuth cannot provide directory authentication without having access to these functions.
    Please disable any WP plugins that deal with authentication in order to use wpDirAuth. Unfortunately, we cannot provide you with more info as to which plugin is in conflict.

    I’m currently working on some things in wpDirAuth to further reduce plugin conflicts. But I’m a bit surprised that the NextGen Gallery plugin is using wp_authenticate or wp_setcookie. Maybe one of their developers can explain why they are overriding those functions. In the mean time, I’ll download their plugin and see if I can figure out what they are doing.

    It appears that they are loading wp-includes/pluggable.php upon their plugin’s initialization where NORMALLY pluggable.php is loaded after all your active plugins so those plugins can override the functions in pluggable.php.

    As I mentioned, I’m working to redo some of wpdirauth so it will play nice with other plugins that need to touch authentication (specifically Better WP Security).

    Thread Starter edunger

    (@edunger)

    Thank you for the response. I appreciate knowing that someone is actually looking at this specific concern.

    Thread Starter edunger

    (@edunger)

    Do you have any updates to changes for either the wpDirAuth app or NextGen Gallery app for this issue? I have tested all of the updates to the NextGen Gallery with the exact same results each time.

    FYI, ran into the same error with wpDirAuth and the latest release of WordPress Twitter Bootstrap CSS:

    https://www.ads-software.com/support/topic/plugin-conflict-wpdirauth-and-wordpress-twitter-bootstrap-css?replies=1#post-4649377

    Same error for me too with White Label CMS

    iltdevunit, White Label CMS is doing the same thing: at line 27 of wlcms-plugin.php they are including the pluggable.php file.

    *SIGH*

    You can safely comment out that line (or lines 26-28), as the function they need from pluggable.php (wp_get_current_user) isn’t actually called until after the wp_dashboard_setup action which, by then, wordpress will already have loaded pluggable.php properly.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘WordPress Directory Authentication Conflict’ is closed to new replies.

Tags