Changes not displaying unless I use browser refresh

Posted: Mon Feb 25, 2008 11:48 am

This is not a problem for me on many domains running RN 2.1 on php4.

But RN 2.2 and php5, and several fresh installs on a couple of different servers, in both IE and Firefox, it is a problem. I don't know if it's the RN or the php.

Just one scenario...

Modules Admin ... change module from Inactive to Active.
Program asks if you really want to make the change? Select Yes.
Page refreshes without the change displayed in the modules table. To see the change displayed I need to refresh the browser page.

Same behavior for many other functions, like blocks admin, news saving ... etc.

The db tables are correct after making change, but something is preventing the change being displayed without refreshing the browser.

It's not fatal, but it makes the program feel a tad buggy and new admins need to be warned of the misbehavior.

First question ... anyone else experiencing the same thing?

Second question ... error logs aren't saying anything, how could I troubleshoot/fix this?

Posted: Mon Feb 25, 2008 11:54 am

If you look at the htaccess file you will see there are some caching settings there. You can disable these by commenting them out or deleting them but generally, you will find efficiency improvements with them the way they are.
Because of the caching it does impact what you see in the browser.

Posted: Tue Feb 26, 2008 7:24 am

WOW ... commenting out all the caching in .htaccess was a quick fix. Thanks!
However, how come this doesn't seem to be an issue for others? Is the problem with my php.ini? Or something else?

registered · Posted: Tue Feb 26, 2008 7:37 am

There was a post by Brujo (I think) recently which added another directive for PHP scripts to not cache. It seems that some hosted environments could need this. Sorry that I do not have time ATM to search for that thread, but it was a reply to Raven's post which suggested these caching parameters.

If you find that post and try it out, you may be able to take advantage of all the other caching statements.

Good catch "G"! Smile

Posted: Tue Feb 26, 2008 7:44 am

I have only really ever noticed it when doing some admin functions as I'm specifically looking for the data to change immediately. A lot of the admin functions repost the data (which is now cached) rather than doing a hard refresh. I'm living with it because under normal user circumstances it offers a tangible benefit.

Posted: Tue Feb 26, 2008 9:56 am

I found a post on the similar discussion here ... http://www.ravenphpscripts.com/postt15118.html

Thanks for the clue. Smile

Posted: Wed Feb 27, 2008 6:19 am