Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Minor
-
Resolution: Duplicate
-
Affects Version/s: 2.0
-
Fix Version/s: 2.0
-
Component/s: Repositories
-
Labels:None
-
Affected Branches:MOODLE_20_STABLE
-
Fixed Branches:MOODLE_20_STABLE
Description
I don't think the current api implementation or example plugins are particularly easy to undestand or write plugins for:
1/ The use of the GLOBAL variable $action is really not clear (and if it is a global, should it not be in caps?). Could we not do this work within the plugin isntance variables?
2/ print_login use is not clear
- When does it get called? (It certainly isn't used if its defined).
- Where will resultant of this be posted to - where do I do something with this login?
- There is an ajax flag, and it apears to output needs to be in a specific format when this is set? What is this?
- It looks like I need to set repo_id in here?
3/ The logout button seems to only cause a change in the $action variable, which the plugin needs to inspect. Again could this not be done by a function of the plugin rather than the module creator needing to examine $action?