Google Crawling - cached items

Permalink
I have a client who requires some data to be kept private, and only accessible from those allowed to view it.

With the built in permissions in Concrete5 this is find but I am not to sure who the cache would deal with this?,

Am I able to set a page to be private and have the files, content associated with that page be removed from the cache?

This is mainly for images as my client runs a gallery but could be content as well.

Im thinking I may be able to use the deletecache and pass the id of the images through?

TheRealSean
 
ijessup replied on at Permalink Reply
ijessup
Though I'm not 100% sure I understand the question... try setting the pages to private and then clearing the cache from the 'Sitewide Settings' page in the dashboard.

I haven't messed with the caching system enough to know how it works, but this should at least point you in the right direction.
TheRealSean replied on at Permalink Reply
TheRealSean
My client creates a gallery(page) in the dashboard, which is assigned various page attributes and a file-set.

When creating the page I have noticed that I could use the cache functions to manually add the files to the cache, but on visiting the gallery page, the link hangs whilst the images are created/loaded

But once the images have created a cache version the pages seem to load quicker.

I wander if I can use Concretes inbuilt cache to cache the page on creation and then delete it once made private(permissions)

I am going to add the cache to the robots text so that the search engines can not crawl this not but I wanted to check.

Currently I am telling our client that they need to remove the cache after making a page private (altering the permissions)

Im not sure if that is any clearer but thank you for your post.
ijessup replied on at Permalink Reply
ijessup
"I see." said the blind man.

So basically, the images need to be cached before you have a fully cached page.

If I remember correctly, c5 uses the gd library to manipulate images, as well as make smaller cached versions.

I'm assuming here, but I think the images don't get cached until someone actually views the page.

I'd start with the dispatcher.php file and see where the block caching mechanisms take you. You may be caching an empty page because the blocks themselves are getting cached?