Hi All,

Running SuSE 10

PHP apache MySQL etc Compiled from source and are latest versions available.

Everything working fine apart from this OLD module that I need to run and plugin to PHP but because its been compiled against an old version of PHP's module API... it won't allow it to start.

Is this going to be impossible to get running without downgrading PHP to the required version? OR is there a switch that might help e.g. which turns off the checking of the modules compiled API version number? (if that would be enough to do it)

Warning: PHP Startup: XXXXXXX: Unable to initialize module
Module compiled with module API=20060613
PHP compiled with module API=20090626
These options need to match
in Unknown on line 0

Module is for PHP 5.2.0 and there's nothing else available to replace it (no newer module available). I'm running PHP 5.3.3 which of course is the latest version. Is there a way to get the module talking nicely with PHP? However all I have is the compiled XXXXX.so file, I don't have the code to re-build the module for the version of PHP.

Any ideas from anyone?
Thanks all

And just WHAT is this secret module w/o source? :}

This:
catches my eye. If you compiled it once, why can't you compile it again, against the new PHP??

Didn't say HE compiled it ;}

I have a suspicion (just googling for the exact error message he
posted) that it may have to do w/ MS-SQL ...


Cheers,
Tink

HI Guys,

Thanks for the replies. No not something i've compiled, its provided by a 3rd party (payment gateway) which basically doesn't seem to be keeping up the module to the latest releases of PHP any more. For quick turn around we're mainly a PHP shop and I wondered if its possible to bypass the problem whilst still possibly using the latest PHP version and the module supports upto version 5.2.0.

So i've come up with a separate idea how to get round the issue but keep my servers on the latest PHP versions etc. I've just installed PHP 5.2.0 CLI ONLY and added the module into the php.ini for that version of PHP and it all works fine. Code on the Latest PHP version running on apache will be able to make a call to this older version of PHP and this module. Thus i think my problem for the short term is solved and longer term there's other ideas in the pipeline to solve completely which isn't PHP based.

PS- Yes I saw people having problem with MySQL but it wasn't exactly the same problem compared to this, those are more that they've upgraded and the MySQL mod didn't update as well or so on. They weren't looking to find out if its possible to bypass PHP's built in check that causes this stuff to not allow the module to be attached/initialised. There doesn't seem to be a "force" type parameter that will mean it should just try and work and see how to go on from there.

Thanks anyway,
Best Regards,
M