I'm sending Newsletter from the content section and have configured a default sender name and email but these values are not set when creating a new newsletter content. Also after save and publish, the default values are not set correctly.
Strangely, also no draft newsletter is created when i create a new content newsletter. Because if i create a draft email directly, the default values are set correctly.
Any idea if this is a bug or if i need configure something additional?
The issue was that, after upgrading NewsletterStudio, the attribute activateCssInliner="true" was still in the newsletterStudio.config. This threw an exception when reading the file and the config was nod loaded properly.
After deleting the attribute, everything works fine.
How do you mean? That line should work in 2.1.7? Did you downgrade back to an old version? Or did you overwrite the new binaries with old once after the upgrade?
Default sender name not set
Hi,
I'm sending Newsletter from the content section and have configured a default sender name and email but these values are not set when creating a new newsletter content. Also after save and publish, the default values are not set correctly.
Strangely, also no draft newsletter is created when i create a new content newsletter. Because if i create a draft email directly, the default values are set correctly.
Any idea if this is a bug or if i need configure something additional?
I'm using the newest Newsletter Studio (v2.1.7).
Thanks
Severin
Hi!
This is actually a bug as far as I know. Just need to delete the email and recreate it.
Cheers
// m
Hi,
The issue was that, after upgrading NewsletterStudio, the attribute activateCssInliner="true" was still in the newsletterStudio.config. This threw an exception when reading the file and the config was nod loaded properly.
After deleting the attribute, everything works fine.
Cheers
Severin
Hi!
How do you mean? That line should work in 2.1.7? Did you downgrade back to an old version? Or did you overwrite the new binaries with old once after the upgrade?
Hi,
just saw that i have overwritten the binaries with the v2.1.4 ones. Replaced them with the v2.1.7 ones and all works fine.
Cheers
Severin
Yepp, that attribute was not present in 2.1.4 so that explains why you had the problem.
Thanks for letting us know.
is working on a reply...