phplist

NOTE:: Before reporting an issue, make sure you are running the latest version, currently 3.3.1


View Issue Details Jump to Notes ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0016796phplist applicationInterface - Administratorpublic29-05-13 16:3503-06-13 20:09
Reportermichiel 
PrioritynormalSeverityminorReproducibilityalways
StatusresolvedResolutionfixed 
PlatformOSOS Version
Product Version2.11.9 
Target Version2.11.11Fixed in Version2.11.11 
Summary0016796: Review statistics exactness
DescriptionSplitting out the statistics issue from 0016788


Issue is, statistics include "not sent" entries, and are therefore incorrect


TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to 0016788new phpList plugins Not able to send a message to subscribers who previously were excluded 
related to 0006499resolvedmichiel phplist application subtract bounces to calculate percentages 
has duplicate 0014253resolvedmichiel phplist application clicktracking totals: sent msgs is calculated wrong (especially for RSS msgs) 

-  Notes
(0052053)
michiel (manager)
29-05-13 16:39


Hi Duncan
(made you developer, so I can assign things to you :-)

Can you specify the Statistics being wrong? The statistics overview page does an SQL Query that includes

um.status = "sent"

which afaict should ensure that "not sent" entries are excluded from the calculations.
(0052054)
duncanc (developer)
29-05-13 18:31

The View Opens page, http://strontian/lists2.11.9/admin/?page=mviews, [^] includes the 'not sent' rows from the usermessage table.
The sql has a count(status) to get the number of messages sent to the user.

The Find Subscribers page, http://strontian/lists2.11.9/admin/?page=users, [^] includes 'not sent' in the total of messages sent to each user.
The sql has a count(*) to get the number of messages sent to the user.

There might be others, but I haven't looked closely as it seems to be a retrograde step to introduce the new value of 'not sent' for the status column. Up until now a row in usermessage means that the message was sent to the user.
(0052055)
michiel (manager)
29-05-13 21:43

great, thanks, I'll look into it.

I think it's preferable to use the status column, as I intend to use the table for more stuff, eg, there is already the PREPARE_QUEUE, which marks them as "todo", so that the sending can be done by multiple processes.
(0052071)
michiel (manager)
31-05-13 14:47

have added 'and status = "sent"' to all relevant queries


Copyright © 2000 - 2017 MantisBT Team
Powered by Mantis Bugtracker