Originally Posted by
BlightyExPat
If I open a second or third session in the same browser, then I agree, the zenid is no longer part of the url.
When you say that the zenid is present when first arriving at the (home) page, are you saying that it should ONLY be present in the home page url? My problem is that it appears in all of the various links (eg. any of the product categories) so instead of going 'say' to page 2, which might be our 'Newsletter' page, the link address is page2 PLUS the zenid text, which clearly isn't a valid url address.
Here is a typical example: "http://www.fort777.co.za/index.php?main_page=newsletter&zenid=nn1p0ilr74tt3k9kgqgotlj2aioq5gur4m58pbg0i4kkfiin34r1"
So, not sure why it is thought that a uri that contains more than one parameter (main_page is a parameter, that is followed by zen_id. If the "starting" point were a product in a category then there would be three initially, but if one were to move to the next or previous product from there (or in this case clicked on 3.5mm to 6.35mm to end up on the result) then an additional parameter would be added (zenid). See this as an example:
Code:
http://www.fort777.co.za/index.php?main_page=product_info&cPath=1_2_3_4_1457&products_id=9801
Code:
http://www.fort777.co.za/index.php?main_page=product_info&cPath=1_2_3_4_1398&products_id=9277&zenid=sessionCode
See, here's the process: customer opens a browser, types in the uri to the desired location (somewhere on your store), server(s) direct the customer to the page. A check is performed for a session token either in the uri or "inthe page" from where it came (POST data/hidden field data), if the session value is found, then aspects of the previous session if it is still alive are brought into the browser (ie, shopping cart contents) and the session's clock is restarted allowing it to live longer. If that session data is found in the uri either with a ? Or & in front of it then it is assigned to a hidden field on the page and removed from the uri for the next link location. If the session data is found in the hidden value of the previous page then it will remain as a hidden value.
If the session value doesn't exist in either the uri ($_GET[]) or the hidden value ($_POST[]) then the process is begun with attaching it to every ZC generated URI so that the above process can be performed. URIs that are hard coded will not gain the benefit of passing the session value (zenid) and so the system will ttempt to compensate which (and I think at this point I'm getting beyond my experience of review) should result in the same session value assuming that cookies worked and other checks that the software does, otherwise a new session may be begun and any session tracked aspects become "lost".
Anyways, so the zenid will appear in the links of the first page visited (regardless if the home page or otherwise), and in the uri of the browser on the first click from the first page, and then as a hidden value on that second page and each subsequent page if ZC page design is followed especially if using zen_ related functions.
So back to the "issue"... What is it? Meaning, what is the issue or problem now that so much of that has been explained. There is information available on the topic; however, I was not quickly able to find what I was looking for. I know that the instructions for the plugin CEON Uri mappings provides some discussion on it/it used to be on the applicable website; however, after the passing of the original author (Connor Kerr), some things have not been maintained as they were.
Bookmarks