Set Future Status / _recache

(Oliver Kass) #1

Hi,

 

We are looking to setup some auto publishing on our homepage news feed and I'm trying to figure out a way that means the Standard Page assets can be set to go live at a certain time and all users will see the new pages automatically.

 

As it stands when we need to ensure users will see the newest version of a page we need add _recache to the end of the page url. I was wondering if there was away of reproducing this with a trigger? If the page needs to go live at midnight for example there won't be anyone in the office to manually recache the page.

 

e.g if an asset under this tree location has its status changed to live then recache the location...

 

Anyone got any tips?

 

Thanks

 

Oli

 

 

(Tbaatar) #2

You could run 2 trigger to solve it:

 

 

Trigger 1: Set Future Status

 

Event: Asset Created

Condition: Asset Location and Asset is of Type

Action: Set Future Status and Clear Matrix Cache.

 

 

Trigger 2: Clear Cache

 

Event: Status Changed

Condition: Asset Location and Asset is of Type

Action: Clear Matrix Cache (select the asset you like to clear the cache).

#3

Hey oli,
You can set the cache specifically for certain root nodes. We have elements for our homepage that clear every time the cron runs ( every 15 minutes) especially for news items. So you could clear the cache frequently on an area - hourly? You can set this up in system management .


Or set a trigger -

Our news team is not publishing too many posts daily hence we don’t have to worry about you can create a future status to send an asset live at set a time. You can then set a trigger with has child/parent, on last published, set the root node and action of clearing the cache.



I’m sure the guys on here will have a more succinct plan of attack.

#4

Ha ha- what did I say !

(Oliver Kass) #5

Thanks folks. I'll do some testing.

 

Do you know if I need to factor the Squid cache into this as well?

#6

Ello there - if you don’t have a squid proxy then I’m not sure clearing the squid cache will do anything at all.

(Tbaatar) #7

fuzzi81 the custom cache for root node is nifty! never knew you could do that. Very useful for news sites for sure.

(Oliver Kass) #8

We do have a squid proxy and I think this could be why the tips above aren't working...may be best contacting Squiz direct about this one I think as it seems a bit more complicated than it should be.

#9

Ah ha! Yes if you are an SLA client you’ll need to get a support ticket in.

(Tbaatar) #10

You could try using the Clear Squid Cache as the action in the Trigger before sending support ticket?

#11

Yes of course! As tbaatar says :slight_smile: try this first.