See PR https://github.com/LimeSurvey/LimeSurvey/pull/339

mail_registered_participants is almost a direct copy of invite_participants, with one significant change: the default conditions can be overridden. Main use: do not mail all 'unsent' users, but select one.

For instance select one by tid:

$overrideAllConditions = Array();
$overrideAllConditions[] = 'tid = 12345';
$response = $myJSONRPCClient->mail_registered_participants( $sessionKey, $survey_id, $overrideAllConditions );

@DenisChenu or @Mazi
Do i need to create PR's for other branches?

Hi JanE : for develop : surely (but not sure remote control work on develop)

I don't not use Remote control a lot for mail sending, but the condition for invite_participants seems very a good idea .

PR for the develop branch:
https://github.com/LimeSurvey/LimeSurvey/pull/340

I will implement $overrideAllConditions in invite_participants as soon as this is tested for mail_registered_participants. invite_participants uses findUninvited() in stead of findAll(), so I will have to copy the conditions from findUninvited() to remotecontrol_handle.php. Adding features is less dangerous than changing current code.

Yes, i know .... for sending email : i add my own controller , for commands:

Own Class in commands
commands/myOwnClass.php

This never break , and it's more easy to fix when updating LS core.

My first thoughts were the same: a modified commands/InviteCommand.php
https://bugs.limesurvey.org/view.php?id=9764
But the two of you talked me into changing the RC API.

But you are right: we are going to use this in production and have to be very careful with updating LS. Could you pull this and/or speedup a new build?

For using on Production : why not make your own class ?
(I'm not use any of Remote_control t accept pull request in remote_control actually, like already said : i'm only a dev, not the leader dev).

I'd rather see this ASAP in the current 2.06 branch than muddling with OwnClasses. Should we involve @c_schmitz in this?

Sam, can you please have a short look at the LS 3 pull request and merge if it looks fine to you?!

Please also merge the 2.06 PR. This is LSRC only so it won't break anything at the core and Jan is on stand-by for fixing any upcoming issues.

Thanks!

Both PRs have a second commit now to fix a typo (consitions -> conditions).

I have the documentation ready and can add that to https://manual.limesurvey.org/RemoteControl_2_API as soon as the PRs are merged

Talking about the docs: https://manual.limesurvey.org/RemoteControl_2_API#PHP_Example is outdated, now that there is a jsonRPCClient.php in application/libraries/

Composer is not needed to pull the weberhofer/jsonrpcphp repository and calling the RC is easier:

require_once 'application/libraries/jsonRPCClient.php';
...
$myJSONRPCClient = new JsonRPCClient( LS_BASEURL.'index.php/admin/remotecontrol' );

Note that the URL for the LSRC has changed as well /index.php/admin/remotecontrol.

Shall I update this part of the docs as well?

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

Thanks for committing. The PR for the master branch is still open. Would not it be better to re-assign the issue to @c_schmitz so he can take care of it when he is back from holiday?

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

Edited the documentation:
https://manual.limesurvey.org/RemoteControl_2_API#mail_registered_participants

This issue can be marked as fixed and closed IMHO. I cannot do that because 'reporters' cannot Assign to, Change status, Stick/unstick, Clone or Close. Reporters can't even Edit the original issue.

Maybe you should "Allow Reporter to close Issue"
https://www.mantisbt.org/forums/viewtopic.php?f=3&t=21761

I think the problem is (in general) :

• Fix the issue : the issue is fixed in GIT
• Close the issue : the release is done.

But still a good idea to leave more option to Reporter (and feedback assigned to reporter too ;) )