Page 1 of 2

farming on main/ascend *FIXED*

Posted: Fri Aug 05, 2016 11:09 am
by byrne_1
Since last night, I notice when farming on both main and ascend. data on it dont update when i push back space. ie amount of naqs in the open or units in the open.

Is this a new update.

Re: farming on main/ascend

Posted: Fri Aug 05, 2016 1:00 pm
by Support
Good call, thanks for the clear description.

It was an unintended side-effect of some other updates. Ideally it should now be resolved. :)

Re: farming on main/ascend

Posted: Fri Aug 05, 2016 4:04 pm
by My_Crows
Support wrote:Good call, thanks for the clear description.

It was an unintended side-effect of some other updates. Ideally it should now be resolved. :)
Oh thank God lol

Re: farming on main/ascend

Posted: Fri Aug 05, 2016 7:50 pm
by ombre
It is still here. Quite annoying this bug. :D

Re: farming on main/ascend

Posted: Fri Aug 05, 2016 10:05 pm
by Support
'here' meaning 'on Ascended'?
ombre wrote:It is still here. Quite annoying this bug. :D

Re: farming on main/ascend

Posted: Fri Aug 05, 2016 10:46 pm
by Human
This problem exists since long time ago when I use the default internet apps on android but bearable as I only login from mobile once in a while.

Since yesterday, the same issue occurs when I am using Chrome on my laptop (still unresolved at this point). As an added info, no such issue when I am using Firefox. Main account. Didn't try Ascended.

Thanks

Re: farming on main/ascend

Posted: Sat Aug 06, 2016 6:42 am
by ombre
I still have it on ascended and on main. And i use Firefox.

Re: farming on main/ascend

Posted: Sat Aug 06, 2016 7:19 am
by Mental
still there for me on main and ascended using chrome.

Refreshing the page corrects it, but cannot see my own or farms correct naq until I do that.

Re: farming on main/ascend

Posted: Sat Aug 06, 2016 7:20 am
by Support
Thank you for clarifying your reports. :) Appreciate it!


There are some browser-specific 'bugs'/'features' that affect cache control. I have reviewed and restructured this on our end, the rest is -unfortunately- out of our hands.

As a final measure, please clear your cache (or use the 'Forget Website' feature), and try again.

Re: farming on main/ascend

Posted: Sat Aug 06, 2016 8:33 am
by reborn
Works fine on IE.

But chrome and FF still wont work same as IE until like Mental said you need to F5, cleared all chahe many times even went as far as removing chrome and still wont work.

( Chrome is the only browers i can get to work on phone ) :S

Re: farming on main/ascend

Posted: Sat Aug 06, 2016 12:36 pm
by R0B3RT
is not only on farm [-X all pages
on sab when i turn back button says sabbbbbbbbbotaging and can click it

i use firefox

Re: farming on main/ascend

Posted: Sat Aug 06, 2016 4:16 pm
by Support
The web is designed to move forward, not backwards.

Going 'back' tells your browser you want to see the page you were previously on. By definition, that means it will NOT reload the content of that page (instead calling it from any existing browser cache). Instead of moving backwards, move forward.
Chrome (traditionally very 'helpful'), and Firefox have had a few updates that follow that particular line of thought. (Personally, I dislike the trend, but understand the paradigm.)


So, the best I can do is forcing a refresh when you use the 'Back' button, but that is going to affect performance client-side. Most notably, it is going to cause a reload-flicker. If you want, you can test the speed of using the Back-button versus moving to the Ranking where you came from, from the Attack Log.
Alternatively, upon visiting the battle log, you can get redirected to the page your attack originated from (either the Ranking or 'Attack' page) after 3 seconds.


So, putting this up for you guys. Let me know which option you prefer:
1) the forced refresh using the "Back" button (including reload flicker)
2) redirect after 3 seconds of displaying the battle result

Re: farming on main/ascend

Posted: Sat Aug 06, 2016 9:07 pm
by ~nyx~
:S idk just want it how it was,

ascended was fine for me until today. (firefox) :smt089

Re: farming on main/ascend

Posted: Sat Aug 06, 2016 9:20 pm
by R0B3RT
Support wrote:The web is designed to move forward, not backwards.

Going 'back' tells your browser you want to see the page you were previously on. By definition, that means it will NOT reload the content of that page (instead calling it from any existing browser cache). Instead of moving backwards, move forward.
Chrome (traditionally very 'helpful'), and Firefox have had a few updates that follow that particular line of thought. (Personally, I dislike the trend, but understand the paradigm.)


So, the best I can do is forcing a refresh when you use the 'Back' button, but that is going to affect performance client-side. Most notably, it is going to cause a reload-flicker. If you want, you can test the speed of using the Back-button versus moving to the Ranking where you came from, from the Attack Log.
Alternatively, upon visiting the battle log, you can get redirected to the page your attack originated from (either the Ranking or 'Attack' page) after 3 seconds.


So, putting this up for you guys. Let me know which option you prefer:
1) the forced refresh using the "Back" button (including reload flicker)
2) redirect after 3 seconds of displaying the battle result
i tryed refresh ;) not work
iff someone farm i can,t sit on him :( i will never see the real amount naq out
not tested in on line batlle but for sure i will not see iff the other player move naq \uu

Re: farming on main/ascend

Posted: Sat Aug 06, 2016 10:20 pm
by ~nyx~
refresh wasn't working for me neither (firefox),