Sorry for the silence lately. We have been busy at work on 1.1 the cron job has been a large point of support for a lot of people. We are going to be releasing a hosted cron solution to help. We are also going to be looking into a bypass for people who don’t want to schedule mailings. More to come. -Tom
Hi Tom, and thanks for the recent updates on your development plans.
I’d like to add my vote for the bypass solution, as the cron job seems to be causing real problems on my hosted server. In fact, it seems to be bringing the whole site down. I am getting “Internal Server Error 500” messages all the time. The support tech who restarted the system the first time mentioned that it was related to a cron job and that imap processes were over the top as well. And that was for a mailout to only 26 people.
The cron job was set to once every 15 minutes, while I was testing after the first installation, but I changed it to every hour after the first crash. Unfortunately, the server’s gone down again, so I think I am best off just forgetting completely about the cron job, at least for now.
Scheduling does sound a good option to have, but for me it’s not absolutely essential. I really do need the server up and running, though, so if we can have the option to bypass the cron job completely and just send directlly (just like through the normal Comnunicate module (which I’ve never had any problems with), then that’s just fine by me. I’m afraid that, unfortunately, I just don’t trust that cron job any more.
Thanks for listening, and I look forward to the improvements in 1.1
Andrew Macpherson Sydney, Australia
So 1.1 is now out I see but have to say hugely disappointed to see that the hosted cron option or an alternative “send now” has not been implemented.
At present this product while great if it works (which in fairness it does for a lot it would seem) relies on a cron script which would appear to be less robust than it possibly could be. Our server is far from an unusual set up and we would seem to be not the only ones with “issues”.
A timescale on the hosted cron or bypass would be appreciated as we need to make some decisions.
Thanks….
Hi Jack,
We’re about to deploy our first site which will be using Boomerang 1.1 for it’s email marketing. We are struggling however with getting the cron PHP to work. After going through cron_me.php I found a reference to “/index.php/?ACT=37” which, when I load this using the web browser, sends everything sitting in my mail queue.
So I’m interested if you know of any modifications I might be able to make to be able to call “/index.php/?ACT=37” from a cron job and whether this is a good idea given that cron_me.php isn’t firing for us.
For what its worth, we’re running on CentOS, PHP5 with Safemode Off.
Cheers. Sam
I would strongly encourage you not to make a cron call to index.php/?ACT=37. The idea behind the cron is to check and make sure we currently don’t have a connection open to the action id.
We are hoping to have an update out later this week, that will provide some updates and alternatives to the cron. (Aiming for Friday)
Boomerang 1.1.1 is now available. Here is a snap shot of what has changed.
* FEATURE: Email sends without cron if delay send is not chosen
* FEATURE: Alternative cron URL added
* ENHANCEMENT: TinyMCE now supports more HTML tags
* BUG FIX: Removed slashes in edit template view, after save
* BUG FIX: Fixed issue people were having with TinyMCE not loading
If using the Alternative cron URL, we don’t recommend having the cron job set to less-then 15min intervals.
-Tom
Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.