Say in other words you want to have the same result as the "save as a new question" button in the edit form where nothing except possibly the category has been changed.

As usual calculated will need special handling

@Pierre
Yes

Acutally, I was already considering this. I think it would be a much less confusing user-interface is we separated copy question and move question behaviour from the edit question behaviour. It would also simplify the code, which means fewer bugs.

I mean, how many times have you clicked on the 'Edit' icon for an question intending to make some changes, and then click 'Make copy', but then clicked 'Save changes' by mistake, and broken the original question.

@Tim
+1 (or Like) to your previous comment

btw, I was going through the code and found out the question_save function
and I think it is very easy to implement. and if you are busy... i will have it done next week or so.
Unless, of course... you already on it

No. I am not on it. I am on MDL-3030. Until that is done, I cannot promise to peer review anything.

As Pierre says, make sure to test calculated questions. Also, you will need to read http://docs.moodle.org/dev/Question_data_structures

@Tim, ok I will patch it and add a link to it when I am done.

I have made some progress, BUT I am stuck. and love to get some help...

I have added the following code to moodle/question/editlib.php (around/after line 403)
Which adds a listbox of "my courses" at the end of the Question Bank dialog, to which i am about to copy a question

question_category_select_menu($addcontexts, false, 0, "$category->id,$category->contextid");
// new code start here
echo "<hr/>";   
$mycourses = get_my_courses($USER->id);
foreach($mycourses as $mycourse) {
  $mycourseslist[$mycourse->id] = $mycourse->fullname;
}
echo choose_from_menu($mycourseslist,'selectedcourse');
echo '<input type="submit" name="copy" value="'.get_string('copyto', 'quiz')."\" />\n";
// new code end here
}

And added a new Action:"copy" to handle to copy/duplicate request,
around line 442 (inside question_showbank_action() function):

    if (optional_param('copy', false, PARAM_BOOL) and confirm_sesskey()) {
    $courseid = required_param('courseid', PARAM_SEQUENCE);
    $sql = "SELECT qc.id as tocategoryid, qc.contextid as contextid
FROM `mdl_context` c
JOIN `mdl_question_categories` qc ON c.id = qc.contextid
WHERE `instanceid` = $courseid ";

$questioncategory = get_record_sql($sql);
      if (! $tocategory = get_record('question_categories', 'id', $questioncategory->tocategoryid, 'contextid', $questioncategory->contextid)) {
          error('Could not find category record');
      }
      $tocontext = get_context_instance_by_id($questioncategory->contextid);


      $rawdata = (array) data_submitted();
      $questionids = array();
      foreach ($rawdata as $key => $value) {    // Parse input for question ids
          if (preg_match('!^q([0-9]+)$!', $key, $matches)) {
              $key = $matches[1];
              $questionids[] = $key;
          }
      }
      if ($questionids){
        $questionidlist = join($questionids, ',');
        $sql = "SELECT q.*, c.contextid FROM {$CFG->prefix}question q, {$CFG->prefix}question_categories c WHERE q.id IN ($questionidlist) AND c.id = q.category";
        if (!$questions = get_records_sql($sql)){
            print_error('questiondoesnotexist', 'question', $pageurl->out());
        }
        foreach($questions as $question) {
          $question->id = NULL;
          echo $question->name = 'copy_'.$question->name; echo "<br/>";
          $newquestion = $QTYPES[$question->qtype]->save_question($question, $question);                    
        }
      }
      die;
    }

What I am trying to do is, to copy the selected question(s) to the first question category of the selected course.
I am calling $QTYPES[$question->qtype]->save_question() for each question. BUT! it seems that the save_question_options() for each question type does not get invoked and the question is "half" duplicated.
I see it on the question bank list, but, with no content.
While examining the question/type/questiontype.php - save_question() function I saw that it is suppose to be invoked from within the function.
Should I invoke it explicitly? (For each question type and 3rd-party question type too)
And am I on the right track with this implementation? (Should it be done in a different way?)

Try reading http://docs.moodle.org/dev/Question_data_structures if you have never read it before.

You need to make sure you pass the right data to save_question, which is non-trivial, because get_question_options does not return the data structure that save_question expects.

Tim, Thanks you very much!

I wish I came across the document before, though i read a few "neighboring" documents and read through several question types too.

Again, thank you!

Our teachers would love this "save as a new question" button.
Is this coming?

This issue was assigned to me automatically, however I will not be able to work on this issue in the immediate future. In order to create a truer sense of the state of this issue and to allow other developers to have chance to become involved, I am removing myself as the assignee of this issue.

For more information, see http://docs.moodle.org/dev/Changes_to_issue_assignment

I have done the fix

Here is the diff:

https://github.com/mkassaei/moodle/compare/mdl_32523?expand=1

BTW, I deleted the "Make a copy" from the form and its occurrence in the code apart from

} else if (!empty($form->makecopy)) {
in question/type/calculated/questiontype.php and

if (empty($question->makecopy) && $question->itemid[$i]) {
and
if (!empty($question->makecopy) && !empty($question->convert)) {
in question/type/calculatedsimple/questiontype.php

I believe that 'makecopy' need to be replaced by 'duplicate', since we have a hidden element 'duplicate' in question/type/edit_question_form.php. Alternatively, we could replace 'duplicate' in new changes with 'makecopy' and therefore we might get away with not changing the above calculated qtypes.

I have not yet tested this yet, I have just looked at the code, but it is looking very good. A pleasingly small patch.

Some minor points:

1. I think that, to duplicate a question, you need moodle/question:add on the context of the currently selected category, and question_has_capability_on($question, 'view') on the question being copied. I think this affects

• question_bank_duplicate_action_column
• question/question.php
• validation() in question/type/edit_question_form.php.

2. I am not sure why you need protected $duplicatequestionurl;

3. I wonder if we can use the name makecopy instead of duplicate? If we are lucky that might make things like caclulated and STACK just work. If we are unlucky, it will cause problems.

4. I don't think you should remove the // Copies should not be hidden comment.

5. Please can you edit this issue, and write some testing instructions. We will need those before this can be integrated.

6. Also, if it were me, I would probably add more to the commit comment explaining what this change is.

Thanks Tim,
I have replaced 'duplicate' with 'makecopy' accordingly and added other minor changes.
I also tested with calculated qtype and it worked.

That is getting better, but two more things:

1. I just noticed ' (copy)' was hard-coded. It needs to be a langauge string, and you should not concatenate strings, because that does not work for languages taht need a different word order. So, you need a string like

$string['questionnamecopy'] = '{$a} (copy)';

2. I think you should not use 'makecopy' in question_bank_makecopy_action_column or makecopyaction. I think in those two you could just use the word 'copy'.

3. You need to rebase -i to reduce this to a single commit.

I have amended the code to accommodate the above changes including checking for capabilities that the user can add a question in the same category as the existing question and to view and edit the details of the question being copied.

Oops! Typo. The new lang string has ' {copy)'. They should both be round brackets.

Also, I just tested with qtype_multianswer, and that does not work for some reason.

I also tested a STACK question, which is a particularly complicated qtype, and that worked fine . So, we just need to fix multianswer, and the type, and we are done.

I have created two multianswer questions taking the two examples form
http://docs.moodle.org/26/en/question/type/multianswer
It was able to duplicate both of them.

I have changed the typo '{cop)' to '(cop)' and pushed it github

I don't know what happened before, but when I test again, multianswer questions are fine.

So, this is now ready for integration. We just need to wait for 2.6 to be released, then we can rebase this.

Rebased on latest version of master (Moodle 2.7 dev)
See https://github.com/mkassaei/moodle/compare/master...MDL-32523

The main moodle.git repository has just been updated with latest weekly modifications. You may wish to rebase your PULL branches to simplify history and avoid any possible merge conflicts. This would also make integrator's life easier next week.

TIA and ciao

I have rebased this on latest main Moodle git repository

Hi Mahmoud, this is a very nice change!
Please correct the following:
1. class definition must have phpdocs block with class description, copyright and package
2. there are trailing whitespaces in question/type/edit_question_form.php line 247
and the most important
3. this issue needs behat test, all other buttons have tests in question/tests/behat/*.feature
I can help you with behat test if you need it

linking to the css issue I found: MDL-43284

Moving this reopened issue out from current integration. Please, re-submit it for integration once ready.

Thanks Marina, I have done the suggested changes and wrote a behat test (I have not checked them in becasue I need to run behat before doing so). However, I has some issue with installing behat for windows.

I get the follwoing message:
—
Connection Error [ERR_CONNECTION]: Unable to connect to getcomposer.org

Request to https://getcomposer.org/installer failed with errors:
Failed to open stream: No connection could be made because the target machine actively refused it.
–
I can see the php code when I go to https://getcomposer.org/installer

Hi Mahmoud,
please try the following (from http://docs.moodle.org/dev/Acceptance_testing#Installation)

If you don't have curl installed or you have problems running curl http://getcomposer.org/installer | php:

    Download http://getcomposer.org/installer
    Store it in /your/moodle/dirroot/composerinstaller.php for example
    Run it from /your/moodle/dirroot with php composerinstaller.php, you can delete this file after running the next step (php composer.phar update --dev) 

I have written a behat test-file for this, However, I have not tested it because I had some issues with my local server and behat installation after updating my master branch.

In terms of the order of integration, this should be integrated before

https://tracker.moodle.org/browse/MDL-33839
and
https://tracker.moodle.org/browse/MDL-33653

I have just rebased this on latest version of Moodle master

Results for MDL-32523

• Remote repository: git://github.com/mkassaei/moodle.git

• Remote branch MDL-32523 to be integrated into upstream master
  • Executed job http://integration.moodle.org/job/Precheck%20remote%20branch/523
  • Details: http://integration.moodle.org/job/Precheck%20remote%20branch/523/artifact/work/smurf.html

Results for MDL-32523

• Remote repository: git://github.com/mkassaei/moodle.git

• Remote branch MDL-32523 to be integrated into upstream master
  • Executed job http://integration.moodle.org/job/Precheck%20remote%20branch/538
  • Details: http://integration.moodle.org/job/Precheck%20remote%20branch/538/artifact/work/smurf.html

Mahmoud, I just pushed three small commits on top of your work: https://github.com/timhunt/moodle/compare/master...MDL-32523 Are you happy with those changes?

Mahmoud checked out my new commits, and was happy. I squashed two into the main commit, and left the third one separate. I hope that makes sense.

Submitting for integration.

Thanks Tim and Mahmoud Kassaei,

Looks good to me, + passes all tests.

Integrated to master only.

works good, thanks

I won't be saying "Thanks!" this week. I'm tired of it.

For the good (and the bad), your code is now part of Moodle, the best LMS in the world. Hope you are contributing for that to continue being a fact (and not the opposite), sincerely.

Just closing this as fixed, ciao

PS: Just a bit of black/cruel humor, sorry, LOL!