This implementation will introduce a qbank plugin "managecategories"
which will add the question categories feature in the question bank view
by replacing the core classes. Having this plugin will give users
the flexibility of enabling or disabling the category tab.
This implementation will introduce a qbank plugin "exporttoxml"
which will implement the export to xml action in the question
bank view by replacing the core class. Having this plugin will
give users the flexibility of enabling or disabling this action.
This implementation will introduce a qbank plugin "viewcreator"
which will view the question creator/modifier column in
the question bank view by replacing the core classes. Having
this plugin will give users the flexibility of enabling
or disabling the question creator and modifier column
in the question bank view.
Co-Authored-By: Marc-Alexandre Ghaly <marc-alexandreghaly@catalyst-ca.net>
This implementation will introduce a qbank plugin "viewquestiontext"
which will view the question text row in the question bank view
by replacing the core class. Having this plugin will give users
the flexibility of enabling or disabling the question text row
in the question view.
This implementation will introduce a qbank plugin "viewquestionname"
which will view the question name column in the question bank view
by replacing the core classes. Having this plugin will give users
the flexibility of enabling or disabling the question name column.
This implementation will introduce a qbank plugin "viewquestiontype"
which will view the question type column in the question bank view
by replacing the core class. Having this plugin will give users
the flexibility of enabling or disabling the question type
in the question bank view.
Admin should respect the home page preference set
just like any other user. Also when user preference
is set to dashboard, the home points to the dashboard
and the dashboard should become "Site home" which would
point to Site home.
- Part of: MDL-69588
The menu used to select one of the available languages is now
displayed as a submenu within the user menu only when a user is
logged in.
- Part of: MDL-69588
The first tab in the secondary navigation is to show the tab to
navigate to the modules view.php file. This patch sets the url
to view.php and if it matches the pages url, also sets it as
active.
- Part of: MDL-69588
Enables to pre-define nodes which should be added into the "more" menu
by default and also setting a maximum limit of displayed nodes in the
secondary navigation.
This implementation will introduce a qbank plugin "exporquestions"
which will add the export feature in the question bank view
by replacing the core classes. Having this plugin will give users
the flexibility of enabling or disabling the export questions tab.
Co-Authored-By: Guillermo Gomez Arias <guillermogomez@catalyst-au.net>
This implementation will introduce a qbank plugin "importquestions"
which will allow user to import a bank of questions in the question bank view
by replacing the core class. Having this plugin will give users
the flexibility of enabling or disabling the question import
in the question bank view.
Co-Authored-By: Marc-Alexandre <marc-alexandreghaly@catalyst-ca.net>
This implementation will introduce a qbank plugin "editquestion"
which will implement the edit question, add question and copy
question actions in the question bank view by replacing the
core classes. Having this plugin will give users the
flexibility of enabling or disabling these actions.
This implementation will introduce a qbank plugin
"deletequestion" which will implement the delete question
action in the question bank view by replacing the core
class. Having this plugin will give users the
flexibility of enabling or disabling this action.
This commit implements the qbank api so that any plugin
can implement its own question bank. This api currently
works parallely with the moodle core classes and the
added qbank in the core, means the moment a plugin
is installed, that object is replaced with the object
from the plugin instead of core, which means the api
has flexibility till the plugins are integrated and the
plugins can be integrated in any order.
All the old classes are still there and not deprecated
as there is a different tracker for the changes to the
quiz and another tracker for class deprecation and
class renaming. Core question units tests are pointing
to the new api structure but the classes are pointing
to the location related to the plugin availability.
Co-Authored-By: Luca Bösch <luca.boesch@bfh.ch>
Co-Authored-By: Guillermo Gomez Arias <guillermogomez@catalyst-au.net>
one more array fix
