I don't know why. All else works Great! Just on question. Do I have to turn off normal Drupal caching or can I leave it on. I think off but the instructions leave room for doubt.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | boost-590704.patch | 1.24 KB | mikeytown2 |
I don't know why. All else works Great! Just on question. Do I have to turn off normal Drupal caching or can I leave it on. I think off but the instructions leave room for doubt.
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | boost-590704.patch | 1.24 KB | mikeytown2 |
Comments
Comment #1
mikeytown2 commented6.14 seems to be caching url variables; which means the crawler request could be getting cached. I should change the request to a POST instead of a GET, to avoid any other caching issues.
#589180: Core & Boost cache enabled, nocache set; core caches page
Normally you can leave both on and encounter no side effects, but with Drupal fixing a page caching bug I recommend turning it off for now. Let me know if this fixed the crawler for you.
Comment #2
mikeytown2 commentedComment #3
dbeall commentedIt didn't make any diff in 6.13
I was wondering the same thing as OP about Drupal cache..
Should there be a
note: ?
Comment #4
dbeall commenteddisabled Drupal page cache gives new nodewords error
this has been reported http://drupal.org/node/589814
Comment #5
dbeall commentedcrawl on cron with and with out Drupal cache working 6.14.. With OUT patch..
should this go in?
Comment #6
mikeytown2 commentedyeah, will help with future caching schemes, doing a post prevents that page from getting cached.
Comment #7
mikeytown2 commentedcommitted