Forum OpenACS Development: error with cookies

Collapse
Posted by Iuri Sampaio on
I get this page a little distorted on the right column take a look:
http://www.myybiz.net/file-storage/view/bugcookies.jpg

I'm concerned I get this page storaged on my cookies and somehow the error comes up. How do i get rid of it without having to locally delete cookies oftenly?

Collapse
2: Re: error with cookies (response to 1)
Posted by Torben Brosten on
Hi Iuri,

Verify that all of the urls to www.mybiz.net either include the prefix 'www.' or exclude it.

You can get around this also by using local references (ie:substitute "/" for "http://";) and then set the forcehost_p kernel parameter to 1.

hope this helps,
 Torben

Collapse
3: Re: error with cookies (response to 1)
Posted by Torben Brosten on
er.. I miss stated. substitute "http://domain.net/"; and "http://www.domain.net/"; with "/".
Collapse
4: Re: Re: error with cookies (response to 3)
Posted by Iuri Sampaio on
Torben,

i already checked the inlclude files. They all are being track from / dir. I put the page right bellow. and eve the pages are included have another include which are following the same path.

div id="main-container"
include src="/www/yabt/email"
table border="0" cellpadding="3" cellspacing="3" style="border-collapse: collapse" bordercolor="#111111" width="100%"
tr
td width="10%" valign="top"
include src="/www/yabt/left-menu"
/td
td width="80%" valign="top">
slave
/td
td width="10%" valign="top"
include src="/www/yabt/right-menu"
/td
/tr
/table

also. I didn't find the parameter you said forcehiost_p to change it to value 1

Collapse
5: Re: error with cookies (response to 1)
Posted by Torben Brosten on
my mistake, it's: ForceHostP

from /admin/site-map/ click on the "kernel" link at the bottom of the page.

Collapse
6: Re: Re: error with cookies (response to 5)
Posted by Iuri Sampaio on
ok i just changed to value 1. I'll post if i still get the error.

by the way...i'm interested to understand the parameters on of the packages. any docs??

Collapse
Posted by Iuri Sampaio on
Torben,
I still get the error on my computer.
The right menu with a new login page opened
http://www.myybiz.net/file-storage/view/bugcookies.jpg
Collapse
8: Re: error with cookies (response to 1)
Posted by Torben Brosten on
Okay. Hmm. Identify the source of the content for that registration window on the right, and you are half way there.

Could that source be referring to..

..an item (such as image) via https?

..an item from a different port? For example, if you are using a reverse proxy, or are serving other versions of the website on other ports.

Collapse
9: Re: error with cookies (response to 1)
Posted by Torben Brosten on
Here is the documentation to parameters:

https://openacs.org/doc/current/tutorial-parameters.html
https://openacs.org/api-doc/procs-file-view?path=packages/acs-tcl/tcl/parameter-procs.tcl

Parameters are implemented at the package level. This document provides some context: https://openacs.org/doc/current/packages.html

Collapse
10: Re: error with cookies (response to 1)
Posted by Torben Brosten on
Iuri, another possibility,

Maybe something in your registration page is trying to display something that requires you to login to see it...

Collapse
Posted by Iuri Sampaio on
i guess you got right there on the second last email.
"Could that source be referring to.."

although i don;t see where.

going deeper on the right menu page... there are only two includes: calendar and news
both pages to see ok even if you are not loged
http://www.myybiz.net/calendar/view
http://www.myybiz.net/news/

news is the one that as the scroling js. so far i see now items on it.

the weird thing is that once you get the error and login the error disapear, then if you log out the error doesn't come back.
wasn't it suposed to get back if the pages requires being loged?

Collapse
12: Re: error with cookies (response to 1)
Posted by Torben Brosten on
Well, Iuri, I don't see the error on your site, so am unable to help identify the problem.

Try examining the page source on cases where you get the error.

You could look for 302 redirects in the server.log file for any hints. If there is a pattern, hopefully you can see it there. For example:

grep ' 302 ' server.log*

and verify the urls for each case work as expected instead of returning a login page.

You need to identify cases that are repeatible. It seems that the problem is no longer predictable, which makes solving it more difficult.