Sorry, I replied too quickly. In this case it indicates an error in communicating with ws_server.pl, i.e. the SQL-Ledger interface. Check your web server logs.
those are notices, nor errors, but the html output they produce may break other things such as sessions,
in your php.ini file, turn off showing notices and turn on logging them,
I think enabling debugging probably means uncommenting some of the debugging code in /library/classes/WSWrapper.class.php. Sorry this is light on details but I’ve never had to do that before.
I really don’t like the way this XML-RPC stuff is implemented. It’s very user-unfriendly and should be reworked.
I have the showing errors off in php.ini and I have the logging on. I’m still getting the Invalid return payload errors. I’ll try to look at the WSWrapper.class.php file and see if I can comment out the debug details. I agree, I don’t like the xml-rpc stuff either…
ok that fixed it… I took out that last if statement on the fault codes… but if I ever get a different error, i won’t know about it :< I’ll have to re-enable it.
That doesn’t sound like a fix to me! You’re just masking the error.
I have a feeling you are not looking in the APACHE error log. Something like /var/log/apache2/error.log? The error is produced in a Perl app, not PHP. Very likely a missing module.
If you’re using sql-ledger 2.6.3 it probably due to that. I just upgraded to sql-ledger 2.6.3, implemented the ws_server_26.pl and now I get the error because of a missing element in the insert (chart_id value I believe). I’ll have to revert to 2.4.16 (I think) and try to see what’s missing in the call.
Note I’m only getting this error when I try to “generate and clear” everythig else seems fine. I get balances fine, add people fine with 2.6.3. Maybe you have another issue since you’re getting errors in the demographics section. Check to make sure you have the ws_server.pl set up correctly (mainly the directory location, the default value may be incorrect for your set up)