Asunto: [bug] Access pages

Hi,

This is about 1 week i noted that when i click to see a new page (forum, office, players, transfers...), this is happen :

[url=https://zupimages.net/viewer.php?id=23/10/xw57.jpg][/url]

And i have to click to sokker shortcut bookmark on FF again and i have to click on Go Back to game :

[url=https://zupimages.net/viewer.php?id=23/10/ljek.jpg][/url]
(editado)

And strange also. To see the screenshots taken, i have to click on it otherwise, i did not see anything.

Weird again, now, i see them :-)

Chrome: shift + f5
Firefox: ctrl + f5

+ log out and log in again.

Thx a lot !! :-)

I tested again after doing your process. It seems OK, i tested over 30 different screens.

Another point : i noted a latency when i click on League screen and on Country screen. About 5 seconds, even after CTRL+F5 and L-Off-L-in.
And when i see transfer player, there is also a latency when i see the price, about 2-5 seconds.

Hi Geston,

It is a bit boring because it happens everyday and even many times everyday till yesterday. I had to do your process.
But now, even after having done your process, i can't go anymore to my club page. It gives the screenshot above.

I'm really blocked. I can't go to the NT team to send an invitation, neither to send a SKmail. Because the site blocks me when clicking on team page.

If you're on the new team page of your opponent, click next matches, you'll be redirected to the old matches page.

Or use the following link

https://sokker.org/matches/teamID/**/page/0

** Insert country ID

Indeed, you can go to the old pages, but after doing this there will be a new bug blocking the page.

Me too and this is the information on the console:

11:21:35.804 Cookie “theme” does not have a proper “SameSite” attribute value. Soon, cookies without the “SameSite” attribute or with an invalid value will be treated as “Lax”. This means that the cookie will no longer be sent in third-party contexts. If your application depends on this cookie being available in such contexts, please add the “SameSite=None“ attribute to it. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite _app-b2fed0fb20044e1671ba.js:1:30002
11:21:36.860 react-i18next:: It seems you are still using the old wait option, you may migrate to the new useSuspense behaviour. _app-b2fed0fb20044e1671ba.js:1:47138
11:21:42.375 TypeError: G is undefined
NextJS 26
framework-336caa3f6419768205fe.js:1:83586
11:21:42.376 TypeError: G is undefined
NextJS 26
main-c56d9bb971f987d0d92a.js:1:8712
11:21:42.376 A client-side exception has occurred, see here for more info: https://nextjs.org/docs/messages/client-side-exception-occurred main-c56d9bb971f987d0d92a.js:1:8729