Posts made by Visvanath Ratnaweera

Picture of Particularly helpful Moodlers Picture of Translators
The story is not over. We started getting the Not registered mails. Followed https://docs.moodle.org/405/en/Site_registration#I_can't_register_my_cloned_site and attempted to register manually. Got the message that there was a previous registration but now deleted so that we can re-register.
 
When I go back and retry getting:
===
Invalid token - token not found

More information about this error

Debug info:
Error code: errorws×Dismiss this notification
Stack trace:
line 126 of /lib/classes/hub/api.php: core\exception\moodle_exception thrown
line 98 of /lib/classes/hub/api.php: call to core\hub\api::process_curl_exception()
line 69 of /lib/classes/hub/api.php: call to core\hub\api::call_rest()
line 137 of /lib/classes/hub/api.php: call to core\hub\api::call()
line 409 of /lib/classes/hub/registration.php: call to core\hub\api::update_registration()
line 66 of /admin/registration/confirmregistration.php: call to core\hub\registration::confirm_registration()
===
 
Back to the moodle.com contact form?
Picture of Particularly helpful Moodlers Picture of Translators
Rick, you wrote:
> if someone is using non-core "anything," are you saying that Moodle developers should not leave this non-core stuff in the cold?

You misread.

What I said was:
>> But in 1) you find all sorts, including non-techies and the clueless.  Developments in Moodle should not leave them in the cold.

Note,
>> 1. Quizzes using only the core question types.
 
P.S. This goes way beyond the original question, Moodle 5.0.1 Question Bank. Therefore I gave this sub-thread a new subject line, Moodle development status quo [General topic], in case this grows further and the moderators want to split the discussion.
Picture of Particularly helpful Moodlers Picture of Translators
You mean, to delete all the questions of a particular add-on question type? I looked for the same recently, see [qtype_crossword] Can't create new questions nor duplicate courses (Moodle 4.5.5). Found no back-end solution. Solved the problem by deleting them (tediously) on the GUI.
Average of ratings: Useful (1)