It seems the solution was to clean out var/cache. Weird since I would have thought that the Admin interface's cache clearing buttons would have had the same effect (guess that's not always true!).
Maybe 3.1-1 suffers from the same cache bug problem as 3.2-1? You could try upgrading to 3.2-2, if that's suitable for you (it's not fairly easy and safe). Also if you're developing templates you might find it easier to disable caching for the time (option in site.ini, or site.ini.append in siteaccess) - it saves some confusion.
~James~
You must be logged in to post messages in this topic!
