Moodle
  1. Moodle
  2. MDL-32024

Coding error detected, it must be fixed by a programmer: Invalid component used in plugin/component_callback():mod_

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Cannot Reproduce
    • Affects Version/s: 2.2.2
    • Fix Version/s: None
    • Component/s: General
    • Labels:
    • Affected Branches:
      MOODLE_22_STABLE
    • Rank:
      38696

      Description

      Moodle Version 2.2.2, Windows 2008R2 server,IIS, MS SQL 2008, PHP 5.3.6

      After upgrade from 2.1.1+ to 2.2.2 I received the message:
      Coding error detected, it must be fixed by a programmer: Invalid component used in plugin/component_callback():mod_

        Issue Links

          Activity

          Hide
          Michael de Raadt added a comment -

          Hi, Zoran.

          Could you please explain how this error came about? What were you doing at the time? How would we reproduce the problem?

          Show
          Michael de Raadt added a comment - Hi, Zoran. Could you please explain how this error came about? What were you doing at the time? How would we reproduce the problem?
          Hide
          Zoran Zdravev added a comment -

          Hello Michael,

          This message appears under Site Administration/Reports/Comments and it came after upgrading from 2.1.1+ to 2.2.2 (two days ago).

          There are no special activities to reproduce this error, I didn’t try to reinstall 2.2.2 again (it is production site).
          I didn’t found problems or no one reports a problem during the work yet, but I think I should wait few days more.

          If you need more information please do not hesitate to contact me.

          Show
          Zoran Zdravev added a comment - Hello Michael, This message appears under Site Administration/Reports/Comments and it came after upgrading from 2.1.1+ to 2.2.2 (two days ago). There are no special activities to reproduce this error, I didn’t try to reinstall 2.2.2 again (it is production site). I didn’t found problems or no one reports a problem during the work yet, but I think I should wait few days more. If you need more information please do not hesitate to contact me.
          Hide
          Michael de Raadt added a comment -

          I wasn't able to reproduce this. I wonder if there is some contributed plugin that might be causing your problem.

          Show
          Michael de Raadt added a comment - I wasn't able to reproduce this. I wonder if there is some contributed plugin that might be causing your problem.
          Hide
          Zoran Zdravev added a comment -

          We haven't additional plugins. Meantime we have reported problems in few cases, but all are connected with writing in Cyrillic (posting in forums, description of activities, description of resources). Everything is ok with Latin letters, but with Cyrillic is not. For example posting in forums is ok with Latin and Posting with Cyrillic is not ok. It cannot be accepted eq Cyrillic letters are ignored.

          With previous version 2.1.1+ everything was Ok.

          Show
          Zoran Zdravev added a comment - We haven't additional plugins. Meantime we have reported problems in few cases, but all are connected with writing in Cyrillic (posting in forums, description of activities, description of resources). Everything is ok with Latin letters, but with Cyrillic is not. For example posting in forums is ok with Latin and Posting with Cyrillic is not ok. It cannot be accepted eq Cyrillic letters are ignored. With previous version 2.1.1+ everything was Ok.
          Hide
          Sean Keogh added a comment -

          We have this exact problem as well, on one of our customer's sites. It is a very standard Moodle 2.2.2+ site, upgraded from 2.1 a few weeks ago. Going to Site Administration/reports/comments produces the exact error message listed in the title.

          The comment mechanism itself seems ok - I can add a comment block and it accepts comments readily enough.

          I have refreshed the contents of /comment and /blocks/comment but that has made no difference.

          You can look at this on our customer site if you wish - I can arrange access.

          Sean Keogh

          Show
          Sean Keogh added a comment - We have this exact problem as well, on one of our customer's sites. It is a very standard Moodle 2.2.2+ site, upgraded from 2.1 a few weeks ago. Going to Site Administration/reports/comments produces the exact error message listed in the title. The comment mechanism itself seems ok - I can add a comment block and it accepts comments readily enough. I have refreshed the contents of /comment and /blocks/comment but that has made no difference. You can look at this on our customer site if you wish - I can arrange access. Sean Keogh
          Hide
          Sean Keogh added a comment -

          Can this be reopened please? This is the same customer that has the out of memory error when using course completion, so tey are not too happy with Moodle at the moment.

          Show
          Sean Keogh added a comment - Can this be reopened please? This is the same customer that has the out of memory error when using course completion, so tey are not too happy with Moodle at the moment.
          Hide
          Helen Foster added a comment -

          Zoran and Sean, thanks for the additional information. As this issue duplicates MDL-31010, rather than reopening it, let's use MDL-31010 for tracking the issue from now on.

          Please vote for MDL-31010 and watch it if you wish to receive email notification of issue updates.

          Show
          Helen Foster added a comment - Zoran and Sean, thanks for the additional information. As this issue duplicates MDL-31010 , rather than reopening it, let's use MDL-31010 for tracking the issue from now on. Please vote for MDL-31010 and watch it if you wish to receive email notification of issue updates.

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: