Gabe Lebron
asked on
Installing php_mailparse On IIS
Hello I am not a huge PHP guy. I Am running server 2003 with II6 and PHP 5.2.9 I need Mailparse.dll installed
I downloaded the php_mailparse.dll and put in the ext file
I also have good in my ini file
; Windows Extensions
; Note that ODBC support is built in, so no dll is needed for it.
; Note that many DLL files are located in the extensions/ (PHP 4) ext/ (PHP 5)
; extension folders as well as the separate PECL DLL download (PHP 5).
; Be sure to appropriately set the extension_dir directive.
extension=php_mbstring.dll
extension=php_mailparse.dl l
;extension=php_bz2.dll
;extension=php_curl.dll
;extension=php_dba.dll
;extension=php_dbase.dll
;extension=php_exif.dll
;extension=php_fdf.dll
;extension=php_filepro.dl
not sure what i am missing maybe the file isnt compatable? not sure what error PHP Warning: PHP Startup: Unable to load dynamic library './php_mailparse.dll' - The specified module could not be found. in Unknown on line 0
means
I did these commands
1. Go to http://pecl4win.php.net/ext.php/php_mailparse.dll and download the version of the dll that goes with your PHP version.
2. Place the dll into your php/ext directory.
3. Open your php.ini and adda line under the extension=php_mbstring called extension=php_mailparse. Make sure that both of these lines do not have the ; preceding them.
4. remove the ; in front of the extension=php_imap.dll
5. Save your changes in the php.ini file
6. Restart IIS
But the link in 1 is broken.. i had to find another dll could that be the issue i am running 5.2.9 php where can i find a good dll?
if thats the issue
I downloaded the php_mailparse.dll and put in the ext file
I also have good in my ini file
; Windows Extensions
; Note that ODBC support is built in, so no dll is needed for it.
; Note that many DLL files are located in the extensions/ (PHP 4) ext/ (PHP 5)
; extension folders as well as the separate PECL DLL download (PHP 5).
; Be sure to appropriately set the extension_dir directive.
extension=php_mbstring.dll
extension=php_mailparse.dl
;extension=php_bz2.dll
;extension=php_curl.dll
;extension=php_dba.dll
;extension=php_dbase.dll
;extension=php_exif.dll
;extension=php_fdf.dll
;extension=php_filepro.dl
not sure what i am missing maybe the file isnt compatable? not sure what error PHP Warning: PHP Startup: Unable to load dynamic library './php_mailparse.dll' - The specified module could not be found. in Unknown on line 0
means
I did these commands
1. Go to http://pecl4win.php.net/ext.php/php_mailparse.dll and download the version of the dll that goes with your PHP version.
2. Place the dll into your php/ext directory.
3. Open your php.ini and adda line under the extension=php_mbstring called extension=php_mailparse. Make sure that both of these lines do not have the ; preceding them.
4. remove the ; in front of the extension=php_imap.dll
5. Save your changes in the php.ini file
6. Restart IIS
But the link in 1 is broken.. i had to find another dll could that be the issue i am running 5.2.9 php where can i find a good dll?
if thats the issue
The pecl4win site is offline and has been for a while. As a windows+PHP developer, the lack of the pecl4win archive is a PITA.
I don't know what the issues are (I've just asked and will update you when I get a response).
But for each extension, at least 20 builds would need to be performed (VC6/VC9, ts/nts, PHP5.0/PHP5.1/PHP5.2/PHP5. 3/PHP6.0). If debug builds are also required, then this becomes 40 builds per extension.
There are currently 220 PECL packages, so that (WCS) is 8,800 builds.
Not an insignificant task. And then what frequency? Daily/Weekly?
You may also have to deal with different versions of the extension.
So, not really an answer, just some info.
If/when I get a response from the PHP Group, I'll let you know.
Regards,
Richard Quadling.
I don't know what the issues are (I've just asked and will update you when I get a response).
But for each extension, at least 20 builds would need to be performed (VC6/VC9, ts/nts, PHP5.0/PHP5.1/PHP5.2/PHP5.
There are currently 220 PECL packages, so that (WCS) is 8,800 builds.
Not an insignificant task. And then what frequency? Daily/Weekly?
You may also have to deal with different versions of the extension.
So, not really an answer, just some info.
If/when I get a response from the PHP Group, I'll let you know.
Regards,
Richard Quadling.
http://web.archive.org/web/20070702121530sa_/pecl4win.php.net/ext.php/php_mailparse.dll is the only place I could find a prebuilt php_mailparse.dll
I'm afraid you are out of luck.
About 10 hours ago, this was committed to the PHP documentation ...
Log:
Removed references to pecl4win as it died. And updated information with
the current status, which is: We do not offer Windows binaries for PECL
extensions. In the future pecl.php.net will offer such downloads.
and
+ At this time the PHP project does not compile Windows binaries for
+ PECL extensions. However, to compile PHP under Windows see the
+ chapter titled
+ <link linkend="install.windows.b uilding">b uilding PHP for Windows</link>.
So, unless you have good quality C skills and a MS C compiler you are going to have problems.
In just reading through the PECL newsgroup regarding this issue. It seems to be repeated again and again.
About 10 hours ago, this was committed to the PHP documentation ...
Log:
Removed references to pecl4win as it died. And updated information with
the current status, which is: We do not offer Windows binaries for PECL
extensions. In the future pecl.php.net will offer such downloads.
and
+ At this time the PHP project does not compile Windows binaries for
+ PECL extensions. However, to compile PHP under Windows see the
+ chapter titled
+ <link linkend="install.windows.b
So, unless you have good quality C skills and a MS C compiler you are going to have problems.
In just reading through the PECL newsgroup regarding this issue. It seems to be repeated again and again.
It seems the issue is that PECL do not version their extensions. So when you build an extension today, the code may be different tomorrow, so which version is the right one?
Over 200 extensions, each with their own "version" and using external libraries which also have versions and the mess is massive and not going to be fixed any time soon it seems.
Over 200 extensions, each with their own "version" and using external libraries which also have versions and the mess is massive and not going to be fixed any time soon it seems.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER