Closed (works as designed)
Project:
Boost
Version:
7.x-1.x-dev
Component:
Expiration logic
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
22 Nov 2012 at 13:58 UTC
Updated:
3 Dec 2012 at 10:12 UTC
Jump to comment: Most recent
Comments
Comment #1
Anonymous (not verified) commentedSorry but this works as designed when en.domain.com/node/1 is expired (as in it is edited and then queued for the next cron job or manually flushed) then fr.domain.com/node/1 is going to not be touched because drupal is set up so that as you know, it can run multiple domains with differing content.
I also can't quite understand why editing the english version you would want to remove the french version at the same time when the french version would not have changed it's content unless I'm missing something.
If you really really wanted to do this flushing of one page removing the others, then you would link the folder under cache/normal/ so
cache/normal/fr.domain.com --> cache/normal/en.domain.com
but it does seem rather odd and I would think that it would break the site by only ever presenting the english version to your surfers.
Comment #2
F.G commentedHi Philip
"I also can't quite understand why editing the english version you would want to remove the french version "
For example : i update each day fresh informations for some nodes, like a new price : so if a new price is setup, i need to refresh all nodes for all languages.
note: i'm actualy triing to do it without "domain modules" just with locale an i18n modules.
Regards
Florent
Comment #3
Anonymous (not verified) commentedI think the only option would be to either manually remove the cached file in the other domain or untick the box under cache expiration:
Ignore a cache flush command if cron issued the request.and then manually flush the cache but that would flush everything. The problem is that everyone else is not going to want to flush their russian or swedish pages if they have just altered an english or french page, there just isn't the facility or the demand for this function. You'll need a custom module to hook into edit node if you want to expire the other domains.
Comment #4
F.G commentedHi Philip,
Infortunaltly, i don't have the skills to create sub module. So after a couple of days, i found a way to do it with domain (first request) and cache expiration which is buggy with domain. The important think is to check all affiliate and select alls subdomains, option on content type.
In a second step, i tried to see if it was possible to remake it without domain. Domain is a big module, and i'm afraid to install to much module on my small vps.