Error WP 4.0.1

  • Resolved beardedeggs

    (@beardedeggs)


    11 years, 5 months ago

    Fatal error: Uncaught exception ‘phpbrowscap\Exception’ with message ‘temporary file already exists’
    in SITE/wp-content/plugins/wp-statistics/includes/classes/Browscap.php:517
    Stack trace:
    #0 SITE/wp-content/plugins/wp-statistics/includes/classes/Browscap.php(289): phpbrowscap\Browscap->updateCache()
    #1 SITE/wp-content/plugins/wp-statistics/includes/classes/hits.class.php(59): phpbrowscap\Browscap->getBrowser()
    #2 SITE/wp-content/plugins/wp-statistics/includes/classes/hits.geoip.class.php(16): Hits->__construct()
    #3 SITE/wp-content/plugins/wp-statistics/wp-statistics.php(128): GeoIPHits->__construct()
    #4 [internal function]: wp_statistics_shutdown_action(”)
    #5 SITE/wp-includes/plugin.php(505): call_user in SITE/wp-content/plugins/wp-statistics/includes/classes/Browscap.php on line 517

    https://wordpress.org/plugins/wp-statistics/

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor Greg Ross

    (@gregross)

    11 years, 5 months ago

    Are you seeing this all the time or only once?

    What are the contents of your wordpress/wp-content/uploads/wp-statistics directory?

    Thread Starter beardedeggs

    (@beardedeggs)

    11 years, 5 months ago

    Seeing all time.

    Contents of your wordpress/wp-content/uploads/wp-statistics directory:
    browscap.ini
    browscap.old
    cache.lock
    cache.old
    GeoLite2-Country.mmdb

    Plugin Contributor Greg Ross

    (@gregross)

    11 years, 5 months ago

    Does your web server have full access to the directory?

    Try deleting the following files:

    browscap.old
    cache.lock
    cache.old

    Thread Starter beardedeggs

    (@beardedeggs)

    11 years, 5 months ago

    After deleting files browscap.old, cache.lock, cache.old all works fine without errors.
    Thank you.
    What was the cause of the error?

    Plugin Contributor Greg Ross

    (@gregross)

    11 years, 5 months ago

    It looks like cache.lock (which is created by the 3rd party browscap libaray during a browscap.ini update) failed to delete properly. Could be caused by the script being terminated by the web server at just the wrong moment.

    I’ve seen it in my development environment before when I manually kill the process while debugging.

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

The topic ‘Error WP 4.0.1’ is closed to new replies.