Hi,
I am setting up a trigger in which this is the process:
Event: Status Changed
Conditions: Status = "up for review" and tree location
Actions: Send Email Trigger Action, Set status to Live, Set future status to "up for review" in 30 days.
This is all working well, no problems.
But then I try to add to the Send Email Trigger Action the "Asset to Send", which says the content of the asset will be send in the email in replace of the body of the email.
When I add my status here, the emails won't send AT ALL. Not even receiving a blank email as another user thread mentioned (this thread also did not have a final solution for them).
Am I missing something? Is it a bug? If a bug, is there a fix?
Thanks in advance!
Hi,
A very basic question I'd start with.
Is the trigger action failing? What I mean is, does the Logs have an entry saying something like "trigger_action_send_email failed" ?
[quote]
When I add my status here, the emails won't send AT ALL. Not even receiving a blank email as another user thread mentioned (this thread also did not have a final solution for them).
[/quote]
So by above, do you mean to say the trigger action to send email is working fine by itself. But the moment you add another trigger action to change the status, the email trigger action stops working?
What is the order of the trigger actions?
Ash
Hi Ash,
The trigger in general doesn't seem to be failing. I have checked the error Log and it doesn't have any errors from the trigger. And the set status and future status actions are still working, only the send email action that doesn't work.
[quote]So by above, do you mean to say the trigger action to send email is working fine by itself. But the moment you add another trigger action to change the status, the email trigger action stops working?[/quote]
The trigger action to send email is working even with my 2 other trigger actions. But as soon as I input an Asset to Send, the trigger action of sending an email doesn't work, but the other 2 actions still work.
[quote]What is the order of the trigger actions?[/quote]
The order is the same as I listed in my first post:
Send Email Trigger Action, then
Set status to Live, then
Set future status to "up for review" in 30 days.
Thanks for helping me with this. 
Hi,
Its always my pleasure to provide assistance to any getting stuck and using Forums. 
I tried what you have described on a 4.8.4 Version of Matrix and selecting asset to send (and even over-writing it by ticking check-box to use the asset that is firing the trigger) seems to be working smoothly. Is there any other factors coming in Play?
Like the asset being sent not being Live or having some restricted permissions.
If there is no errors in error.log Can you get you system Admin (if there is one) to check if there is any errors in the Mail logs for PHP.
Are you selecting the "asset to send" via the asset picker or just selecting the check box to send the Current asset which is firing the trigger?
Also what Version of Matrix are you using?
Ash
I wasn't sure if permissions would be a problem, so I have the "ignore permissions" checked just in case.
I have been selecting the asset just by entering the Asset ID, but when I commit the changes it recognises the asset because it fills in the name of the asset in the left-side box.
We are using Squiz Matrix v4.6.5
The asset I am trying to send will either be live, or will be the asset that triggered it (in which case it would have been made "up for review" and then set back to live by the same trigger). But there are 2 other assets that could possibly cause the trigger to fire, but the same asset should still be sent.
I am a System Admin user, but not sure how to access the php Mail logs. It is all hosted on the Squiz server, not our own.
Hi,
It looks like something specific to the configurations. As I couldn't replicate the issue on a 4.6.5 system either.
As you are Squiz Client, I'd suggest you raise a support ticket to determine the problem. Can't think of anything that can be causing this. And Since the Trigger isn't failing its very difficult to advise, without jumping in the code, what might possibly be going wrong.
Ash