Page displaying differently when logged in

[mike62]

I'm working on a page and it's showing up differently when I'm logged in. It's not that a field is set to private or anything, because it's still pulling data from that field. It looks like the "public" view is simply using an old version of the template (home.php), and the logged-in view is using the current version of home.php. See attached screenshots.

Is there something that caches template files? Is there a way to force it to use the most recent version of the template?

EDIT: I found the Pro Cache module and cleared it. That seemed to help. 

Thanks,

-Mike

[mike62]

So, this isn't as "solved" as I thought it was. I'm still having caching issues, even though I've removed the Pro Cache module completely. On one browser, it's loading the most recent template files, but only when logged in, and it's still not loading the most recent CSS file. On another browser it'll load the most recent CSS file, but not the template files. It's making me crazy! Am I missing something obvious? This is making development extremely difficult.

[kongondo]

Template caching maybe? Check the Cache tab when editing the relevant template. As for CSS, browser cache? Chrome is notoriously 'cachy!'. You will want to develop with dev inspector open and set not to cache, if that is the case.

[mike62]

Ah, ok I see the Cache tab on the Template page now. Thank you! (I'm getting there, slowly but surely...!)

[SamC]

What @kongondo said for sure! I always keep the dev tools open now, css and js caching was a nightmare for me. This stops that, 'alt+cmd+i' on a macbook. Can't remember the windows desktop combo, maybe 'shift+alt+i'.

[DaveP]

In Chrome, with dev tools open, you can long-click the refresh button for browser cache-busting super powers.

[desbest]

54 minutes ago, DaveP said:

In Chrome, with dev tools open, you can long-click the refresh button for browser cache-busting super powers.

Alternatively you can hold down the shift button and click refresh to clear the cache for the website and refresh.

[mike62]

The problem I'm having is not to do with the browser's cache. I am updating home.php, uploading it, emptying the cache, and I'm still not seeing the changes I just made. It's very frustrating.

EDIT: It seems like the solution is to use this setting (see screenshot) for the template itself. Then to be able to see the changes I make:

1. Upload home.php via FTP.
2. In the ProcessWire admin, open the Home page and save it.
3. Switch to Chrome and empty its cache.
4. Switch to the tab with the site's homepage and refresh.

Is this correct? Is this the most efficient way to develop a site with PW? Seems arduous at best.

[Macrura]

@mike62

1) no need to remove ProCache
2) you should be logged into your admin when you are developing or trying to see uncached pages
3) make sure to add body class to cached pages so you can tell what is going on
4) install and use Tracy Debugger
5) make sure you have both wire_challenge and wires_challenge cookies in PC settings
6) if you for some reason do need to see the site when not logged in, add a get var, like ?nocache to the end of the url

by the way, what happened to your admin - it looks like the admin from a much earlier version of PW. You should check to see if your user has an admin theme selected...

By the way, i have never had to do any of the things you list, and work on live sites around 20 hrs a week.

[kongondo]

4 minutes ago, Macrura said:

by the way, what happened to your admin - it looks like the admin from a much earlier version of PW

Mike is using PW 2.3

[Macrura]

2 hours ago, kongondo said:

Mike is using PW 2.3

Doh! ok, i guess scratch #4 (don't think Tracy works on that version).. why not upgrade though, at least to 2.7.3?