I'm really sorry, everybody. I'm creating this issue as a dupe of one I created in the wrong category (Issue 459530).
Anyway, here was my original question:

Hi. I'm using Boost on a high-traffic site and it's fantastic. I've been reading the documentation and there's something important I don't understand: When you update a page, does boost clear that page from the html page cache? One poster claimed that boost_nodeapi does that, but it doesn't on my server. Is there some way I'm supposed to hook it up?

Here is my response upon finding out that the code does clear an html, but NOT the one I wanted it to clear:
Hah! just figured it out. In the boost_nodeapi function, the call to expire the cache only works with pages called "node/NN". Like so: boost_cache_expire('node/' . $node->nid, TRUE);
However, my page is called "about_us/our_mission" and so the cache_expire code doesn't delete the html. So it would seem to me that all that is needed is a more flexible param with the actual [nodename].html passed to it.

So here is my question to all of you: What am I missing?? It seems so obvious to just write an algorithm to clear the [actual-page-name-].html. I'm sure someone has already done that?

Wisdom would be much appreciated.

CommentFileSizeAuthor
#4 boost-459956.patch774 bytesmikeytown2

Comments

Dracolyte’s picture

Dracolyte commented

Okay, sorry again. I see now that all the cache_expire func is doing is expiring the cached page so it is cleaned up next time the [cache-expires?]/[cron runs?]. So I'm really looking for a boost_delete_html_version function. Is there one out there? I'll give it a shot myself.

mikeytown2’s picture

mikeytown2 commented
Status: Active » Closed (duplicate)

The way it should work, is the cached html file gets nuked when the node is updated; if that page is a node. If its not a node, then odds are it will not be cleared until cron is run. I've only done minimal testing on this, since the symlink patch. This feature works for me, but once this issue is completed, it should be less of an issue.
#368366: Boost Block - Button: Flush Page's Cache

Marking this a dup of this issue.
#443736: Smarter boost_cache_expire(). Path Changes & Wildcard Support

tntclaus’s picture

tntclaus commented
Priority: Normal » Critical

hi!

I experience the same problem at my high traffic site. After adding new node the front page doesn't update (logged in users see updated page, it's ok, but anonymous visitors see old page).

Can anyone help me?

mikeytown2’s picture

mikeytown2 commented
Title: Boost not clearing updated pages from cache » Flush front page when node is edited/created with promote to front page selected.
Priority: Critical » Normal
Status: Closed (duplicate) » Needs review
StatusFileSize
new boost-459956.patch774 bytes

@tntclaus
Your describing a complicated situation. Luckily it's the front page your complaining about. So to reiterate your situation, you create a node that has the "Promoted to front page" checked under Publishing options. So if a node is promoted & has been created/edited/ect... flush the front page. Patch below should do that; I haven't tested it yet, but is should work.

tntclaus’s picture

tntclaus commented
Title: Flush front page when node is edited/created with promote to front page selected. » Boost not clearing updated pages from cache
Priority: Normal » Critical
Status: Needs review » Closed (duplicate)

thanks alot :)
is this patch suitable for boost 6.x-1.0-beta2?

**UPD: sorry for unfortunately change of status/topic etc. I've posted another message with backchange

tntclaus’s picture

tntclaus commented

thanks alot :)
is this patch suitable for boost 6.x-1.0-beta2?

mikeytown2’s picture

mikeytown2 commented
Title: Boost not clearing updated pages from cache » Flush front page when node is edited/created with promote to front page selected.
Priority: Critical » Normal
Status: Closed (duplicate) » Needs review

yep ;)
enable the boost block as well, you might like it.

tntclaus’s picture

tntclaus commented

thanks! it works well.

I really love boost module :)

>> enable the boost block as well, you might like it.

what does it do?

mikeytown2’s picture

mikeytown2 commented
Status: Needs review » Reviewed & tested by the community

displays a 'flush page' button; lets you know how much longer till the current page expires. And with this patch, allows for different expiration times. It displays/works for any user who is not anonymous; need to work on permission for it soon most likely.

tntclaus’s picture

tntclaus commented

ok, I think this block is useful in debug mode ;)

I've thought about flushing cache when node is cr8ed or updated. I think it would be good to add block to admin/performance page, where you could set an array of pages, whose cache should be flushed in the case of updating/editing nodes. Perhaps there should be a single array of pages for each node type or even taxonomy term etc.

I have a huge site with ~30k unique visitors / day, and there're lots of pages generated by views module, containing grouped by taxonomy/node type. So I need to update not only the front page, but several other pages.

If you find this feature useful but do not have time right now to work over it, I can try to help and write some code ;)

mikeytown2’s picture

mikeytown2 commented
Status: Reviewed & tested by the community » Fixed

committed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.