Active
Project:
Mass Mailer
Version:
master
Component:
Code - PHPlist engine
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
28 Mar 2006 at 23:44 UTC
Updated:
20 Jul 2006 at 20:09 UTC
Jump to comment: Most recent file
Comments
Comment #1
robin monks commentedproject.module ate my attachment...
Robin
Comment #2
killes@www.drop.org commentedThe patch is quite unclean and also not against the most recent version of phplist.module. Can I assume that the important changes are in phplist_process_queue? Any other changes that matter?
Comment #3
killes@www.drop.org commentedI've cleaned the patch a bit. There are several places where I disagree with the patch.
-// Drupal sends mails in 8bit mode
-define('TEXTEMAIL_ENCODING','8bit');
-
-// We use PHPmailer for sending.
-define("PHPMAILER",1);
-
@@ -780,7 +780,7 @@ function phplist_send_mail($lids, $mid,
Comment #4
Amazon commentedRobin, could looking into cleaning up the config file.
patch -p0 -u < ../../massmailer_without_cli.patch.txt
patching file engines/phplist/config.php
Hunk #1 FAILED at 74.
1 out of 2 hunks FAILED -- saving rejects to file engines/phplist/config.php.rej
patching file engines/phplist/phplist.module
Comment #5
pauln600 commentedThis patch also needs changes to PHPlist... more to come.
Paul N.
Comment #6
robin monks commentedI just tested the attached patch to work on a new CivicSpace install. There was a small error which Paul Newby found and I corrected in this illiteration.
Robin
Comment #7
robin monks commentedGerhard, what changes will be needed before you commit this patch?
Robin
Comment #8
killes@www.drop.org commentedRobin, why are these changes in the patch?
-// Drupal sends mails in 8bit mode
-define('TEXTEMAIL_ENCODING','8bit');
-
-// We use PHPmailer for sending.
-define("PHPMAILER",1);
-
Paul said he didn't make them.
Comment #9
killes@www.drop.org commentedapplied the patch minus the parts that didn't belong there. Awaiting sql changes.
Comment #10
killes@www.drop.org commentedmanual processing of the mail queue seems to log users out.
Comment #11
pauln600 commentedI'm not quite sure what you mean - manual being via the phplist admin interface directly?
Paul N.
Comment #12
killes@www.drop.org commentedmanual through the link we present in the Drupal admin menu.
Comment #13
pauln600 commentedAfter you run it, you need to log back in to Drupal?
Paul N.
Comment #14
killes@www.drop.org commentedyes
Comment #15
pauln600 commentedHm, I'm not seeing that in my install... anyone else?
The session handler is switched to 'files' in phplist config.php. What's the session handler set to in your drupal site settings.php?
Paul N.
Comment #16
killes@www.drop.org commented"user" as Drupal requires. It is possible my install is borked. But if phplist changes sets the session handler to files then problems are almost guaranteed.
Comment #17
pauln600 commentedPlease explain.
Paul N.
Comment #18
killes@www.drop.org commentedDrupal calls several session function during a page request. All these functions assume that the cookie information is stored in our database (this is what session handler = user means to us) so if they can't find the info because the sessionhandler changed, I expect problems.
Comment #19
pauln600 commentedPHPlist switches the session handler to 'files' and exits on completion. Since any session data in PHPlist would be saved in the filesystem, it shouldn't interfere with the Drupal session data.
Comment #20
pauln600 commented... also the PHPlist session_start fails because it's preceded by the Drupal session. If it didn't, we would need to disable it to prevent subsequent PHPlist admin access without login.
Pau N.
Comment #21
datura-1 commentedTake a look at this code:
What's happening is that the CURL is trying to access a page that drupal cannot find and returns that to the browser. Since it is CURL accessing the page, and the CURL user is not logged in to drupal, you see "Page not found" and it looks like you're not logged in. But really it is CURL that is not logged in.
The real issue is that the URL that CURL is trying to fetch is not a valid path...I'm digging into that part now.
Considering I haven't yet seen this thing work, any words of encouragement that this is a worthwhile endeavor would be greatly appreciated ;-)
Comment #22
dalinI've managed to get everything except unsubscribe working. Take a look at these issues:
http://drupal.org/node/60205
http://drupal.org/node/61766