tjhunt e92c286c20 block contexts: MDL-19098 every block should have a context ... even non-course and sticky blocks. The parent context is block_instances.parentcontextid. The block context should be used for checking permissions directly related to the block, like moodle/block:view or moodle/site:manageblocks. However, if the block is displaying information about the current page, for example the participants block showing who 'here', then it may be better to use the context of the page where the bloack is appearing - in other words $this->page->context - to check permissions about the user's ability to see participants here. Or, if the block is displaying something stronly related to courses, for example, a course meny block, the block should probably use the context for $this->page->course to check permissions.		2009-07-13 08:37:34 +00:00
..
access.php	filters: MDL-7336 create new moodle/filter:manage capability	2009-04-13 06:54:11 +00:00
events.php	MDL-10107 Fixed the definition of message providers ... it now works through files very similar to those for events and capabilities, which makes them easy to add/remove/change as necessary	2008-07-31 08:01:46 +00:00
index.html	Some blank index.html files to prevent browsing	2004-03-20 04:10:26 +00:00
install.php	MDL-14990 implemented query loggin in new native DML drivers	2009-06-13 15:59:55 +00:00
install.xml	blocks MDL-19536: rename block_instances.contextid to parentcontextid to avoid gross confusion	2009-07-10 05:58:59 +00:00
messages.php	MDL-16438 centralise information about plugins to avoid duplication, includes local customisation conversion to standard plugin structure + fixes for some recent regressions; see tracker for more details and links to docs and forums discussions	2009-06-19 14:25:56 +00:00
upgrade.php	block contexts: MDL-19098 every block should have a context	2009-07-13 08:37:34 +00:00
upgradelib.php	2.0 prefixes syntax	2009-05-23 22:51:53 +00:00