The test email on the newsletter editor arrives correctly, but when sent arrives to the user likes this:
<div style="font-family:Fira Sans,Helvetica,Arial,Verdana,Trebuchet
MS;font-size:13px;line-height:1;text-align:right;color:#000"><a href="[VIEWBROWSERURL]" style="color:#477626" moz-do-not-send="true">Ver en el navegador</a></div>
Also checked the user has a proper UUID.
Installed are latest versions and latest plugin version too. Not sure what else to test or how to debug further.
Thanks @duncanc
I understand this is the relevant part (it is another test)
Plugins? Active:
CKEditorPlugin, CommonPlugin (3.11.2), domainthrottlemap, inviteplugin, restapi. SegmentPlugin, ViewBrowserPlugin
@luison Ah yes, you did say.
Please show the source of the message in phplist. If you are using the editor then show the html using the Source toolbar button.
Is this the firs time that you have tried using the plugin, or was it working before but now is not?
How do you process the queue - a cron job or through the browser?
Hi again
Bellow is the test source code we are using as URL as this is the case we have the issue. Have also tried including the HTML in the editor. Same result.
We had issues before but thought they were related to having separate languages, subscription pages.
We use a cron to execute the queue.
@luison Thanks. I am guessing that when you run a cron job it uses a different version/configuration of php than the web server, which causes the plugin to not be enabled. Possibly the xsl extension is not present in the php configuration.
If you are able to run this from a command line or as a cron job to capture the php configuration php -i > phpconfig.txt
Can you try sending a campaign with processing the queue through the browser to see whether that is any different?
That was the issue thanks. Works with except the [USERID] which shows correctly on the email but not on the linked browser version. That might likely be intentioned behaviour.
xsl module was loaded in PHP but the cron was going via a bash script that was executing a different version of PHP which likely did not have it. I should have deduced it from it working on the test version but not the cron. Sorry.
@luison I think that using USERID may be historical. Some of the phplist documentation now refers to UNIQID. They refer to the same value, the 32 character string in the uniqid column of the user table.