Posted by matthewboh on July 1, 2009 at 10:22pm
| Project: | Messaging |
| Version: | 6.x-2.x-dev |
| Component: | PHPMailer |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
There's no download files at https://sourceforge.net/projects/phpmailer/files/
Comments
#1
I think you're going to have to elaborate a bit. How is this a bug report? What are you talking about? :)
And anyway, I see a whole bunch of tarballs on that page.
#2
#3
#4
The README file says to use PHPMailer v2.0 but that version is for PHP4, is that still the recommended version or can we use the new v5?
#5
You can use v5. I am using 5.0.2. I'm running 6.x-2.x-dev and I don't see anything in the README specifying a version number. Hope that helps.
#6
Does that mean PHPMailer module 6.x-2.x-dev doesn't specify a particular PHPmailer version in the readme? Can you elaborate this please?
#7
Dane, the issue is with a Messaging error message on the Drupal status report page. The error message says:
"HTML Mail requires the PHP Mailer class to properly send HTML Mail. Please download the 2.0 version and place the phpmailer folder in your messaging_phpmailer module directory. Rename the folder to "PHPMailer".
Changed the Issue title and attaching screenshot
#8
Ah, we finally see an error message. Wonderful. Yes, this should be updated to mention v5. I don't have CVS permissions for Messaging so I shouldn't do it myself though.
Jose, PHPMailer changed their versioning system so that v2.x is only intended for use with PHP4. v5.x is nearly identical and completely compatible, but is intended for use with PHP5. We should update this error message so we're not pointing people to the old version.
#9
and so you are not pointing people to http://drupal.org/project/phpmailer
-.-
#10
I guess this part is answered here: http://drupal.org/node/541938 where you can also use libraries to store the PHPMailer class
#11
@Dane Powell, you have cvs access now to commit this or other bug fixes.
#12
This has been fixed in 2.x and 4.x
#13
Automatically closed -- issue fixed for 2 weeks with no activity.