Please attach a small example script, thank you.

Hi.
I work with symfony 2 and i use symfony-rpc-bundle (https://github.com/skolodyazhnyy/symfony-rpc-bundle). In my file you can see that i call the export_response method with 'call' function. After this call i have an 'The XML document has not valid XML-RPC content' error ( you can see this error in https://github.com/skolodyazhnyy/symfony-rpc-bundle/blob/master/XmlRpc/Implementation.php).
Actually i must add tag in BigDate.php file in xmlrpc_echo_stream function like this :

    protected static function xmlrpc_echo_stream($data)
    {
        echo "<base64>";
        $data->render();
        echo "</base64>";
    }

Thanks a lot for your response.

The function does not advertise to give back base64 but a simple string, which happens to be base64, but that should not be the problem.
Do you state somewhere in your client that base64 is expected?

I see that in the XML_RPC response the type is not advertised.
The XML-RPC specs says though:

"If no type is indicated, the type is string."

I assume that your XML-RPC client is not behaving properly.

Yes, a simple string but encoded in base64 like an encoded file.
When the tags are specified , the rpcbundle can decode in base64 and i can read the limesurvey response.
In first you can see the decoding processus in https://github.com/skolodyazhnyy/symfony-rpc-bundle/blob/master/XmlRpc/Implementation.php (line 229).
Then you can see the real decoding in https://github.com/skolodyazhnyy/symfony-rpc-bundle/blob/master/XmlRpc/ValueType/BlobType.php (line 34)

Thanks a lot.

Fix committed to master branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=14665

Implemented a small fix to indicate the type explicitly as string.

Fix committed to 2.06 branch: http://bugs.limesurvey.org/plugin.php?page=Source/view&id=14666

I have to force it to string, as it would break existing integrations, otherwise.
You will have to decode the base64 in your application separately (which should not be much of a problem)

Thanks a lot.

It works!

Best regards.

For The XML-RPC specs

I will suggest this specs to the bundle devlopper.

Thanks again.

Hi!

I am using the JSON-RPC interface and this change broke my code.
Suddenly a '<string>' is added to the front of the response and '</string>' is added to the back.

base64_decode fails on this.

It is not documented to do so. So why change this?
We are customers of "Limeservice", having currently 4-6 Surveys open and rely on a stable environment. Please don't fix things that are not broken, according to the documentation.

Can you explain this to me?

Thanks.

PS:Otherwise Limesurvey is great.

alibert, it is a valid response, as I wrote before the XML-RPC specs say "If no type is indicated, the type is string." So I just added something that can or cannot be there according to specs.

If your XML-RPC client is not properly implemented then yes, stuff will break. But it is not to blame on LimeSurvey.

Hi alibert and C schmitz.
I asked the xml-rpc symfony bundle developer for these changes and i hope receive a positive response. Then if these tags make problems, you can delete them.

Version 2.05+ Build 141210 released