Problems with parsing XML (Cardia) after moving to a new server

[Guest]

Hiya.

 

I posted this under General Support first, but I see now that I should have posted this in Installation and configuration.

 

So here goes ...

 

We just moved a fully functional webshop from one server to our new RHEL 4 server.

Now we are experiencing some problems with getting the cardia module (cardia.omnimedia.no/cardia-install-osC2.2.html) to parse some XML data properly. We are running the latest pcre and curl libraries for RHEL 4.

 

So as to try to find out what exactly is failing, I'm trying now to figure out what the cardia.class.php file does. I see this switch statement:

 

CODE

 

switch( $this->_getVar( 'responseCode' ) ) {

...

case 1:

// Status Code 1 means OK, but we need the default-case to trap unknown errors

break;

 

default:

// This should never happen, but you never now;) //DOH! This is ofcourse what happens!

return $this->_addError( 'Remote or Local', 'An unknown Response was received: "'.htmlentities($this->response).'"' );

break;

}

 

 

 

This should return an integer but it returns undef which leads me to think that somewhere this XML is not parsed correctly.

If I can see exactly which method is doing the XML parsing I could either:

a) Fix it.

B) Reinstall it.

 

But since I don't know which method is doing this, it gets hard. I'm guessing anyway that the method will use libraries given by pcre (pcre-4.5-3.2.RHEL4) or curl.

 

Our server configuration:

OS: RHEL 4

PHP packages:

php-gd-4.3.9-3.9

php-pear-4.3.9-3.9

php-debuginfo-4.3.9-3.1

php-mysql-4.3.9-3.9

php-devel-4.3.9-3.9

php-ldap-4.3.9-3.9

php-4.3.9-3.9

php-domxml-4.3.9-3.9

pcre-4.5-3.2

curl-7.12.1-8.rhel4

 

 

I'm guessing the culprit is either curl or pcre but reinstall this for another release like CentOs has not helped at all.

 

Any hints or tips are greatly appreciated :)

[♥Vger]

but I see now that I should have posted this in Installation and configuration.

 

Nope! Shouldn't have posted it here either. Sorry ...this is a server problem and not an osCommerce problem.

 

Vger