Details

    • Type: Sub-task Sub-task
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Won't Fix
    • Affects Version/s: 2.0
    • Fix Version/s: None
    • Component/s: Portfolio API
    • Labels:
      None
    • Affected Branches:
      MOODLE_20_STABLE
    • Rank:
      719

      Description

      getting
      No common formats between any available portfolio plugin and the calling location forum_portfolio_caller

      • line 240 of lib/portfoliolib.php: call to debugging()
      • line 3481 of mod/forum/lib.php: call to portfolio_add_button->to_html()
      • line 5815 of mod/forum/lib.php: call to forum_print_post()
      • line 239 of mod/forum/discuss.php: call to forum_print_discussion()

      when only picasa enabled in forum posts - I suppose it would be better to show this as a real warning on configuration pages instead of debug info in each forum post

        Issue Links

          Activity

          Hide
          Penny Leach added a comment -

          How do you think it should be done as a warning on configuration pages? There is no "registry" of which formats are supported by which places in Moodle, because it is dependant on the exact content at export time.

          A forum post with an attachment of type 'image' can be exported to picassa, a pure forum post cannot. You can't really detect every single possible content type available for export and display to the admin user, and even if you could it wouldn't be any good because users would still try and export things that weren't supported.

          What we could do is display a warning to say something fuzzy like, "this plugin only supports a narrow range of formats, are you sure you want to enable it"

          Also, remember that while you're seeing the debug message, normal users just wouldn't be offered the option to do the export when there's no cross over in available formats.

          Show
          Penny Leach added a comment - How do you think it should be done as a warning on configuration pages? There is no "registry" of which formats are supported by which places in Moodle, because it is dependant on the exact content at export time. A forum post with an attachment of type 'image' can be exported to picassa, a pure forum post cannot. You can't really detect every single possible content type available for export and display to the admin user, and even if you could it wouldn't be any good because users would still try and export things that weren't supported. What we could do is display a warning to say something fuzzy like, "this plugin only supports a narrow range of formats, are you sure you want to enable it" Also, remember that while you're seeing the debug message, normal users just wouldn't be offered the option to do the export when there's no cross over in available formats.
          Hide
          Penny Leach added a comment -

          Dan and I just had a talk about this and we suggested making the administration page (and I guess possibly also the user portfolio page, where they can also disable certain plugins), say which formats are supported by which plugins - so when plugins are enabled/disabled, the user can see an explanation.

          The problem with this is that the formats are very dependant on the type of content that is being exported in Moodle. For example, the forum theoretically supports about 5 formats, but only one or two depending on what exactly is being exported.

          We thought maybe a list of the formats a plugin supports, along with a link to a Moodle docs page explaining about the formats might help here.

          Show
          Penny Leach added a comment - Dan and I just had a talk about this and we suggested making the administration page (and I guess possibly also the user portfolio page, where they can also disable certain plugins), say which formats are supported by which plugins - so when plugins are enabled/disabled, the user can see an explanation. The problem with this is that the formats are very dependant on the type of content that is being exported in Moodle. For example, the forum theoretically supports about 5 formats, but only one or two depending on what exactly is being exported. We thought maybe a list of the formats a plugin supports, along with a link to a Moodle docs page explaining about the formats might help here.
          Hide
          Michael de Raadt added a comment -

          Thanks for reporting this issue.

          We have detected that this issue has been inactive for over a year. It was reported as affecting versions that are no longer supported.

          If you believe that this issue is still relevant to current versions (2.5 and beyond), please comment on the issue. Issues left inactive for a further month will be closed.

          Michael d.

          TW9vZGxlDQo=

          Show
          Michael de Raadt added a comment - Thanks for reporting this issue. We have detected that this issue has been inactive for over a year. It was reported as affecting versions that are no longer supported. If you believe that this issue is still relevant to current versions (2.5 and beyond), please comment on the issue. Issues left inactive for a further month will be closed. Michael d. TW9vZGxlDQo=
          Hide
          Michael de Raadt added a comment -

          I'm closing this issue as it has been inactive for over a year has been recorded as affecting versions that are no longer supported.

          This is being done as part of a bulk annual clean-up of issues.

          If you still believe this is an issue in supported versions, please create a new issue.

          Show
          Michael de Raadt added a comment - I'm closing this issue as it has been inactive for over a year has been recorded as affecting versions that are no longer supported. This is being done as part of a bulk annual clean-up of issues. If you still believe this is an issue in supported versions, please create a new issue.

            People

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

              Dates

              • Created:
                Updated:
                Resolved: