Fatal Error

  • Resolved linniccox

    (@linniccox)


    11 years, 1 month ago

    I downloaded your AAM plugin and tried to activate it. Now I get the following error when trying to access anything on my site.

    Warning: require_once(__DIR__/activity.php) [function.require-once]: failed to open stream: No such file or directory in /home/namihelp/namiwichita.org/wp/wp-content/plugins/advanced-access-manager/extension/AAM_Activity_Log/extension.php on line 39

    Fatal error: require_once() [function.require]: Failed opening required ‘__DIR__/activity.php’ (include_path=’.:/usr/local/lib/php:/usr/local/php5/lib/pear’) in /home/namihelp/namiwichita.org/wp/wp-content/plugins/advanced-access-manager/extension/AAM_Activity_Log/extension.php on line 39

    I can not even able to get in to my dashboard to do anything. It has completely destroyed my site! I am brand new to wordpress and don’t have a lot of experience and have no clue what to do. The site location is https://www.namiwichita.org/wp/ Please help!

    https://www.ads-software.com/plugins/advanced-access-manager/

Viewing 5 replies - 1 through 5 (of 5 total)

  • I get the same error. It looks like the plugin was just updated today.

    While we wait for a solution, you can try removing the /wp-content/plugins/advanced-access-manager folder from your website files. Your site should return to its previous state.

    Edit line 39 of /wp-content/plugins/advanced-access-manager/extension/AAM_Activity_Log/extension.php.

    Replace
    require_once(__DIR__ . ‘/activity.php’);

    With
    require_once dirname(__FILE__) . ‘/activity.php’;

    Reason for the error:
    __DIR__ is new in PHP 5.3. For php version 5.2.17 and older, __DIR__ will not work. For older version of php, dirname(__FILE__) works perfectly.

    Hi guys,
    First of all thank you tcliff for quick help.

    The Development Version has fix. We will release 2.2.1 version tonight or tomorrow.

    Regards,
    Vasyl

    Thread Starter linniccox

    (@linniccox)

    Thank you so much for the quick replies! I’ve deleted the folder for now and will await the updated version.

    Actually release 2.2.1 fixes the issue.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Fatal Error’ is closed to new replies.