Icy Phoenix

Hi you all again (yes, me again...)!!

This time I have no idea where to begin the research. Some users are experiencing an unusual issue. When they click Quick Reply, the navigator moves the page to the top, if they go to the bottom, the quick reply block is there and they can answer, but it sucks when you are reading a long post and needs to go down again. If they click quick quote, nothing happens (no page movement, and no block for answer appears, I mean that nothing happens in the way that there is no change, it works wrong too).

One user told us that this is happening to him with Chrome, but it does not happens with Opera. Other one told us that with Firefox the problem was there and was not with IE, but I don't have the problem with Firefox or Safari.

Now I think I have an idea on were can be the problem. The first time I opened the 2.0 version on Firefox, somethings didn't worked, like Fonts and templates. I needed to refresh the page and everything became ok. Maybe the Firefox's cache is making some trouble. I will tell my users to refresh and report here if this solved the problem.

PD: after refreshing one of the users solved the problem.

make shure, that you have yoiu´re cookies correct

like for example .yoursite.com

special eye on the dot

spydie wrote: [View Post]

make shure, that you have yoiu´re cookies correct

like for example .yoursite.com

special eye on the dot

really????

I will tell users with problems to clear cookies.

i mean you´re cookie settings on your site

cookie domain etc

spydie wrote: [View Post]

i mean you´re cookie settings on your site

cookie domain etc

How can this work fine for some users and wrong for some others?

They are ok from the beginning. As you explained and explained at some Readme I found inside icy phoenix pack.

The problem was the caché of their navigators. As this happened after the upgrade from 1.2.0.27c, the navigators had the cached version of viewtopic.php (not the code, I think you understand), and this made the miss behavior.

Solved with a forced refresh (Ctrl+F5 on most navigators).

There is no relation between this and cookies.

(I think I have written here this answer before).

Thank you spydie for your help.

CTRL + F5 is the best invention after the wheel. :mricy: