Closed (works as designed)
Project:
Boost
Version:
7.x-1.0-beta2
Component:
Cron Crawler
Priority:
Minor
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
29 Mar 2013 at 09:06 UTC
Updated:
29 Mar 2013 at 09:43 UTC
Jump to comment: Most recent
Comments
Comment #1
Anonymous (not verified) commentedBoost only displays cached content to non-logged in users, so this is perfectly normal behaviour. You would only see boost pages if logged out even after editing.
That would be normal too, the edited block would have been cached on previously viewed pages for non-logged in users, so you need to expire the family of items in the boost settings, and once again the cache would only be visible to non-logged in users. If you want logged in caching then you should be looking at AuthCache, FileCache and other mechanisms, there's a comparison somewhere on this site.
Comment #2
oriweissman commentedHi,
I understand that boost works only for non-logged-in users. The problem occurs when I update/add content in my computer and after that enter in another computer (as not looged in user) - the old content is being shown, not the updated one.
When i logout and refresh the other computers browser the cache is beign recreated and the new content is shown.
What about that?
Thanks
Comment #3
Anonymous (not verified) commentedThe boost crawler is not what you think it is, it is mis-named, and requires httprl to be installed and working. If a page is edited, it's added to the queue database table and generated on the next cron run. Cron itself is only triggered by a visit to the site so there's an element of delay. There is no "crawler' like a spider for page generation, it works solely on the user visiting a page. The "crawler" is for edited page regeneration, check the contents of the queue table when you edit a page. The other browser issue is probably due to caching and then a reload bringing up a boost page, or that the anonymous user is triggering the crawler or cron to regenerate the page.