Release v3.2.0 beta

[marrco]

@shawn_a the only plugin i run in the site not properly caching is p01-contact, which doesn't seem to directly set the no-cacheheader. But (there's always a but) that plugin set a session cookie, and that's the only other difference i spotted between the cachable and non cachable site.

Add to that that the regular p01-contact has bug (because of user.xml) that exhibits on every page of the site. I mean, whatever page of my website i visit a line in error log gets written notifying of the error in that plugin not finding user.xml. I manually fixed that bug, but why do i get the error on the home page also?

i still don't know if the session cookie that p01-contact sets is the cause for the added pragma:no-cache, but i'd like have a more resilient getsimple with better plugin isolation so that a faulty plugin (i'm still looking for a contact plugin that allows me to easily create a nice ordered multi-colon form layout) doesn't interfere with other pages.
Maybe coding guidelines are sufficient, but i think something should prevent that a contact form plugin disables caching even on the home page. And that could easily shave many ms when a user navigates back to a page he already visited.