Viewing 15 replies - 1 through 15 (of 34 total)
  • Yep, I’ve got the same problem too. It’s completely screwed up my site’s forum page.

    Hi guys,
    Is there any change to get the system error log. We would like to see if there is any other errors that caused the Fatal Error.

    Please also let me know what WordPress version are you using? And did you turned on in ConfigPress caching with caching = “true”.

    Our email address is support@wpaam.com

    Regards,
    Vasyl

    I’m using WordPress version 3.8.1 (I think it updates itself automatically). Unfortunately the error logs don’t seem to be recording properly as there’s nothing for my main site, only a few lines for my other domain.

    In terms of the caching, how do I turn that on? When I click the ConfigPress menu option all that appears is an empty box, no options.

    Thread Starter adfu

    (@adfu)

    Using 3.8.1 but it was broken in 3.8 too. Not entirely sure what you mean about caching=”true” but I’m using WP Super Cache … disabling WP Super Cache doesn’t solve the issue.

    Hi poorlittlefish,
    Very good. Please try Development Version. I posted the temporary fix.

    Thank you for your time and let me know if it works.
    Vasyl

    Hi guys,
    Thanks for updates. I have just pushed the Development Version with fix.

    Please let me know if it works.

    In release 2.1 we introduced caching. This speeds up the system. To turn the caching on you have to go to ConfigPress and type next code:
    [aam]
    caching = “true”

    This is very important if you have a large website with a lot of visitors.

    Please let me know if fix works for you.
    Regards,
    Vasyl

    Hello

    I deleted version 2.1, uploaded and attempted to activate the development version, but on doing so got this message, which meant I couldn’t do anything at all:

    Warning: Illegal offset type in /home/mysite/public_html/wp-content/plugins/advanced-access-manager/application/control/subject.php on line 284

    Fatal error: Call to a member function getParam() on a non-object in /home/mysite/public_html/wp-content/plugins/advanced-access-manager/application/control/subject.php on line 90

    As I was prevented from accessing the plugins page I had to delete the plugin files through FTP but am still getting the error messages, so the “fix” has, in fact, screwed me up much worse than before because now I can’t even login to the backend of my site and from the front end the same pages are affected with the errors shown above. Help!!!

    My bad. The files hadn’t been deleted from the server, so from the front end I’m now OK, but installing the development version gives the problems I mentioned in my previous post.

    Ok. Please come back to version 2.0.
    You might have some very specific settings in your system. Is there any change you give us a complete dump of your files and database so we can install it on our server and debug the case?

    Thank you.
    Vasyl

    Thread Starter adfu

    (@adfu)

    Installing the Development Version doesn’t work for me either.

    Doing what you suggested in AAM ConfigPress doesn’t solve the issue in v2.1. It doesn’t appear to do anything at all.

    Hi adfu,
    As I mentioned above. There must be some other specific settings in your system that we did not have on our development environment.
    If you can make a dump of your website and send it to us this will help us to resolve the issue.

    Regards,
    Vasyl

    Fatal error: Call to a member function cacheObject() on a non-object in /home/edutas5/public_html/wp-content/plugins/advanced-access-manager/application/control/subject.php on line 277 Is what I woke up to this morning and I didn’t even turn on caching. I am really getting mad.

    Vasyl to be honest when 1 person has an issue something might be wrong, when 2 ppl have it there probably is something wrong, but when 3 ppl are having this same issue, its not something specific with our settings, there is something wrong with our code. I don’t like getting a call at 4 AM from my security company telling me that my site is down and them reading off the error code coming from your plugin.

    Similar error here after upgrading to the latest version. My entire site is kaput after 2.1 upgrade. I have also installed it on a clean WP site and it also crashes.

    Hi brashell,
    You are putting to much effort to write comments that does not help us to resolve the issue. You have to understand that we give you the tool that was developed years for Free.
    Please consider to hire the dedicated, expensive developer who will create applications specifically for you. Otherwise, give us time and more information about your website and we will fix it asap.

    Regards,
    Vasyl

    P.S. If you will try to refer to the fact that you purchased AAM Extension, please also take in consideration that it does not cover even half an hour of our time and we put even more time to calm you down on our email conversation than on issue investigation.

Viewing 15 replies - 1 through 15 (of 34 total)
  • The topic ‘Error after upgrade to v2.1’ is closed to new replies.