You need a db entry to remember notification format (text vs html). I use html in email notifications but the setting always reverts "text" and then all my emails looks like $hit. This has been going on since I started using Amilia almost a year ago. It's incredibly frustrating and makes my business look incompetent. Also, your latest update destroyed all my notifications and I didn't realize it until a week later. Have had to manually create all new ones. Very very bad. It's not a complicated fix. Just get it done.
Thanks for reaching out to us. Apologies in advance, yes, this has been an ongoing issue. Apparently, if you already have a notification text configured in Text Mode, there is an issue when changing to HTML mode and vice versa. We have added a small "warning" in the notification templates, but, of course, we are looking forward to fixing this in future updates.
The problem with that is that if you populate the html version, the app code will take part of it and populate the text version as well. And then whenever you click on "notifications" from the Amelia menu, all notifications have defaulted to the text version view and the html version is messed up.
When I had to recreate all the notifications after the most recent update, I ONLY created html versions. However, it started defaulting to text version and is populated with parts taken from the html version.
You need a db entry to remember notification format (text vs html). I use html in email notifications but the setting always reverts "text" and then all my emails looks like $hit. This has been going on since I started using Amilia almost a year ago. It's incredibly frustrating and makes my business look incompetent. Also, your latest update destroyed all my notifications and I didn't realize it until a week later. Have had to manually create all new ones. Very very bad. It's not a complicated fix. Just get it done.
Hi Alex,
Thanks for reaching out to us. Apologies in advance, yes, this has been an ongoing issue. Apparently, if you already have a notification text configured in Text Mode, there is an issue when changing to HTML mode and vice versa. We have added a small "warning" in the notification templates, but, of course, we are looking forward to fixing this in future updates.
Apologies for the inconvenience again.
Kind Regards,
Stefan Petrov
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables
The problem with that is that if you populate the html version, the app code will take part of it and populate the text version as well. And then whenever you click on "notifications" from the Amelia menu, all notifications have defaulted to the text version view and the html version is messed up.
When I had to recreate all the notifications after the most recent update, I ONLY created html versions. However, it started defaulting to text version and is populated with parts taken from the html version.
Hi Alex,
Yes, we are aware of this issue, that's why we added a note to inform the users. As said, it will be fixed in future updates.
Apologies for the inconvenience again.
Kind Regards,
Stefan Petrov
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables