I'm guessing the login option is on all pages and as such, you may experience cache issues with 2 HTTP headers that were added in K2 v2.10.3 and will be optional in the upcoming v2.10.4.

To resolve this now (until 2.10.4 is out), please do this: www.joomlaworks.net/forum/k2-en/54343-cache-problem-with-2-10-3#176573

Test with a private browser window. Depending on your cache duration in Joomla, your browser may had cached the entire output, in which case the user token in forms would be incorrect.

I can't think of anything else. I'll need an actual URL to check on your site's HTTP headers.

I meant just the URL for starters. Otherwise use this: www.joomlaworks.net/support/get-help/contact

OK, so my guess is that you're dealing with cache issues either related to the server or Joomla (through some 3rd party extension). If I use the /login.html path, I get all sorts of warnings (e.g. wrong token, sign in again etc.), despite Joomla having me logged in already, cause if I browser to one of the user actions (through the menu), I can see my profile edit page. Now if I use /index.php?option=com_users&task=login I can login and browse the site just fine.

This means something is switching off cache-control for URLs with com_users but not with /login.html.

So check your Page Cache system plugin for starters and if it's enabled, add the right exclusions under the Advanced tab. If you use another caching plugin, search for similar exclusions as well.

All I can say is that this is not a K2 issue really.

1. That extensions does not modify Joomla's caching, it merely deletes it. It's useful to have.
2. Install v2.10.2 on top of v2.10.3. However I insist the issue is elsewhere. When you disable "all K2 extensions" as you say, you may also have disabled a 3rd party extension for K2.

After a 2nd look, it's most likely the system plugin in K2 caused a different issue with how plugins can inject stuff in the document body. You can install K2 v2.10.4 (dev) on top of 2.10.2 to test as well: getk2.org/downloads/?f=K2_Development_Release.zip

My guess is it will resolve your issue. If it doesn't, you can switch back to 2.10.2 again.

It may say "dev", but all code commits are double-checked. Anyway...