InveoStore.com

[Wandererx]

We recently changed hosts, and I made sure the new host had everything needed to support magic SEO URL. Once the move was complete there were issues with the links so I cleared the cache, set the .htaccess file to 666 and opened the home page. That cleared up the dead links, but the zenid now shows at the end of the link, like: http://driller.com/v2/blasting-supplies ... 7b581d14eb

I've tried taking out magic SEO URL completely and installing it again step by step. From the hosts point of few everything is running okay. Any idea what the zenid is now showing up when it was hidden before? This isn't how magic SEO URL behaved before.

Thanks for your help.

[~J~]

I expect you know how MSU handles Session IDs (see http://www.magic-seo-url.com/zencart/features.html). In short: it is normal for first page visit if you use standard browser (not crawler).

If zendid still persists on the second and other visited page, please make sure your cookies settings are correct in includes/configure.php file.

[Wandererx]

It is showing up on all of the pages in the two I have looked in, IE and Firefox. The configure.php file contains no references to cookies, on session data, it is set to store in the DB which is correct.

[~J~]

includes/configure.php file holds settings which directly affect cookie handling. Make sure your file contains following constants defined exactly by same way as follow:

Code: Select all

define('HTTP_SERVER', 'http://driller.com');
define('HTTPS_SERVER', 'https://driller.com');

define('DIR_WS_CATALOG', '/v2/');
define('DIR_WS_HTTPS_CATALOG', '/v2/');

[Wandererx]

Yes those match, you can see the rest of the config file below minus sensitive parts:

Code: Select all

<?php


/*************** NOTE: This file is similar, but DIFFERENT from the "admin" version of configure.php. ***********/
/***************       The 2 files should be kept separate and not used to overwrite each other.      ***********/

// Define the webserver and path parameters
  // HTTP_SERVER is your Main webserver: eg, http://www.yourdomain.com
  // HTTPS_SERVER is your Secure webserver: eg, https://www.yourdomain.com
  define('HTTP_SERVER', 'http://driller.com');
  define('HTTPS_SERVER', 'https://driller.com');

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

// NOTE: be sure to leave the trailing '/' at the end of these lines if you make changes!
// * DIR_WS_* = Webserver directories (virtual/URL)
  // these paths are relative to top of your webspace ... (ie: under the public_html or httpdocs folder)
  define('DIR_WS_CATALOG', '/v2/');
  define('DIR_WS_HTTPS_CATALOG', '/v2/');

  define('DIR_WS_IMAGES', 'images/');
  define('DIR_WS_INCLUDES', 'includes/');
  define('DIR_WS_FUNCTIONS', DIR_WS_INCLUDES . 'functions/');
  define('DIR_WS_CLASSES', DIR_WS_INCLUDES . 'classes/');
  define('DIR_WS_MODULES', DIR_WS_INCLUDES . 'modules/');
  define('DIR_WS_LANGUAGES', DIR_WS_INCLUDES . 'languages/');
  define('DIR_WS_DOWNLOAD_PUBLIC', DIR_WS_CATALOG . 'pub/');
  define('DIR_WS_TEMPLATES', DIR_WS_INCLUDES . 'templates/');

  define('DIR_WS_PHPBB', '/');

// * DIR_FS_* = Filesystem directories (local/physical)
  //the following path is a COMPLETE path to your Zen Cart files. eg: /var/www/vhost/accountname/public_html/store/
  define('DIR_FS_CATALOG', '/home/userg/public_html/v2/');

  define('DIR_FS_DOWNLOAD', DIR_FS_CATALOG . 'download/');
  define('DIR_FS_DOWNLOAD_PUBLIC', DIR_FS_CATALOG . 'pub/');
  define('DIR_WS_UPLOADS', DIR_WS_IMAGES . 'uploads/');
  define('DIR_FS_UPLOADS', DIR_FS_CATALOG . DIR_WS_UPLOADS);
  define('DIR_FS_EMAIL_TEMPLATES', DIR_FS_CATALOG . 'email/');

// define our database connection
  define('DB_TYPE', 'mysql');
  define('DB_PREFIX', 'zen_');
  define('DB_SERVER', 'localhost');
  define('DB_SERVER_USERNAME', 'dataname');
  define('DB_SERVER_PASSWORD', 'XXXXXXXXXXXXXXX');
  define('DB_DATABASE', 'databname');
  define('USE_PCONNECT', 'false'); // use persistent connections?
  define('STORE_SESSIONS', 'db'); // use 'db' for best support, or '' for file-based storage

  // The next 2 "defines" are for SQL cache support.
  // For SQL_CACHE_METHOD, you can select from:  none, database, or file
  // If you choose "file", then you need to set the DIR_FS_SQL_CACHE to a directory where your apache
  // or webserver user has write privileges (chmod 666 or 777). We recommend using the "cache" folder inside the Zen Cart folder
  // ie: /path/to/your/webspace/public_html/zen/cache   -- leave no trailing slash 
  define('SQL_CACHE_METHOD', 'database');
  define('DIR_FS_SQL_CACHE', '/home/userg/public_html/v2/cache');

// EOF


[~J~]

Make sure in ZC admin panel - Configuration - Session - Cookie Domain is set to false. If this does not help, please contact ZC support for further help.

[Wandererx]

Cookie Domain is set to false. Turned on debug for ZC, seeing this:

Code: Select all

Notice: Undefined index: unInstalledLang in /home/driller/public_html/v2/includes/magic_seo_url.php on line 0

Notice: Undefined index: unFancyLang in /home/driller/public_html/v2/includes/magic_seo_url.php on line 0

Does that help?

[~J~]

No.

I will try to explain it in more detail. If zenid is showing, it is not an MSU issue - what MSU only does is transforming current URI to new SEO format. If old URI contains zenid, new one will also include it (with exceptions described at Feature page to provide best possible results for SEO).

What I am trying to tell you is that ZC support will probably help you better with this issue. You can also turn on "Force cookie use" which stops zenid using at all.

[BlessIsaacola]

Make sure in ZC admin panel - Configuration - Session - Cookie Domain is set to false. If this does not help, please contact ZC support for further help.

J~,

Can you please explain the difference between having Cookie Domain set to False instead of True? I am asking because we've had ours set to True since we've been using Zen Cart and our MSU work just fine without the problem described by previous poster.

Thanks!

[~J~]

In ZenCart it affects how cookie domain is set.

The domain that the cookie is available. To make the cookie available on all subdomains of example.com then you'd set it to '.example.com'. The . is not required but makes it compatible with more browsers. Setting it to http://www.example.com will make the cookie only available in the www subdomain. Refer to tail matching in the » spec for details.

http://www.php.net/set_cookie