Uploaded image for project: 'Confluence'
  1. Confluence
  2. CONF-21079

Going to legacy Plugin Manager from General Config displays token error

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Won't Fix
    • Affects Version/s: 3.4
    • Fix Version/s: None
    • Component/s: None
    • Environment:

      Confluence 3.4 Standalone

      This has been confirmed on Chrome 6.0.472.63 and Firefox 3.6.10 on OS X (screenshots of each attached).

    • Last commented by user?:
      false
    • Support reference count:
      1

      Description

      Going to the Plugin Manager ([Confluence Address]/admin/plugins.action) from the Plugin Administration Page link on Confluence Admin > General Config displays an error:

      The following error(s) occurred:
      Your request could not be processed because a required security token was not present in the request. You may need to re-submit the form or reload the page.

      This is failing silently / no error/s appear in the Confluence log.

        Attachments

          Issue Links

            Activity

            Hide
            bmallow Brad Mallow [Atlassian] added a comment -

            Reported via CSP-52882

            Show
            bmallow Brad Mallow [Atlassian] added a comment - Reported via CSP-52882
            Hide
            bmallow Brad Mallow [Atlassian] added a comment -

            I changed this bug report back to it's original Summary and Description. Currently it is possible to disable the UPM by disabling the REST plugin on which it depends, therefore I'd say it makes sense to keep a link around to the legacy system. However, whether or not we should surface a link to the legacy plugin manager is open for debate, but is not the point of this bug.

            The point of this bug is to explain that we currently throw an error when accessing the page via the link.

            Show
            bmallow Brad Mallow [Atlassian] added a comment - I changed this bug report back to it's original Summary and Description. Currently it is possible to disable the UPM by disabling the REST plugin on which it depends, therefore I'd say it makes sense to keep a link around to the legacy system. However, whether or not we should surface a link to the legacy plugin manager is open for debate, but is not the point of this bug. The point of this bug is to explain that we currently throw an error when accessing the page via the link.
            Hide
            mhrynczak Mark Hrynczak [Atlassian] added a comment -

            As pointed out by Brad, this issue isn't really fixed.

            The linked issue has been fixed by correcting the link to point to UPM.

            However, anyone going to /admin/plugins.action will still see the error. This may still be linked to from elsewhere in the product, or in plugins, or in documentation. The plugin manager is still in the product as a fallback in case of issues with UPM, so it should be accessible.

            This should be fixed to not give a misleading error about security tokens.

            Show
            mhrynczak Mark Hrynczak [Atlassian] added a comment - As pointed out by Brad, this issue isn't really fixed. The linked issue has been fixed by correcting the link to point to UPM. However, anyone going to /admin/plugins.action will still see the error. This may still be linked to from elsewhere in the product, or in plugins, or in documentation. The plugin manager is still in the product as a fallback in case of issues with UPM, so it should be accessible. This should be fixed to not give a misleading error about security tokens.
            Hide
            ssaasen Stefan Saasen added a comment -

            Not fixed in 3.4.1

            Show
            ssaasen Stefan Saasen added a comment - Not fixed in 3.4.1
            Hide
            shaffenden Steve Haffenden [Atlassian] added a comment -

            Hi There

            Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog now for quite some time with very little or no progress being made.

            Because this issue is now older than 2 years, has a low priority and has no votes I'm going to close this as won't fix. Unfortunately it is unlikely that we'd be able to address this issue in the foreseeable future.

            Regards
            Steve Haffenden
            Confluence Bugmaster

            Show
            shaffenden Steve Haffenden [Atlassian] added a comment - Hi There Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog now for quite some time with very little or no progress being made. Because this issue is now older than 2 years, has a low priority and has no votes I'm going to close this as won't fix. Unfortunately it is unlikely that we'd be able to address this issue in the foreseeable future. Regards Steve Haffenden Confluence Bugmaster

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Last commented:
                  1 year, 26 weeks, 4 days ago