Thanks for sharing this plugin with the Moodle community. Some formal issues were detected and reported by our automated plugin checker tool. Please review all the plugin checker results and fix the issues mentioned, if possible. These changes are typically pretty easy to make but if you have any questions just let us know. For now, I am going to mark this plugin as needing more work. Once you get these formal issues resolved, please use the link “Schedule this plugin for re-approval” so that the plugin code can be fully reviewed and approved by my human colleagues.

Hi. I have one question about tracker URL. What is the best way to get a Tracker URL? The Gitgub Pull URL like this https://github.com/cescobedo/moodle-auth_dev/pulls? or make a request for project in tracker.moodle.org to Anthony Borrow?

Carlos,

I noticed that you did not specify an issue tracker for your plugin. Providing a place for users of your plugin to report issues encourages participation and provides a way for users to report bugs, make feature requests, or suggest other types of improvements. There are a couple of options. You are welcome to request that a component be created in the Moodle Tracker. This will allow for you to become more familiar with how issues are managed in Moodle core but may take a little more time to setup. Alternatively, for folks who are using Github.com, you can use the issues feature of Github to handle such requests. Kindly let me know which of these two options seems best for you.

If you go the github route, the URL would be: https://github.com/cescobedo/moodle-auth_dev/issues

Please provide a documentation URL. You are welcome to create your documentaiton in Moodle Docs, See http://docs.moodle.org/dev/Plugin_documentation for more information. Since it is an authentication plugin and fairly simple to setup and use, you may just want to point to: https://github.com/cescobedo/moodle-auth_dev/blob/master/README.md

Please do not hesitate to let me know if there is anything I can do to be supportive of your efforts. Peace - Anthony

Hi Anthony,
thanks for you fast answer.

I'd like to make a request to have a component in the Moodle Tracker. I know Jira and I'd like to use Moodle Tracker to maintain all my plugins.
- auth_dev - https://moodle.org/plugins/view.php?plugin=auth_dev
- Custom Navigation - https://moodle.org/plugins/view.php?plugin=local_navigation
- UpgradeDB - https://moodle.org/plugins/view.php?plugin=local_upgradedb
- Reset My Moodle - https://moodle.org/plugins/view.php?plugin=tool_resetmymoodle
I have two users in the Moodle Tracker, carlos.escobedo (is the user that i want to use), cescobedo is the user to moodle partner that i work it.

So I will build documentation in doc.moodle.org as soon as possible.

If this isn't place to make request to tracker please don't hesitate to give me the right place to make a request.

Thanks for all and i'm sorry for the inconvenience,

I make a little change to allow this plugin only for site admins.

Thanks Carlos for sharing this plugin with the community. I appreciate the idea and the simple implementation of it. You may consider enable the prelogout_hook() functionality if and only if the development mode is on (e.g. the the DEBUG_DEVELOPER is set). This might add yet another protection level to those admins who ignore the plugin name and the description and are crazy enough to use it at production sites.

You are cleared to land now, welcome to the Plugins directory.

Forgot to mention, it might be good to highlight in the description and the UI itself that the only thing that has to be done is to enable this auth_dev plugin. There is no need to set it as any user's authentication method.

Thanks a lot David.
I've updated the documentation with your comment.
As soon as possible I will update the plugin with this check the DEBUG_DEVELOPER is set

i just did an "auto install" through mysite.com/moodle -> site admin menu -> plugins -> install plugins -> clicked *install from moodle.org/plugins*

and it is giving me a version of
2014051200
vs
2014051300

errr difference in version numbers....
(( 200 vs 300 ))

i do not know if a "mis type happened" or if mess up in version.php file

but it is forcing the "upgrade" notation for plugins to happen. when i goto site admin menu -> notifications. or overview of plugins area on my site.

I tested this plugin in Moodle 3.0.2 and works fine. Enjoy.

Also in 3.1+

Hi, I updated my Adaptable theme yesterday and now the auth development tools plugin doesn't work anymore....is anyone else having this issue? I am using moodle 3.2.1

Hi Ali,

is there any error message? Could you enable Debugging mode in Site Administration / Development / Debugging (Developer: extra Moodle debug messages for developers) and check Display debug messages and look if there is an error message? Also, which version of Adaptable theme do you have (maybe, 1.3.4)?

Cheers.