Error Message after update – conflictwith xcache 1.2.2?!

  • Hi yesterday I update to WP 3.4.1.

    During the database update, it could not go on? Well I googled and found out that it’s the object-cache.php file in the wp-content folder (is a xcache file, version 1.2.2)

    I deleted the file and it went flawlessly.

    After the update was completed and the plugins were updated I thought I upload the file again and prombt comes this error message:

    Fatal error: Call to undefined function wp_cache_add_non_persistent_groups () in / var / www / youth welfare / wp-includes / class-wp-theme.php on line 177

    This is the following snippet, the Line 177 is the strong line:

    / / Initialize caching on first run.
    if (isset (self :: $ persistently_cache)) {
    self :: $ persistently_cache apply_filters = (‘wp_cache_themes_persistently’, false, ‘WP_Theme’);
    if (self :: $ persistently_cache) {
    wp_cache_add_global_groups (‘themes’);
    if (is_int (self :: $ persistently_cache))
    self :: $ cache_expiration = self :: $ persistently_cache;
    Else {}
    wp_cache_add_non_persistent_groups (‘themes’);
    }
    }

    $ this-> theme_root theme_root = $;
    $ this-> stylesheet = $ THEME_DIR;

    Can someone help me? What should I do? I deleted the line 177 and then it went? What is “wp_cache_add_non_persistent_groups” Does I need this?

    Thanks from Germany!

Viewing 1 replies (of 1 total)
  • Moderator t-p

    (@t-p)

    have you tried:

    deactivating ALL plugins (yes, all) temporarily to narrow down the problem. If the problem goes away, re-activate them individually (one-by-one) to find the problematic plugin(s). If you can’t get into your admin dashboard, try resetting the plugins folder by FTP or phpMyAdmin. Sometimes, an apparently inactive plugin can still cause problems (because the hooks remain unless plugins completely removed or some plugins stick around in cached files. So by renaming the folder, you break them and force them inactive).

    -switching to the unedited default theme (Twenty Eleven) for a moment using the WP dashboard. If you don’t have access to your admin area, you can switch to the default theme by renaming your current theme’s folder in wp-content/themes via FTP or SFTP or whatever file management application your host provides. The idea is to force WordPress to fall back to the default theme to rule out any theme-specific issue.

Viewing 1 replies (of 1 total)
  • The topic ‘Error Message after update – conflictwith xcache 1.2.2?!’ is closed to new replies.