Justin J <firstname.lastname@example.org>
Subject: Missing Tracker Reports: Fix
Date: May 18th 2012
I've been getting a lot of reports about the Tracker sometimes not showing all the reports for every Mass Mailing that goes out. The problems seems to be that it doesn't record the number of subscribers that are on the list, when a mass mailing goes out.
When the Tracker makes a list of all the reports to show, it uses this one metric to gather everything. Missing metric = missing report. Not good. I think the current version of Dada Mail fairs better at this, as there is a check to make sure that entry is in there, but for those lamenting reports of the past that seemingly are lost in the winds - fear not, as I whipped up a script that'll reveal the missing reports. It does so by simply adding back that missing metric (and setting it to, "0"). If you're running v5.x.x of Dada Mail, give it a spin:
I've attached a screen shot of the graph that gets produced in the Tracker after the script is run - every dip in it was a missing report about the Number of Subs I had on that mailing. Seems like I got bitten by the bug, as well.
Here's the docs:
Around v5.0.0 to v5.0.3 (the actually version this problem happens is fuzzy), there is/was a problem with the Tracker plugin, where it wouldn't successfully track the Number of Subscribers at the time of a mass mailing, or this metric wasn't being tracked, because of a user preference (Enable Subscriber Count Logging was unchecked).
Some related bugs:
This leads to a major problem, as Tracker uses this one metric to grab all the mass mailings that it shows in its reports. No "Number of Subscriber" report, no report for anything else.
tracker_add_missing_num_subs.cgi adds that missing entry into the database. You can get a preview of what this plugin will most likely achieve in the Tracker before running this script. In the Tracker Preferences, uncheck the option, Clean Up Tracker Reports. Your missing entries should now be shown, although other, "garbage" entries will probably also be shown, such as Test Mass Mailings.
Since the number of subscribers of a past mass mailing is unknown, it will simply add a new entry and record, 0 subscribers. (You may later manualy fix this in the SQL table, if you would like.).
This script also makes some assumptions, so not to make a new "Number of Subscribers" entry for every single thing in the Tracker Log:
• Doesn't already have a, "num_subscribers" entry Only mass mailings with missing "num_subscribers" entries will be looked at.
This also means that it's safe to re-run this script multiple times, if you find the desire to do so.
• Mass Mailings with an Archived Message but no, "num_subscribers" entry will be given one • Mass Mailings without an Archived Message and too few total Tracker entries will NOT be given a new "num_subscriber" entry
At the moment, this limit is a paltry, 5, and you may change this limit on the top of the script, in the variable,
This plugin also only works with any of the SQL backends, and does not work with the Default (plaintext logs) Backend.
No configuration will need to be done in this script itself. The permissions of this script simply need to be set to, 755.
Please fix backup the dada_mass_mailing_event_log table in your SQL database. Although this script will not remove any data from your database, it will potentially add data and add quite a bit data.
Visit tracker_add_missing_num_subs.cgi in your web browser, or run the script via the command line. Be aware that running the script may potentially take several minutes, depending on how many entries in the database you have, how many lists you have - things like that.
Once the script is finished, visit the Tracker plugin and see if the missing Message entries are now visible. The Tracker Summary graph itself will probably have some wildly changing entries, as the actual Subscribers data is not available.
Copyright (c) 1999 - 2012 Justin Simoni All rights reserved.
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
<< Previous: Auto-Adjusting Batch Settings for Amazon SES
| Archive Index |
Next: 5.1.0 rumblings >>
This mailing list is to discuss the nerdy programming development of Dada Mail -
If you are just looking for support Dada Mail, consult the message boards at:
To post to this list, send a message to:
All subscribers of this list may post to the list itself.
Some on topic... topics include:
At the moment, there aren't many people with CVS access for Dada Mail - if you would like CVS access, please first talk about the changes you propose and how it will affect the program. If the idea is sound and agreed upon, the change will be comitted. A good track record of this will allow you to have CVS access. Some reasons that patches will not be accepted is if the patch breaks compatibility with a previous version of the program, the patch is too centric to your own problem or the patch simply isn't very good.
Please, please please familiarize yourself with the documentation at:
Since no one wants to answer the same question twice.
Another sneaky reason for this mailing list is to test out the discussion list capabilities of Dada Mail, since Dada Mail is used for the mailing list itself.
NOTE - because of this, there may be times that this list will be somewhat broken. Although we're not planning on breaking the program by using it, we're giving you the heads up that this may well happen anyways.