Fixed bug in cancelling scheduled send - If campaign was scheduled to be sent, a checkbox was still shown on the campaign status page. This gave wrong impression that by unchecking the checkbox, the scheduling is cancelled. Checkbox is removed now and the "Pause" button has be renamed to "Cancel scheduling"
Added default role for campaign admin that administer multiple namespaces.
ERR! Senders Sending message to 4:1 failed with error: shortid is not defined. Dropping the message.
verb ReferenceError: shortid is not defined
at html.replace (/home/mailtrain2/mailtrain/server/lib/message-sender.js:236:29)
at String.replace (<anonymous>)
at MessageSender._getMessage (/home/mailtrain2/mailtrain/server/lib/message-sender.js:235:25)
at MessageSender._sendMessage (/home/mailtrain2/mailtrain/server/lib/message-sender.js:345:34)
Campaigns list is now by default ordered by 'Created' in descending order.
Fixed display bug - two clicks on main menu item made it disappear
Campaign Status is now protected by 'view' permission. (Up till now it was 'viewStats' permission.)
Fixes in campaign status to hide send buttons and test send button if a user does not have necessary permissions.
Templates, Mosaico templates and Campaigns (edit and content) are now displayed to user even if the user does have only 'view' permission (not 'edit'). A banner is displayed that the user cannot save any changes and buttons are removed from the edit pages. This is to allow users to copy settings and content from existing campaigns which they are not supposed to edit. A better solution would be to display the edit and content form in read-only mode, but this seems to be a bit complicated.
- Removed node_modules from client after compilation
- Added copy-webpack-plugin to copy required JS and fonts to dist
- Adjusted server to serve files from client/dist
- add js-yaml to server packages in order to use npm install --production
This fixes that triggered campaign e-mails are not reported in ui and so it's also possible to
create another triggered campaign on this first triggered one.
What i don't understand why their is a difference in handling of a triggered campaign and a normal one in sending.
Also i expected that a triggered campaign can only be send once to an user regardless which trigger fires the send.
But currently it's send for every trigger that is defined in a campaign.
