• Resolved blindpet

    (@blindpet)


    I am using Debian 8 x64 and the dotdeb repos with php 7 RC 6 builds and the first thing I wanted to do was test your redis plugin with the pecl extension I successfully built and installed just like I have for php5. I get a 500 internal server error when I activate the plugin and the error log shows this for nginx:

    Stack trace:
    #0 /var/www/htpcguides/wp-content/object-cache.php(613): Redis->get('wp_:default:is_...')
    #1 /var/www/htpcguides/wp-content/object-cache.php(110): WP_Object_Cache->get('is_blog_install...', '')
    #2 /var/www/htpcguides/wp-includes/functions.php(1282): wp_cache_get('is_blog_install...')
    #3 /var/www/htpcguides/wp-includes/load.php(472): is_blog_installed()
    #4 /var/www/htpcguides/wp-settings.php(109): wp_not_installed()
    #5 /var/www/htpcguides/wp-config.php(89): require_once('/var/www/htpcgu...')
    #6 /var/www/htpcguides/wp-load.php(37): require_once('/var/www/htpcgu...')
    #7 /var/www/htpcguides/wp-admin/admin.php(31): require_once('/var/www/htpcgu...')
    #8 /var/www/htpcguides/wp-admin/plugins.php(10): require_once('/var/www/htpcgu...')
    #9 {main}
      thrown in /var/www/htpcguides/wp-content/object-cache.php on line 613" while reading response header from upstream, client: 192.168.60.1, server: www.htpcguides, request: "GET /wp-admin/plugins.php?plugin_status=all&paged=1&s HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "192.168.60.134:8090"

    https://wordpress.org/plugins/redis-cache/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Till Krüss

    (@tillkruess)

    What’s the actual error exception that’s thrown? Should be found right above the stack trace.

    Thread Starter blindpet

    (@blindpet)

    My apologies Till, this was a derpy moment. I built the redis-extension but forgot to install redis-server. Unsurprisingly I am now able to enable object cache and all seems to be working.

    Plugin Author Till Krüss

    (@tillkruess)

    Okidoki : )

    Thread Starter blindpet

    (@blindpet)

    That will teach me to test new environments at 1 am 😉

    It would be nice if the plugin could detect this sort of grave oversight and disable itself but I can understand if it’s not a priority.

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

The topic ‘Compatibility with php7 errors’ is closed to new replies.