Jeffrey Schutzman

I just did an upgrade from 3.9 to 10.1 om a site with 19,963 no issue with WP-eCommerce. PHP memory is set around 150MB

Some other things you may want to check, admittedly low possibility of being the cause.

1) There was a recent bug in WordPress that caused tens/hundreds/thousands of CRON jobs to get queued. These could cause out of memory errors on some systems. Use a CRONTROL plugin to check to sere if this is an issue.

2) Look at the WordPress options table and see if the option that has the WP-eCommerce version is present and properly formatted. If the option is an odd value there is a very remote chance that the upgrade routine is trying to upgrade from a near paleolithic version of the plugin, if this is the case it could take a while and use much memory.

3) Double check again that drag and drop is not being used to order the products.

Also, what version did you upgrade from?

I ask because if the visitor or visitor meta tables have not been created correctly every visitor would be assigned the visitor ID 1.

Because you are running multisite, if you enabled multisite without going through the WP-eCommerce installation and setup it is possible that the visitors table and visitor meta table were not created with your second site database prefix.

jeff

Definately something wrong here. wpsc_customer_cookie_* should never start with “1” for a real user. The “1” is the visitor id reserved for a bot.

Still not seeing the user agent in the debug dumps above? you want to

error_log( var_export( $_REQUEST , true ) );

and

error_log( var_export( $_SERVER , true ) );

to get the whole picture.

What is the url of your site?

-jeff

Your close to finding the cause,

I would suggest you dump dump the $_COOKIES array so we can see if there is a cookie set that is invalid and forcing the bot selection.

the line:
error_log( var_export( $_COOKIE, true ) );

should put the information info your debug log.

I am a little suspicious that you may be hitting the invalid cookie check in at the start of _wpsc_is_bot_user()

You might also want to confirm that the wpsc_bot_user_agents and wpsc_is_bot_user filters are not being used by any themes or plugins.

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

see this https://ww.wp.xz.cn/support/topic/plugin-wptouch-wptouch-serves-bscorecardresearch