Creating a Read Only Site

Permalink
Is there a way to configure Concrete5 to disable the database writes that occur for an anonymous user?

What I would like to do is configure Concrete5 with a mysql account that only has read only access to the database. This would prevent anyone outside the building from being able to write anything into the database. However, when I try, I see update failures to the Logs, PageStatistics, CollectionVersionBlocksOutputCache, and Areas tables.

Thanks

Joe

 
mkly replied on at Permalink Reply
mkly
Hello,
Have you taken look at Full Page Caching in the latest versions of concrete5? If you enable Full Page Caching and set it to "On - In all cases." this will serve pages without hitting the database. Also, disable statistics by going to Dashboard -> System & Settings -> SEO & Statistics -> Statistics and unchecking "Track page view statistics."

I should note that full page caching does not work with things like paginated page lists and some blocks, so this is something to keep and mind and you might need to make a couple adjustments to the site for that.

Best Wishes,
Mike
nospam4u replied on at Permalink Reply
Thanks for the response. Disabling page statistics did resolve one of the 4 database writes (the one to PageStatistics). The other three look to be more problematic. I have to imagine there is a way to disable the Logs, but the CollectionVersionBlocksOutputCache might be more problematic. And I have no idea why the Areas table needs to be updated by an anonymous user.

I will update as I go.
mkly replied on at Permalink Reply
mkly
Full Page Caching never hits the database. It was an intentional design decision. What is the Area query you are seeing?

Best Wishes,
Mike