The behat.yml in 2.8 lists under features the root features folder in each plugin and in runtime all features are executed including those in sub folders. In 2.9 it lists particular features but only from the root features folder and only those features are executed. Adding the root features folder to the behat.yml fixes that but only until the next initialization. Bug? Known? Or am I missing something?
Itamar Tzadok
Posts made by Itamar Tzadok
See CONTRIB-5620 re the Dataform error. Resolved, on git, but not yet in a formal release. I will add a branch on git for interim releases, but the next tagged release will be only in May, on the Moodle release point.
The condition doesn't currently work across courses. I've been thinking about adding to the condition configuration a setting for site wide dashboard dataforms. But this and other possible enhancments and considerations require discussion. You can open an issue in the Set: Dataform component tracker for that and we can take it from there.
The availability plugin is not a sub plugin of the Dataform so Dataform content conditions on course activities are not included in a Dataform preset. The conditions are included in the backup of the restricted activity in a course backup, but only if the backup includes the course activities (otherwise, the reference to the dashboard Dataform in the restricted activity will remain unresolved).
A new plugin Availability dataformcontent allows teachers to restrict user access to an activity or section based on content of a designated Dataform instance in the course. The plugin requires the Dataform module plugin. Version for 2.8 awaiting approval in Moodle plugins repo, but already available from git at https://github.com/itamart/moodle-availability_dataformcontent/releases/tag/v2.8.0.
For a related discussion down this forum see Allocate resources/activities to individual students.
Please note: this plugin requires the Dataform module plugin which is available from Moodle plugins repo and from git.
Hope this plugin helps anyone. Feel free to feed back.
The mandatory fields in the Database activity will be available from 2.9. You will set the field as required in the field configuration.
The mandatory fields by * in the field pattern is not in the Database activity but in the Dataform activity. So, if you are using the Database, this option is not available for you.
I will look into the Quiz access rule approach and continue this on the tracker. Thanks.