Real trouble removing OSCid

[chrisholgate]

Hi there,

This is my first post to the board and I'm really hoping that someone can offer some help. It has recently become obvious that the OSCid string at the end of all our web addesses at www.refreshcartridges.co.uk has been causing a problem with our search engine positioning however all attempts to remove it have failed.

 

We were under the impression that withen a couple of clicks OSC would determine whether or not cookies were enabled and then remove the OSCid string automatically however this not only doesn't happen at all but even when we force the use of cookies the site comes up with an error message saying that the browser doesn't have cookies enabled.

 

We have tried using several different browsers (all with cookies enabled) on several different machines and several different Internet connections but each time we force the use of cookies we are unable to place an order due to our store compaining about a lack of cookie support. When the use of cookies is left optional OS Commerce insists on using the OSCid string rather than automatically detecting the fact our browser supports cookies and changing as appropriate.

 

Other OS Commerce stores on the same server work without any problems

 

Any further information I would be happy to provide as it would be really nice to get to the bottom of this.

 

Many thanks

[chrisholgate]

Just so you know, our webguy is currently working on this so you may find the OSCid isn't there when you visit.... If this is the case just try adding something to the cart to be greeted with our lovely cookie_usage.php screen....

[chrisholgate]

He's given up for the evening so the problem on the site is now once again quite evident to see. Any help would be very much appreciated and I'm happy to post across any information whatsoever.

 

Thanks again

[satish]

well for spiders there is kill session id which will take care.

 

Tis works with spiders.txt file and any spider with a name in that file is trated as a search engine and oscid is not concatenated.

 

Regards,

satish

[chrisholgate]

well for spiders there is kill session id which will take care.

 

Tis works with spiders.txt file and any spider with a name in that file is trated as a search engine and oscid is not concatenated.

 

Regards,

satish

 

Thanks for that Satish, I am still rather curious though as to why cookies don't seem to be working on my site at all. Even from an non SEO point of view I would still be genuinely interested as to why every URL of mine has OSCid at the end of it when apparently for those with cookies enabled it isn't an issue!

[Guest]

Thanks for that Satish, I am still rather curious though as to why cookies don't seem to be working on my site at all. Even from an non SEO point of view I would still be genuinely interested as to why every URL of mine has OSCid at the end of it when apparently for those with cookies enabled it isn't an issue!

 

If your configure.php file is not setup correctly for the cookies paths/domains then you will get the session with the url. It's the first place to check. And make sure your osc admin configuration->sessions has the prevent spiders sessions set to true.

[satish]

If you want it by cookies anyhow then set force cookies as true thru Admin

 

Satish

[chrisholgate]

If your configure.php file is not setup correctly for the cookies paths/domains then you will get the session with the url. It's the first place to check. And make sure your osc admin configuration->sessions has the prevent spiders sessions set to true.

 

Thanks for your help; my configure.php file looks like the following:

 

define('HTTP_SERVER', 'http://www.refreshcartridges.co.uk/'); // eg, http://localhost - should not be empty for productive servers

define('HTTPS_SERVER', 'https://refreshcartridges.co.uk/'); // eg, https://localhost - should not be empty for productive servers

define('ENABLE_SSL', true); // secure webserver for checkout procedure?

define('HTTP_COOKIE_DOMAIN', 'refreshcartridges.co.uk');

define('HTTPS_COOKIE_DOMAIN', 'refreshcartridges.co.uk');

define('HTTP_COOKIE_PATH', '');

define('HTTPS_COOKIE_PATH', '');

 

This all looks pretty fine to us though; any ideas at all?

 

Thanks again

[Guest]

try changing:

 

define('HTTP_SERVER', 'http://www.refreshcartridges.co.uk/'); // eg, http://localhost - should not be empty for productive servers
define('HTTPS_SERVER', 'https://refreshcartridges.co.uk/'); // eg, https://localhost - should not be empty for productive servers
define('ENABLE_SSL', true); // secure webserver for checkout procedure?
define('HTTP_COOKIE_DOMAIN', 'refreshcartridges.co.uk');
define('HTTPS_COOKIE_DOMAIN', 'refreshcartridges.co.uk');
define('HTTP_COOKIE_PATH', '');
define('HTTPS_COOKIE_PATH', '');

 

to

 

define('HTTP_SERVER', 'http://www.refreshcartridges.co.uk'); // eg, http://localhost - should not be empty for productive servers
define('HTTPS_SERVER', 'https://refreshcartridges.co.uk'); // eg, https://localhost - should not be empty for productive servers
define('ENABLE_SSL', true); // secure webserver for checkout procedure?
define('HTTP_COOKIE_DOMAIN', 'refreshcartridges.co.uk');
define('HTTPS_COOKIE_DOMAIN', 'refreshcartridges.co.uk');
define('HTTP_COOKIE_PATH', '/');
define('HTTPS_COOKIE_PATH', '/');

 

so those slashes do not go with the server/domains but with the paths.

[chrisholgate]

try changing:

 

define('HTTP_SERVER', 'http://www.refreshcartridges.co.uk/'); // eg, http://localhost - should not be empty for productive servers
define('HTTPS_SERVER', 'https://refreshcartridges.co.uk/'); // eg, https://localhost - should not be empty for productive servers
define('ENABLE_SSL', true); // secure webserver for checkout procedure?
define('HTTP_COOKIE_DOMAIN', 'refreshcartridges.co.uk');
define('HTTPS_COOKIE_DOMAIN', 'refreshcartridges.co.uk');
define('HTTP_COOKIE_PATH', '');
define('HTTPS_COOKIE_PATH', '');

 

to

 

define('HTTP_SERVER', 'http://www.refreshcartridges.co.uk'); // eg, http://localhost - should not be empty for productive servers
define('HTTPS_SERVER', 'https://refreshcartridges.co.uk'); // eg, https://localhost - should not be empty for productive servers
define('ENABLE_SSL', true); // secure webserver for checkout procedure?
define('HTTP_COOKIE_DOMAIN', 'refreshcartridges.co.uk');
define('HTTPS_COOKIE_DOMAIN', 'refreshcartridges.co.uk');
define('HTTP_COOKIE_PATH', '/');
define('HTTPS_COOKIE_PATH', '/');

 

so those slashes do not go with the server/domains but with the paths.

 

Unfortunately this has made no difference; we've got two guys working on the problem now with no avail and I'm starting to pull my hair out! If anyone has any suggestions whatsoever you'd put us all out our misery.

 

If there are any other sections of code you need please don't hesitate to contact me.

[Guest]

ok you need to locate the correct cookies domain. It might need a www. infront but I am not sure so first try this.

 

define('HTTP_SERVER', 'http://www.refreshcartridges.co.uk'); // eg, http://localhost - should not be empty for productive servers
define('HTTPS_SERVER', 'https://refreshcartridges.co.uk'); // eg, https://localhost - should not be empty for productive servers
define('ENABLE_SSL', true); // secure webserver for checkout procedure?
define('HTTP_COOKIE_DOMAIN', '.refreshcartridges.co.uk');
define('HTTPS_COOKIE_DOMAIN', '.refreshcartridges.co.uk');
define('HTTP_COOKIE_PATH', '/');
define('HTTPS_COOKIE_PATH', '/');

this will cover the whole domain.