| Anonymous | Login | Signup for a new account | 02-09-10 21:58 GMT | ![]() |
| Main | My View | View Issues | Change Log | Roadmap |
| View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
| 0005521 | phplist | Message Send Process | public | 20-02-06 12:29 | 18-02-08 14:19 | ||||||
| Reporter | michiel | ||||||||||
| Priority | normal | Severity | minor | Reproducibility | always | ||||||
| Status | new | Resolution | open | ||||||||
| Platform | OS | OS Version | |||||||||
| Product Version | |||||||||||
| Target Version | 2.11.X | Fixed in Version | |||||||||
| Summary | 0005521: check on "doneusers" needs to use "status" column | ||||||||||
| Description | The check on "users who have received this message" checks for an entry in the usermessage table, but doesn't take the status into account, so it will also exclude users who haven't actually received the message. | ||||||||||
| Tags | No tags attached. | ||||||||||
| Attached Files | |||||||||||
Relationships |
|||||||||||
|
|||||||||||
Notes |
|
|
(0010857) michiel (administrator) 20-02-06 12:31 |
change query to $req = Sql_Query("select userid from {$tables["usermessage"]} where messageid = $messageid and status = \"sent\""); |
|
(0010858) michiel (administrator) 20-02-06 12:42 |
Hmm, it may not be as simple as that. When using RSS, and there is no content for the user to send, the status becomes "not sent" and if this is the case for at least one user in the total time of "frequency" (eg a day), the message would never be marked sent. So either RSS messages need a different code to be indentified, or it needs to stay like this. Situation: Using RSS message, user "last sent" data is after the time of sending the message. Therefore at sending a message time, there is no content for the user to send. The message will remain in the queue as being not done yet, but if the message is marked "sent" for the user instead (which is not true, but would help), the message is marked "sent" in total the next time the queue is run, as there will not be any more users, and therefore requeued for the next "frequency" time. |
| Copyright © 2000 - 2010 MantisBT Group |