Comment 3 for bug 142615

I did this using Zope 2.6.2. I did not test that with newer versions.

step1: place a browser_id_manager in your test application folder and change the entry "Browser id name" in the browser_id_manager page to a desired name.

step1b: add a session_data_manager with session_data etc. in the test app folder (and as i did the CookieCrumbler)

step2: build a page template with code that reads some SESSION data

step3: build a python func (in ZMI) that reads or manipulates the SESSION data

step4: glue that together with some nice HTML forms - actually the SESSION was meant to transport form data from multiple forms to the last form. Each form calls a python script that fills the data from thle last form into the SESSION data and calls the next TAL HTML form and so on till the last form is reached an a summary is shown (as zpt)

This works fine as long as you don´t change the Browser id name. If you do, Zope places two Cookies into the browser and creates two SESSION objects. The zpt forms (which in my example show some of the entered data of the prev. forms) see the one SESSION data, the python scripts see the other SESSION data.

I consider this a bug. I did not any more research on that, I simply let the name unchanged and that´s it. (But that´s a workaround..) Again, I did that on Zope 2.6.2.