Can you confirm any Auto responder plans?
There are definitely plans. It’s not the next up major feature, but it’s in the works. Check out the Feature Request Poll to see where things are headed and throw in your 2 cents!
Thank you for adding a cron bypass, I can confirm that the module is now all we wanted it to be so thank you and congratulations on an awesome product taking on board suggestions and implementing requirements.
Glad you’re happy! No small thanks to Tom Jaeger on this one though, he’s the real brawn behind the module, I’m mostly just the voice and the usability/interface/small things guy 😊
I feel like I’m the only one that doesn’t have a clue how to use this module. How do the templates work? I feel like I’m missing the instructions. When I try to create a new email from a template and send a test email, nothing from the template comes through. I feel like an idiot. I must be missing something somewhere.
I feel like I’m the only one that doesn’t have a clue how to use this module. How do the templates work? I feel like I’m missing the instructions. When I try to create a new email from a template and send a test email, nothing from the template comes through. I feel like an idiot. I must be missing something somewhere.
Are you using EE tags in your template? If so, did you set a blank/dummy EE template in the config area?
As far as Boomerang templates go, you simply just write/paste your HTML into the proper area when creating a new template. Then, you choose which template you want to use when creating an email. You can then edit that template’s content if it’s static, or if you’re pulling in EE tags, the output of said tags becomes static at that point so you can edit/modify/add to it.
Does that make sense? Are you doing something different?
Okay, now that I have the templates working with standard templates, I’m really seeing the potential uses for this going forward. I’m very excited about using this in the near future with a client.
One request I would have which would make it much easier to use would be to store each template in its own file so that we could use external text editors to modify templates just like standard EE templates.
One request I would have which would make it much easier to use would be to store each template in its own file so that we could use external text editors to modify templates just like standard EE templates.
Glad you got it worked out. Noted on the external file, we’ll put that in the “Draft Pool” of future features. Thanks!
thanks a lot for this wonderful module! working out of the box!
anyways. I see a small bug: when I don’t specify a text based newsletter the subject is not beeing filled out. and I can’t see statistics, cause there’s no title to click on… that’s when I put no text or whatsoever in the Text Version field…
and a few questions (sorry): is there a way to generate an automatic Text version of the email? like a second template or something. I might be missing something very obvious. sorry, I’ve only been using this module for the past hours…
and what should I specify as doctype? are html emails MIME endoced? I can’t seem to find any information?
will I be able to use solspace’s user module in conjunction with boomerang aswell? and, can I send emails to user_groups instead of newsletter lists??
and some feature requests: I would like to give the user an option to change his email address… it this hard to implement? or should we wait for an EE native solution? the upload thing is ok, but it would need some love… this is not as user friendly as it could be…
great work! dammit! stefan
thanks a lot for this wonderful module! working out of the box!
Thanks!
when I don’t specify a text based newsletter the subject is not beeing filled out. and I can’t see statistics, cause there’s no title to click on… that’s when I put no text or whatsoever in the Text Version field…
Not sure what you’re saying here. You need to send both an html and text version of your email for maximum deliverability. If someone is receiving that text email, however, you won’t get full stats on it as there’s no HTML. You won’t get open rates or (i believe) click rates either. What exactly are you referring to when you mention “There’s no title to click on…”?
is there a way to generate an automatic Text version of the email?
Unfortunately no one’s been able to perfect taking an html email with images and conveying the same message with plain text. You can copy and paste the output of your html’s text for a start, but if you want to make sure you’re hitting the full impact, you should really tailor every email. We can, however, look at making the text version optional for those who don’t want to mess with it.
and what should I specify as doctype?
HTML emails shouldn’t contain a doctype, they should start with <body>. CSS should really be all inline for maximum compatibility across email clients. Check out http://campaignmonitor.com/css for some tips.
are html emails MIME endoced? I can’t seem to find any information?
This is taken care of automatically, with properly formatted email headers.
will I be able to use solspace’s user module in conjunction with boomerang aswell?
Not at this time. We’re planning a partner module for personalization of emails.
and, can I send emails to user_groups instead of newsletter lists??
Soon!
I would like to give the user an option to change his email address… it this hard to implement? or should we wait for an EE native solution?
This is currently limited to native ExpressionEngine controls as it uses the built-in Mailing List module.
All the best! Hope the answers helped.
Have created my Boomerang template but something is inserting Fieldframe code…
[removed]FT_URL = "http://www.removed.org.uk/system/extensions/fieldtypes/";[removed]…and
[removed][removed]
[removed][removed]
[removed][removed]
[removed][removed]These all carry through to the New Email screen as well.
Have created my Boomerang template but something is inserting Fieldframe code…
We noticed this too and have requested support from Brandon Kelly several times and have had no help thus far. We’re working on it on our end, so we’ll post a fix or release an update when we figure out why his extension is invading our module.
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.