WordPress.org

1. danka
   Member
   Posted 2 years ago #

   Hi,

   I just updated to the plugin version 1.7.2, and it dont even activate here.

   Thanks for the support.

   http://wordpress.org/extend/plugins/simple-tags/

2. Pfff
   Member
   Posted 2 years ago #

   The same, i've just update.
   WP 2.9.1 is saying "plugin activated" but it is really not activated !!

3. trib
   Member
   Posted 2 years ago #

   I have the same issue - plugin page says it activates, but it doesn't.

   I did it first as an upgrade and then purged my options table and reinstalled. No joy either way.

4. adkbasecamp
   Member
   Posted 2 years ago #

   Yeah, me too.

   Rolled back and got the "fatal error" thing.

5. 1dfh
   Member
   Posted 2 years ago #

   Das Plugin kann nicht aktiviert werden, da es einen fatalen Fehler erzeugt

6. kndy71
   Member
   Posted 2 years ago #

   Same issue as everyone else. Hopefully a fix will be coming soon!

7. dhoffmann
   Member
   Posted 2 years ago #

   yepp, can't activate it too.

8. gurumosh
   Member
   Posted 2 years ago #

   same case here :(

9. NickyYe
   Member
   Posted 2 years ago #

   Same issue

10. fr@nkdrews.de
    Member
    Posted 2 years ago #

    I just installed simple tags, but I can't activate it, cause to fatal error message

11. fr@nkdrews.de
    Member
    Posted 2 years ago #

    for me it's 1.7.4.2 and 2.9.2 : fatal error message
    But nervertheless, it is now listed as activated and it seems to be working fine, at least the tag-cloud widget is ...

12. Amaury Balmer
    Member
    Posted 2 years ago #

    I fix the error during the activation with WP and PHP4 on version 1.7.4.3

13. Michael Torbert
    WordPress Virtuoso
    Posted 2 years ago #

    1.7.4.3 and 2.9.2 is still giving the same error for me. Best I can tell, the plugin is still activating anyway.

14. kndy71
    Member
    Posted 2 years ago #

    Updated to the new 1.7.4.3. and still get the same fatal error. Tags are working. Activation is working. But only when you click publish, afterwards you get the fatal error. The post goes through, it's just the fatal error message comes up right after you hit publish instead of going back to the usual confirmed posting.

15. Amaury Balmer
    Member
    Posted 2 years ago #

    The same error ? Can your detail the error message ?

    I try this version with PHP Version 4.4.9
    With Simple Tags 1.7.4.2, i have a fatal error.
    With Simple Tags 1.7.4.3, all it's ok...

16. kndy71
    Member
    Posted 2 years ago #

    Upgraded to 1.7.4.4. So far, so good.

17. kndy71
    Member
    Posted 2 years ago #

    Ok, have done additional tests and 1.7.4.4 worked well. The fatal error tends to happen when I have the following plugin activated: WP-DBManager

    When I have DB Manager on, I get the fatal error. Deactivate it...and I don't.

18. Truth
    Member
    Posted 2 years ago #

    Am I the only one who has the JS problem? :(

    My admin page for Simple Tags are not displayed correctly.

19. kndy71
    Member
    Posted 2 years ago #

    Ok, so maybe it's not WP-DB Manager. So, far everything works with WP-DBManager. Out of the 20 posts I made yesterday and today, about two times did I receive a fatal error message.

20. kndy71
    Member
    Posted 2 years ago #

    Well, had to deactivate Simple Tags 1.7.4.4 once again for the bigger site... fatal error problems. I'm testing it on three wordpress sites right now. The smaller blogs are working fine it seems but the bigger site, I thought it was working at first but now the fatal error problem is back.

    The problem happens after publishing a post.

    For me the Fatal Error is always found in wp-includes/wp-db.php line 480 (which I have in bold)

    function _real_escape($string) {
    if ( $this->dbh && $this->real_escape )
    return mysql_real_escape_string( $string, $this->dbh );
    else
    return addslashes( $string );
    }

    If I deactivate simple tags, everything works fine. When I activate it...I get the fatal error.

21. kndy71
    Member
    Posted 2 years ago #

    What I ended up doing is deactivating under administration:

    Activate autocompletion feature with old input

    And now, no longer receiving any fatal errors for almost a week.

Topic Closed

This topic has been closed to new replies.