Coding error detected, it must be fixed by a programmer: mygroupid() can not be used any more, please use groups_get_all_groups() instead.

Re: Coding error detected, it must be fixed by a programmer: mygroupid() can not be used any more, please use groups_get_all_groups() instead.

by Howard Miller -
Number of replies: 3
Picture of Core developers Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Peer reviewers Picture of Plugin developers

You could also switch Debugging right up to developer and reproduce the error again. That will give you a trace of it being called.

My bet is that you have a plugin that calls get_current_group. This is also in deprecatedlib.php but does not throw a warning. BUT... it does call mygroupid() which (as you found out) does.

So, either find what called get_current_group() or do the trace.

I have a feeling that I submitted a bug about this...

EDIT:
I submitted one very similar, not this. However, I have now - MDL-50818

In reply to Howard Miller

Re: Coding error detected, it must be fixed by a programmer: mygroupid() can not be used any more, please use groups_get_all_groups() instead.

by Ed Main -

Phew . . . just upgraded from 2.81 to 2.91 and was presented with the same ("Coding error detected, it must be fixed by a programmer: mygroupid() can not be used any more, please use groups_get_all_groups() instead.") error message. Turned on debugging and among there was reference being made to a plugin . . . deleted the plugin and now all is well . . . thanks! smile 

In reply to Ed Main

Re: Coding error detected, it must be fixed by a programmer: mygroupid() can not be used any more, please use groups_get_all_groups() instead.

by Fiona Graham -

I am also getting this error after upgrading to 2.9.1. 


@ Ed: Can you tell me which pluggin you removed?


Thanks,


In reply to Fiona Graham

Re: Coding error detected, it must be fixed by a programmer: mygroupid() can not be used any more, please use groups_get_all_groups() instead.

by Fiona Graham -

I had to turn on debugging for developers before I found the pluggin name that was giving me problems.  It happened to be the FN marking block. Once I removed that my problem went away.