293961
sunsnapper
Re: Browser cache causing many problems?

That makes me wonder if an "Expire" meta tag would help solve this problem. In other words if we put this code in the <HEAD> of the "Sorry..." redirect page:
<meta-http-equiv="Expires" content="Thursday, 10-Jan-69 00:00:00 GMT">
or
<META HTTP-EQUIV="Expires" CONTENT="-1">


This and other cache possibilities described at this link: The Open Web Application Security Project

(I should have read Steve's entire post... he just said that. Oh well).


<small>[ Edited by sunsnapper on 2002/6/13 23:46:02 ]</small>



293962
dscg
Re: Browser cache causing many problems?
  • 2002/6/14 7:06

  • dscg

  • Just popping in

  • Posts: 9

  • Since: 2002/6/7 8


I don't know if your problem has been solved, but I've also had many problems with that damn "Sorry..." message.

What I've found during my testing of XOOPS is that the browser is caching the "Sorry..." redirect page and I have to force the browser to refresh the page to make things work right.

For example, consider this scenario...
1. I set anonymous user permissions to the contacts module to off.
2. I logout and try to access the contacts module and get the old "Sorry, you don't have permissions..." message. Good so far.
3. Now I log back in and change the anonymous user permissions to the contacts module to on.
4. I logout and try to access the contacts module and still I get the "Sorry..." message. Not so good anymore.
5. Now, if I try to access the contacts module again, and I immediately press the browser refresh button before the browser can redirect me, I can get to the conacts module.

I think this browser caching issue is causing a lot of the problems that people are attributing to cookies. Also caching may be the cause of problems where it "appears" that updated settings are not taking effect.

Possible solutions to this may be to add a line to the page headers to prevent caching. Either...

<meta-http-equiv="Expires" content="Thursday, 10-Jan-69 00:00:00 GMT">

or <META HTTP-EQUIV="Expires" CONTENT="-1">

or <meta http-equiv="Pragma" content="no_cache">

or <META HTTP-EQUIV="Cache-Control" CONTENT="no cache">




293963
onokazu
Re: RC3 recent discussions block: why 'Re:'?
  • 2002/6/13 11:42

  • onokazu

  • XOOPS Founder

  • Posts: 617

  • Since: 2001/12/13


thanks. will add this to RC3.0.1



293964
MrSmith
Re: RC3 recent discussions block: why 'Re:'?
  • 2002/6/13 8:04

  • MrSmith

  • Just popping in

  • Posts: 12

  • Since: 2002/5/12


Thanks for the fix! It was line 453 on my system as well.

<small>[ Edited by MrSmith on 2002/6/13 8:04:59 ]</small>



293965
MrSmith
Re: Default Comment Order not being set properly for new users
  • 2002/6/12 12:27

  • MrSmith

  • Just popping in

  • Posts: 12

  • Since: 2002/5/12


Quote:
why not just set in "Preferences" default comments order to "oldest first" ??


I did have it set that way in my preferences but it wasn't working. XOOPS is hardcoded to use "Newest First" for the viewing mode when new users sign up. As it is right now, the setting in preferences is only affecting anonymous users.

The change I suggested hard codes it so that "oldest first" is the default viewing mode for new users. What really should be done is that it should take the setting specified from preferences, which is what it looks like the developers will do.




293966
onokazu
Re: Default Comment Order not being set properly for new users
  • 2002/6/12 8:00

  • onokazu

  • XOOPS Founder

  • Posts: 617

  • Since: 2001/12/13


Quote:

MrSmith wrote:
Nevermind.. I found it. In case anyone else wants to know, look at function store in class XoopsUser in class/xoopsuser.php (line 227)

You will see that its using a defalut value of "1" for uorder. If you want oldest first as your default view mode for new users, set this to "0"


thanks, we will fix this



293967
netwize
Re: Default Comment Order not being set properly for new users
  • 2002/6/12 7:20

  • netwize

  • Just popping in

  • Posts: 89

  • Since: 2002/1/20


why not just set in "Preferences" default comments order to "oldest first" ??



293968
MrSmith
Re: Default Comment Order not being set properly for new users
  • 2002/6/12 6:38

  • MrSmith

  • Just popping in

  • Posts: 12

  • Since: 2002/5/12


Nevermind.. I found it. In case anyone else wants to know, look at function store in class XoopsUser in class/xoopsuser.php (line 227)

You will see that its using a defalut value of "1" for uorder. If you want oldest first as your default view mode for new users, set this to "0"



293969
MrSmith
Re: Default Comment Order not being set properly for new users
  • 2002/6/12 6:38

  • MrSmith

  • Just popping in

  • Posts: 12

  • Since: 2002/5/12


Nevermind.. I found it. In case anyone else wants to know, look at function store in class XoopsUser in class/xoopsuser.php (line 227)

You will see that its using a defalut value of "1" for uorder. If you want oldest first as your default view mode for new users, set this to "0"



293970
MrSmith
Default Comment Order not being set properly for new users
  • 2002/6/12 6:21

  • MrSmith

  • Just popping in

  • Posts: 12

  • Since: 2002/5/12


I have my default comment viewing order set to "oldest first" which works fine for the anonymous users, but when new users register it sets the users default view mode to "Newest First" which is quite confusing to alot of my members.

How can I change things so that all new users are created with the correct default view mode?

I've looked through register.php, and tried to hardcode it with

$newuser->setVar("uorder", 0);

but that didn't do it. Anyone have any other ideas?







Login

Who's Online

164 user(s) are online (110 user(s) are browsing Support Forums)


Members: 0


Guests: 164


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: May 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits