Jump to content

Recommended Posts

Posted

I tried searching this, assuming I'd see others with the same issues, but I didn't see any similar threads, but apology if this is a repeat topic.

The site looks normal (as designed) while I'm logged in to the admin. If I log out, the CSS changes.

Been working on a site with a custom login page. The custom login is NOT being used to log into PW admin, however it does know and indicates I'm logged in. It's a user facing login for members. I was working on the site all day yesterday making CSS changes and adding some javascript to handle a video button that changes videosource. Prior to adding this JS, I never had this issue. The site looked normal when logged in or out, That was WITH the custom login.

I didn't even know what code to post if any, since this seems REALLY weird. Any thoughts on what might cause such behavior?

NOTE: I'm a graphic designer recently turned bad-developer, slowly improving. So, please filter your suggestions to someone with less than the common level of knowledge here.

Posted

Did you enable template caching? Try disabling it from Setup > Templates > my-template > Cache (or flush page cache from Modules > Page Render) or use @Soma's plugin (https://github.com/somatonic/ClearCacheAdmin)

Template cache (by default) is disabled for logged in users, so when you're logged in you're seeing whatever you're supposed to see, but when you log out you see the last cached version of that page.

Posted

Shit. Try logging in from an incognito window. 

If that doesnt work, go to /site/modules and rename ClearCacheAdmin to something else

Posted

I renamed the plugin, but still no login content was found. This is pretty strange. Maybe I should try a fresh install, and just replace the site folder with my current one?

Incognito window - same result.

Posted

Than the ClearCacheAdmin module isn't the problem, something else is at play here.

Let's try clearing module cache. Add this in home.php and visit homepage again

$modules->refresh();

 

Posted

I doubt home.php gets processed at all. Try echoing something and see if anything shows up. Or try force logging in yourself (put $session->forceLogin('admin') see if you can access backend)

If not, use site/ready.php (if it doesnt exists, create it) to put these codes in and see if it makes any difference

Posted

I wasn't really sure what was the real issue here, but by manually removing Modules.wire and Modules.site entries from caches table in DB, the issue was resolved after a brief Teamviewer support ^_^.

  • Like 6

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...