controllers/admin/RemoteControl.php:     * @var Zend_XmlRpc_Server
controllers/admin/RemoteControl.php:                require_once('Zend/XmlRpc/Server.php');
controllers/admin/RemoteControl.php:                require_once('Zend/XmlRpc/Server/Exception.php');
controllers/admin/RemoteControl.php:                require_once('Zend/XmlRpc/Value/Exception.php');
controllers/admin/RemoteControl.php:                $this->xmlrpc = new Zend_XmlRpc_Server();
controllers/admin/RemoteControl.php:                Yii::import('application.libraries.LSZend_XmlRpc_Response_Http');
controllers/admin/RemoteControl.php:                $this->xmlrpc->setResponseClass('LSZend_XmlRpc_Response_Http');
controllers/admin/RemoteControl.php:                if ($result instanceof LSZend_XmlRpc_Response_Http) {
controllers/admin/RemoteControl.php:                    // a Zend_XmlRpc_Server_Fault with exception message from XMLRPC
controllers/admin/RemoteControl.php:                require_once('Zend/XmlRpc/Client.php');
controllers/admin/RemoteControl.php:                $client = new Zend_XmlRpc_Client($serverUrl);
libraries/LSZend_XmlRpc_Response_Http.php:class LSZend_XmlRpc_Response_Http extends Zend_XmlRpc_Response_Http

For dev : https://github.com/gggeek/phpxmlrpc ?

For master : delete whole Zen except RPC (and related) ? Or move to https://github.com/laminas/laminas-xmlrpc ?

Wait for https://github.com/LimeSurvey/LimeSurvey/pull/3962 to touch vendor

If we just removed the xmlrpc then users code based on it would be broken, so i would definitely prefer to replace it with a new xmlrpc.
I am not sure how much needs to be updated for it to work, but the previous one seemed lightweight in the usage.

If we just removed the xmlrpc then users code based on it would be broken, so i would definitely prefer to replace it with a new xmlrpc.

Yes i know

I am not sure how much needs to be updated for it to work, but the previous one seemed lightweight in the usage.

Issue with https://github.com/zendframework/zend-xmlrpc : This repository has been archived by the owner on Apr 28, 2020. It is now read-only.
Issue with https://github.com/laminas/laminas-xmlrpc : no php7.4 support : "php": "~8.1.0 || ~8.2.0 || ~8.3.0",

Then : try https://github.com/gggeek/phpxmlrpc/blob/master/composer.json in vendor "php": "^5.4.0 || ^7.0 || ^8.0", (reason why i wait for vendor update currently)

https://bugs.limesurvey.org/view.php?id=19685 was merged into master, any progress on this ticket?

Can you find another dev for this ?
I really think i don't find a good way (or wait a lot lot lot of time …)

Thank you

https://github.com/LimeSurvey/LimeSurvey/pull/3985

I encountered compatibility issues with Zend Framework 1 (ZF1) when using newer PHP versions.
After some investigation, I found the following solutions:

Original Source (zendframework/zf1):
The original ZF1 project reached its end-of-life in 2016. The repository contains a conversion of the ZF1 subversion repo to Git, starting from version 15234 onward. However, Lime (another context) seems to use only a subset of the library/Zend files from this repository.

ZF1 Future (Shardj’s Fork):
I discovered a fork called “ZF1 Future” on GitHub, maintained by Shardj. This fork aims to create a PHP 8.1-compatible version of ZF1.
While it almost worked for me, I still had to apply a manual fix.
If you’re interested, consider contributing by submitting a pull request (PR) to the “ZF1 Future” repository. The last update was about two weeks ago.

Testing and Compatibility:
I tested the solution with the RemoteControl controller. Interestingly, it failed in the same place as it did with PHP 7.4.
So no new issues introduced here.

If you’re interested, consider contributing by submitting a pull request (PR) to the “ZF1 Future” repository. The last update was about two weeks ago.

It can be great !

Then we can move to vendor (it's my solution with gggeek/phpxmlrpc : but a lot of work for adaptation)

Else : add a test is easy : https://github.com/LimeSurvey/LimeSurvey/pull/3975
(i can PR your Pull Request)

1. Add a test : it's needed
2. Way to move to vendor ? Maybe after a PR to ZF1 Future ?

We will workaround the xmlrpc issue for now. Still, in the future, I suggest to keep only json. Obviously, not many people is using XML. If not someerror would have been triggered in the past by users.

Still, in the future, I suggest to keep only json.

Maybe add an event in RemoteControl just in case ;) (don't do core plugin)

Maybe add an event in RemoteControl just in case ;) (don't do core plugin)

What do you mean? Not sure i follow

@tibor.pacalat Is it ok to create a new ticket for using the "ZF1 Future" as vendor, instead of having a copy on our own repo? That should be done on DEV or Master?

What do you mean? Not sure i follow

If we keep only json for RPC, it can be cool to add an event (on remote control call) to allow replace JSON by another system (XMLRpc for example)

a new ticket for using the "ZF1 Future" as vendor, instead of having a copy on our own repo

You already fix the repo :+1: great great !

@tibor.pacalat Is it ok to create a new ticket for using the "ZF1 Future" as vendor, instead of having a copy on our own repo? That should be done on DEV or Master?

@gabrieljenik sure, please create a new ticket for this and it should go to master.

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

Tested and merged. Thank you @DenisChenu and @gabrieljenik!

Fixed in Release 6.6.7+241028