Fixing WebLogin Sessions That Work Only After Clearing Cache

A frustrating WebLogin symptom appears when users sign in successfully but still cannot access the protected resource until the site cache is cleared. In older Evolution CMS builds this usually means the login state, cached page output, or redirect flow is out of sync.

Where the Problem Usually Lives

• the protected resource is cached too aggressively
• login and redirect snippets are mixed between cached and uncached calls
• session state is valid, but the page shown after login was already rendered for a guest

What to Test

Use uncached login-related calls, verify that protected pages are not serving stale guest output, and test the same flow with both WebLogin and WebLoginPE under the same resource permissions.

If clearing cache immediately restores access, treat it as a caching mismatch first, not a password or permission problem.