• I’ve been having problems with a client site running WPeC.

    I’ve noticed that every visitor is tracked in the database in the wp_wpsc_visitors and wp_wpsc_visitor_meta tables.

    This site is pretty busy so one of my guesses was that this table had grown HUGE and doing a fetch and insert on every page load (is that what happens?) could be putting the server on quite a big load. I don’t know if there are possibly optimisation routines that run on these tables too?

    Anyway, I just want to eliminate it as a potential source of server load so is there any way that I can turn off this visitor tracking?

    Thanks

    https://wordpress.org/plugins/wp-e-commerce/

Viewing 5 replies - 1 through 5 (of 5 total)
  • Hi There, I too am having this issue and our database size has grown to over 8GB (HUGE). Any thoughts on how to trim this down to a reasonable size?

    Currently we have the following database table size issues.
    wp_wpsc_visitors = 3.3GB
    wp_wpsc_visitor_meta = 5.4GB

    Any thoughts on how to reduce or what to do with these?

    Also, I’m curious why are there so many visitors? I’m seeing 1-2 entries per second of every day. Our traffic numbers are nowhere near this.

    Plugin Author Justin Sainton

    (@justinsainton)

    Hi HewittDesign,

    What version of WP eCommerce are you running?

    Hey Justin, thanks for asking. We’re running the latest (just upgraded today). Previously we were on whatever version was current from March 2015. We are also on the latest WP version.

    The way the profile system is designed to work is that a customer cookie is created on the first visit to the web server. This is can be a page generation or an AJAX request. The AJAX request can be something like an add to cart, or a get cart widget contents OR can be a lightweight request done at the start of the wp ecommerce js when it detects that a customer cookie isn’t present.

    The database should only be updated when the cookie is created, that should be once per session. The database is updated when products are added to a cart, or during the checkout process.

    If creating the cookie fails in the javascript the javascript will set a ‘wpsc_attempted_validate’ cookie to stop repeated attempts during the same session.

    If your database is filling with seemingly endless profiles you have two issues:

    1) Something is stopping the customer cookie from being created AND recognized by subsequent session page views. Start to diagnose this by checking your caching and WordPress COOKIE_DOMAIN configuration to be sure all is as it should be.

    2) The WordPress cron job that cleans up abandoned profiles is not running periodically as it should. Check your WordPress cron configuration.

    – jeff

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

The topic ‘Can I disable visitor tracking’ is closed to new replies.