Does the exclude only apply to nodes?
| Project: | CacheExclude |
| Version: | 6.x-2.1 |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | ebrand |
| Status: | closed |
Jump to:
I see the other question about how you probably can't exclude from views, but I have a similar question. I have a ton of images that are just in my /screenshots directory. I don't want any of them cached because for whatever reason they're being cached as 404's, though they still appear properly to anons.
I've tried tons of different variations of screenshots/* and nothing is stopping them from being cached (verified in the cache_page table). Does Cache Exclude stop non-nodes from being cached? Should it? Personally, I think so: if it's being cached by Drupal this module should be able to exclude it.
Additionally is there any way to stop 404's from being cached. The other day my front page got cached as a 404 (WTF?!) and it totally freaked me out, which got me to looking at Cache Exclude in the first place.
#1
It's unclear from your comment if /screenshots is a directory on disk or if you're referring to a path pattern in Drupal. If they're files on disk then Drupal should never even get called.
Note that this module also prevents a page from getting cached; it does not skip a cache entry that is already present. When in doubt flush your entire cache and then try. If you have a page that is already cached then this module doesn't even get called.
#2
/screenshots is a directory on disk, Drupal should not know about it but yet there are /screenshots entries in my cache-page table.
#3
Clear your cache first. If a file exists literally on disk then Drupal shouldn't even be called. That has nothing to do with this module.
#4
Did this work for you? Or are the photos still showing up in the cache table?
#5
No response from user, so I presume it's working.
#6
Automatically closed -- issue fixed for 2 weeks with no activity.