Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

Talk:Roles: Difference between revisions

From MoodleDocs
mNo edit summary
(legacy support for isstudent() and isteacher())
Line 2: Line 2:


choice_canviewresults
choice_canviewresults
== legacy support for isstudent() and isteacher() ==
We could provide legacy support for modules (and core) to continue using isstudent() and isteacher() calls, by replacing these with stubs that simply wrap the new access control API and feed in the proper parameters. This might help reduce the initial effort (i.e., you don't HAVE to update every. single. module. at first, just the ones most affected by this API change. then, as time allows, and as modules are being updated anyway, migrate them to the new API)

Revision as of 15:42, 6 July 2006

The list of capabilities for some activities should include viewing as a separate capability since it is a distinct action from editing or taking part, for example

choice_canviewresults

legacy support for isstudent() and isteacher()

We could provide legacy support for modules (and core) to continue using isstudent() and isteacher() calls, by replacing these with stubs that simply wrap the new access control API and feed in the proper parameters. This might help reduce the initial effort (i.e., you don't HAVE to update every. single. module. at first, just the ones most affected by this API change. then, as time allows, and as modules are being updated anyway, migrate them to the new API)