I have checked the ns_Newsletter and there is nothing wrong there, the markup is exactly like given.
There is no error in the logs, the rendertask is there and other render tasks are working.
I am using 2.1.4 on 7.1.8 - everything else seems to be working. Just not the readonline rendertask.
What is the URL that I should be expecting to be replaced exactly? I believe the id is added somewhere but would like to know the URL that is supposed to be replaced so I can check further.
Is it possible to share the source code for this readonline render task, so i can add debugging/logging to see what is going on?
Did the order of execution or logic changed in latest 2.1.4 ?
I have been using the exact same newsletter.config in previous version 2.0/1, in the exact same order, and it was working as expected.
When i upgraded to 2.1.4, somehow the order of the render tasks needed to be updated otherwise the readonline was not working, as explained in OP.
When the render tasks are stacked one after another, it would be great if a "debug" flag can be set so the NS can log somewhere the render task X executed/called, maybe return/status code, and the order of execution can be diagnosed in similar cases.
ReadOnline doesnt seem to be working
Using the latest 2.4 NS on a 7.1.8 install.
1) I insert Read Online link via the Insert-merge-field,
2) I checked the rendertask is in place in the /config/newsletter.config for readonline (i.e. untouched)
3) After sending and receiving, clicking the link will resolve to http://domain.com/[readonline]
Click tracking is captured as per normal but the [readonline] doesnt seem to be replaced with the link to view it.
RenderTask is in place, is there anything else needs to be done?
Hi!
Have a look at the source code of the template, the link has to look like this
Sometimes the rich text editor prepends the domain which could be your issue.
/ m
Hi Markus
Thats exactly the markup used.
When sent (send now, not test), then opened in client link looks like this (shortened nid and e param. values):
http://domain.com/app_plugins/newsletterstudio/pages/tracking/trackclick.aspx?nid=9094072161203201211&e=521312131882121&url=http%3a%2f%2fdomain.com%2f%255Breadonline%255D
The rendertask is in place in config, yet it doesnt replace the [readonline] as seen. Clicking link brings to domain.com/[readonline]
There isnt any entry in logs either.
How can I ensure this works?
Whats the URL being replaced normally with [readonline] so I can counter check ?
Hi!
Have a look in the database ns_Newsletter table and the generated content of your email.
Sometimes things are added during saving.
Is there any errors etc. in the logs or trace-files?
I just tested this on a fresh Umbraco-install with Newsletter Studio 2.1.4 and it worked.
Hi Markus
I have checked the ns_Newsletter and there is nothing wrong there, the markup is exactly like given.
There is no error in the logs, the rendertask is there and other render tasks are working.
I am using 2.1.4 on 7.1.8 - everything else seems to be working. Just not the readonline rendertask.
What is the URL that I should be expecting to be replaced exactly? I believe the id is added somewhere but would like to know the URL that is supposed to be replaced so I can check further.
Is it possible to share the source code for this readonline render task, so i can add debugging/logging to see what is going on?
Hi again Markus
Did the order of execution or logic changed in latest 2.1.4 ?
I have been using the exact same newsletter.config in previous version 2.0/1, in the exact same order, and it was working as expected.
When i upgraded to 2.1.4, somehow the order of the render tasks needed to be updated otherwise the readonline was not working, as explained in OP.
When the render tasks are stacked one after another, it would be great if a "debug" flag can be set so the NS can log somewhere the render task X executed/called, maybe return/status code, and the order of execution can be diagnosed in similar cases.
Hi!
Yes there was a change at some point. Did you manage to solve your issues?
Hi Markus
I managed to solve only after changing the order.
Perhaps it should be noted for other users migrating to 2.4, to keep an eye on the order of render tasks and test it after upgrading.
is working on a reply...