Two problems with sending Newsletters
Standard member
1. The first problem I seem to be experiencing is with sending newsletters. I have Cron configured properly (10 minute intervals) as the notice to set up scheduling has now dispappeared from the Admin Checklist. Additionally, I have a usergroup with one user in it for testing purposes and I sent a news article as a newsletter. This appears to be 'partially' working as far as I can tell. I get the Preview copy almost immediately (to the sender email address) and my test account does 'eventually' receive the email but it took over 40 minutes to receive. I tried a second time by using the "Manage automatic issues" option for a one-off issue. Again, I got the the Preview copy almost immediately (to the sender email address) but it's been over an hour and my test account has yet to receive the newsletter. I have no idea where to even begin looking to debut this. Email from the server seems to be working, Cron seems properly configured...but receiving newsletters appers to be extremely sporadic if it is working (and I'm not competely sure about that). Any ideas where to start?
2) the second problem is with the Newsletter footer. At the bottom of the Newsletter this is what appears:
bad newsletter footer.jpg
(Click to enlarge)
Formatting and populating dynamic fields don't seem to be working properly. Any ideas how (or where) to fix this?
Thanks for the help!
Site director
I'm going to change the logic so that if a batch is not full it won't wait to do the next one.
2 - This is very odd.
Is WYSIWYG being used to edit the newsletter?
If not, are you attempting to do a full HTML newsletter, or just typing some plain text?
Where are you seeing this? E.g. on the preview screen in the web browser? In the preview email? In the final email?
What browser are you using?
Become a fan of Composr on Facebook or add me as a friend. Add me on on Mastodon. Follow me on Minds (where I am most active). Support me on Patreon
- If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
- If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
- If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
- If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.
Standard member
Chris Graham said
1 - It's the "Minutes between newsletter batches" setting. If you're testing a lot of newsletters, even to just yourself, that's still a batch, so it waits. The option (along with "E-mails per newsletter batch") are designed to avoid overwhelming a server and also avoid hitting email send limits.
I'm going to change the logic so that if a batch is not full it won't wait to do the next one.
That makes sense and sort of what I assumed, but wasn't sure…primarily because the sender receives the preview copy almost immediately, but the receiver takes a while (in this case there is only one recipient due to testing). So as far as I know there should only have been one entry in the batch…and it still took about 80 minutes to receive the email. So, it does definitely work, but seems to take longer than I would expect (a lot longer).
I am using the WYSIWYG editor and prefaced the generated newsletter with introductory text at the top of the newsletter. It is a full HTML newsletter, not just plain text.Chris Graham said
2 - This is very odd.
Is WYSIWYG being used to edit the newsletter?
If not, are you attempting to do a full HTML newsletter, or just typing some plain text?
Where are you seeing this? E.g. on the preview screen in the web browser? In the preview email? In the final email?
What browser are you using?
From “Post #7,233”, 24th October 2020, 10:56 pm
The screen capture I shared with you is what I see in the Newsletter Archive. The actual footer of the received newsletter looks like this:
I'm using the Vivaldi browser (i.e. Chrome).
Site director
and it still took about 80 minutes to receive the email
There are a few steps to the newsletter send flow…
- Create task] to fillup the send queue (immediate)
- Execute task via Cron hook (up to 10 mins on your Cron config)
- Execute Cron hook to do drip send (10 mins again)
- Wait until next drip send slot (up to 20 minutes on default config)
- Time for mail to get to your inbox (you said almost immediate, but maybe a couple of mins?)
That's 42 minutes. I can't explain 80 though.
I have optimised it a bit (0004454: Allow newsletter/mail queue filling and queue processing to happen in same Cron request - Composr CMS feature tracker).
I'll try and look at the main issue tomorrow.
Become a fan of Composr on Facebook or add me as a friend. Add me on on Mastodon. Follow me on Minds (where I am most active). Support me on Patreon
- If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
- If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
- If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
- If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.
Standard member
Chris Graham said
and it still took about 80 minutes to receive the email
There are a few steps to the newsletter send flow…
- Create task] to fillup the send queue (immediate)
- Execute task via Cron hook (up to 10 mins on your Cron config)
- Execute Cron hook to do drip send (10 mins again)
- Wait until next drip send slot (up to 20 minutes on default config)
- Time for mail to get to your inbox (you said almost immediate, but maybe a couple of mins?)
That's 42 minutes. I can't explain 80 though.
I have optimised it a bit (0004454: Allow newsletter/mail queue filling and queue processing to happen in same Cron request - Composr CMS feature tracker).
I'll try and look at the main issue tomorrow.
From “Post #7,246”, 25th October 2020, 3:09 am
Yeah, I can't explain 80 minutes either…but with the internet it isn't always easy to pinpoint performance issues (other than what is in our control)…such as what you're focusing on.
I'll definitely take a look at the hotfix you've made available and see if it helps. Thanks!
Site director
- https://gitlab.com/com…rces/comcode_compiler.php
- https://gitlab.com/com…er/lang/EN/newsletter.ini
- https://gitlab.com/com…ules/admin_newsletter.php
It should definitely fix the archive issue you had. I couldn't reproduce an issue with variable binding not working, but I wonder if it is caused by the same issue as your Comcode permissions issue and subject to my earlier fix.
If it's still not solved please let me know the exact HTML you are using (what the WYSIWYG has in its source), and also a full screenshot of the final email.
Become a fan of Composr on Facebook or add me as a friend. Add me on on Mastodon. Follow me on Minds (where I am most active). Support me on Patreon
- If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
- If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
- If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
- If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.
Standard member
Chris Graham said
See if putting these 3 updated files in place solves your newsletter issue:
- https://gitlab.com/com…rces/comcode_compiler.php
- https://gitlab.com/com…er/lang/EN/newsletter.ini
- https://gitlab.com/com…ules/admin_newsletter.php
It should definitely fix the archive issue you had. I couldn't reproduce an issue with variable binding not working, but I wonder if it is caused by the same issue as your Comcode permissions issue and subject to my earlier fix.
If it's still not solved please let me know the exact HTML you are using (what the WYSIWYG has in its source), and also a full screenshot of the final email.
From “Post #7,257”, 25th October 2020, 7:31 pm
Thanks Chris. I've installed these three files as requested and will do some testing tomorrow, and let you know how things go.
1 guest and 0 members have just viewed this.
