Hi guys,
Something really weird is happening.
I am using the back-end, signed in as a system admin for this and checking in a separate browser and public user (not logged in).
I have made some changes recently (opening hours over xmas) that I wanted to disappear after the period was over.
I made the changes, put the page into safe edit, took away the changes, put the page into "approved to go live".
Now, we have a trigger set to put any asset that's "approved to go live" to "live" in an hours time. So, I deleted the future status for live, and set a future status for live in a few weeks time, after the xmas period.
No I checked the front end several times, with /_nocache, etc. And all was good. The asset was still in "Approved to go Live" and the initial changes were still showing.
The next day, the asset is still "Approved to go Live", the future status is still in the future status list, but the second changes (safe edit changes) have now been applied.
So it's like the safe edit changes have gone live when they weren't meant to, but the status of the asset and future status still havent changed.
I understand if this is something with our system, we will have to contact a squiz consultant, but I was wondering if I'm overlooking something. Have there been glitches with future status' that are deleted hanging around? Has anyone had Safe edit issues like this? etc?
It's extremely confusing and I hope the giant wall of text has not burnt your eyes.
Cheers.
"Approved to go Live" status possible glitch?
When you say: "Now, we have a trigger set to put any asset that's "approved to go live" to "safe edit" in an hours time" - do you mean a trigger "approved to go live" to "live"?
Either way is there trigger that re-applies the removed trigger to all pages in the site, say every 24 hours? You may need to look at the job listing in the cron manager.
Ahh crap. Edited, yes that's what I meant.
Will try this again and look at cron manager tomorrow. Thanks for your advice.
Just checked the cron manager for anything to do with workflow and status' during the time it happened and nothing showed up.
I would also check the trigger manager, to see if there is a trigger action applying the status change to assets, say once they've been released or something.
I just re-checked and there's not. The only thing set to put these events live is the one I mentiond, which I delete.
And like I said, the Asset's status hasn't changed. It's still in "Approved to Go Live" with the future status for "Live" there, but the changes have been applied.
I'm wondering does matrix have some automatic setting or something where if something is approved but not made live already, it applies the changes automatically but doesn't change the status, as not to mess with things?
I'm wondering does matrix have some automatic setting or something where if something is approved but not made live already, it applies the changes automatically but doesn't change the status, as not to mess with things?
Not as far as I know; the only way this could happen is through triggers.
How is the future status trigger you deleted applied to your assets in the first place?
Event:
- Status Change
Conditions:
- Tree Location - Asset is under site
- Asset current status of Safe Edit Approved To Go Live
Actions
- Set Future Status Offset 30 mins from immediate
Note: This trigger works fine like this and the asset's status doesn't actually change with the glitch mentioned, it stays as "Approved to go live" and the future status (manually set one after deleting trigger set one) is also still waiting for its time to change.
Hi Kieran, I built the trigger with the conditions you mentioned and it worked as expected.
You already said you were using a different browser as a public user to check the content, which it was showing, despite the status being unchanged.
The only other thing I can think of would be to check the permissions to make sure you don't have public read/write/admin access on that page.
Hmm, if it worked fine for you overnight then it must be something with us.
It's various pages on various sections of our (council) site and they dont have admin access.
This is going to be a nightmare to debugg.
Thanks for all your invested time.