Ongoing open beta (1.5.1) - Current Build: 45

[SteveJ]

Thanks to the developers.  You guys have patience that very few of us have.

[[Unknown]]

An Error Has Occurred!

Session check failure. Please try again.

this wos posted somewhere earlier .. it only comes up when clicking a logout link from somewhere on my main site (my site uses an iframe to display content)

is it fixable/gunna be fixed or shall i just delete the links to logout?

The logout action now requires a session id.

-[Unknown]

[Lance L]

Can anyone give me an idea of when 1.5.1 will be ready to come out of beta status?

Thanks!

[MORT]

An Error Has Occurred!

Session check failure. Please try again.

this wos posted somewhere earlier .. it only comes up when clicking a logout link from somewhere on my main site (my site uses an iframe to display content)

is it fixable/gunna be fixed or shall i just delete the links to logout?

The logout action now requires a session id.

-[Unknown]

k .. so i should just delete the link or wot?

[[Unknown]]

Can anyone give me an idea of when 1.5.1 will be ready to come out of beta status?

Thanks!

ANOTHER LLAMA DEAD!!!!

Check SSI.php for the logout stuff....

-[Unknown]

[Killer Possum]

Can anyone give me an idea of when 1.5.1 will be ready to come out of beta status?

Thanks!

some people just don't know the rules around here

[jbhlion]

This is a posting about an urgently needed bugfix for 1.5.1.

The separate thread, http://www.yabbse.org/community/index.php?board=178;action=display;threadid=16843, discusses and remedies a major problem that many users experience with remaining "logged in" to the forums. This problem, which apparently arises out of problems with storing cookies and managing asynchronous clocks (one on the host computer, one on the client computer), has prevented many users from being able to stay "logged in" at all and in fact makes many people unable to even use the forum if it is in "login required for reading" mode.

Has this been addressed in an earlier 1.5.1RC1 release? It doesn't appear to have been, as we've installed release 40 and the problem still exists. As we do not want to have to tell all of our users to clear their cookies in order to fix the problem, can the next release of 1.5.1 please use a new cookie name (or code of some sort to delete the old cookies automatically)?

Thanks.

[jbhlion]

And to add one other bug, we are still trying to figure out why the message, "Invalid Character in Username" comes up when using a three-character (purely alphabetical, no numbers, no spaces or other characters) username to log in -- a message that only comes up when checking the box to remain logged in. It may be related to the other issue described above.

[Owdy]

Print function does not work:
2: Failed opening '' for inclusion (include_path='.:/usr/local/lib/php:/www/int2000/a/****/html')
(/www/int2000/a/*****/html/foorumi/Printpage.php ln 35)

[jackamus]

Why would some users be getting an error message saying you can not change this persons profile.  They are logged in as themselves.  However when they go to post a message or edit the profile it tells them they must be logged in.  I could not duplicate the users error.  However, the forum error log does show the error?  Any sufgggestions?  

[[Unknown]]

Print function does not work:
2: Failed opening '' for inclusion (include_path='.:/usr/local/lib/php:/www/int2000/a/****/html')
(/www/int2000/a/*****/html/foorumi/Printpage.php ln 35)

You did not upload the newest Printpage.php, it does not include ANYTHING.

Why would some users be getting an error message saying you can not change this persons profile.  They are logged in as themselves.  However when they go to post a message or edit the profile it tells them they must be logged in.  I could not duplicate the users error.  However, the forum error log does show the error?  Any sufgggestions?  

Sounds like they are getting cached pages.  Ask them to clear their caches.

-[Unknown]

[Owdy]

You did not upload the newest Printpage.php, it does not include ANYTHING.

No i didnt because Installation Guide says nothin about that.

[[Unknown]]

*clears throat*

Considering the fact that this is a beta, some of the documentation files (ie readme.html) have not been updated.

To successfully upgrade your installation, please upload ALL the files in the package, except perhaps readme.html.

Thank you,
-[Unknown]

[Owdy]

*clears throat*

Considering the fact that this is a beta, some of the documentation files (ie readme.html) have not been updated.

To successfully upgrade your installation, please upload ALL the files in the package, except perhaps readme.html.

Thank you,
-[Unknown]

Ok, i understand that. That i dont understand why u include those misinformation files (such as readme) in upgrade paggage, if they contain wrong info. Why just cut them out?    Ill upload all exept template.php....

[PHPlugin]

Yeah ... it's a readme, so don't read it.
It's just to have it more formerly I guess,
having a readme in the update package!