Support » Plugins » 2.3.1 and Spam Karma 2

  • Resolved hackerforhire



    Has anyone else experienced Spam Karma 2 throwing a fatal error when attempting to activate it after upgrading to 2.3.1 from 2.2?

    I’ve blown away all of the references to SK2 in the wp_options and removed the SK2 tables; however, a reinstall of the plugin gives a bit about the plugin cannot be activated due to a fatal error. Is there some else that has gotten around this or is there a way I can get some more details on what the fatal error was?

Viewing 6 replies - 1 through 6 (of 6 total)
  • due to a fatal error.

    what exactly is the error? SK2 is flawlessely working on WordPress 2.3.1

    I have no idea what the fatal error is because all it says is “Plugin could not be activated because it triggered a fatal error.” No details as what the error is. I’m not seeing anything fail in my apache logs, but I’m sure that’s not the right place to be looking.

    How can I get more details on the error?

    for apache, you should have two sets of logs. Check the error logs, there might be more there.

    Finally found it. It’s a problem with my hosting configuration. A small tweak of:

    php_flag display_errors on
    php_value error_reporting 7

    to the .htaccess file showed

    Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 737280 bytes) in /hsphere/local/home/wyatt/ on line 867

    Now the next question is does anyone know where I can stick something like:

    <?php ini_set("memory_limit","16M"); ?>

    into the plugin? Line 2 and line 866 produce the same sort of error.

    Nevermind. I didn’t read the error message right, it says allowed. A quick email to my host got the issue resolved when the bumped the memory limit to 16mb.

    Thanks again for the help.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘2.3.1 and Spam Karma 2’ is closed to new replies.