Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
On some setups (like Windows, ehem) the checkdnsrr and getmxrr functions do not exist. So I've stuck in a function_exists on these.
Comment | File | Size | Author |
---|---|---|---|
email_verify.module.patch | 1019 bytes | Timotheos |
Comments
Comment #1
beginner CreditAttribution: beginner commentedConfirmed re. windows (use a proper OS!):
http://php.net/checkdnsrr
http://php.net/getmxrr
Anyway, wouldn't bypassing those two if statements seriously impair the functionality on windows servers?
Comment #2
Super_Regg CreditAttribution: Super_Regg commentedI install the email_verify module for version 4.6.11 and it does not verify the addresses mail and it does not let continue with the drupal registry, that variable I must change?
I update the module with all the information on the matter and already follows without working.
Comment #3
beginner CreditAttribution: beginner commented1) my first advice still applies. I recommend Debian Linux: the latest release is very nice.
2) Anyway, there is no patch attached: http://drupal.org/patch
3) Versions for D4.6 and D4.7 are unsupported.
Comment #4
beginner CreditAttribution: beginner commented4) There is no need to spam me about this issue by sending me an email via my contact page. I am subscribed to all issues anyway, and I'll help both if I have time and if I am able to.
Comment #5
beginner CreditAttribution: beginner commented5) Don't combine issues.
Comment #6
Timotheos CreditAttribution: Timotheos commentedYou can't impair a functionality that doesn't exist.
I'm now trying to upgrade to version 5.2 and I'm getting the following error.
Fatal error: Call to undefined function: getmxrr() in C:\Documents and Settings\My Documents\Web Sites\drupal-5.3\sites\testsite\modules\email_verify\email_verify.install on line 22
I think this is a great idea in the install file but you should also to a function exist here and throw false return to the watchdog. What do you think?
Comment #7
dbr CreditAttribution: dbr commentedThe php.net pages list alternative implementations for windows. What about using them in the module?
http://php.net/checkdnsrr
http://php.net/getmxrr
Comment #8
Timotheos CreditAttribution: Timotheos commentedYes that's interesting but it relies on the exec() function which also might be disabled on certain hosts.
Comment #9
brashquido CreditAttribution: brashquido commentedGuys, would it be possible to put a warning on the project page that this module is not compatible with Windows while a work around is looked at? Has anyone looked at using the Net DNS PEAR package instead which will be platform independent?
http://pear.php.net/package/Net_DNS
Comment #10
dbr CreditAttribution: dbr commentedApparently the upcoming PHP 5.3 on windows will support the necessary functions.
I applied the patch proposed in http://drupal.org/node/302503 which prints a warning when necessary, but avoids the failure.
Given the situation, I'll mark the issue as fixed (but I would accept a patch to make it work with earlier versions of PHP as well).