Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-25259

Confluence Page Gadget on JIRA will shows "Resource cannot be found" on Confluence 4.2

XMLWordPrintable

      Description of The Bug

      When JIRA user add Confluence Page Gadget from Confluence 4.2 into its dashboard, the page will load fine, but there would be a message at the top of the gadget:

      The resource <Server Base URL>/rest/likes/1.0/content/undefined/likes, cannot be found.

      Workaround

      Disabling "Confluence Like Plugin" from UPM resolve the issue

        1. likes.png
          likes.png
          20 kB
        2. Screenshot-2.png
          Screenshot-2.png
          19 kB

            [CONFSERVER-25259] Confluence Page Gadget on JIRA will shows "Resource cannot be found" on Confluence 4.2

            Paul Curren added a comment -

            Thanks Ashton.
            The fix was committed on the 21st June so the first version you'll see it working is 4.3-beta1.

            Paul Curren added a comment - Thanks Ashton. The fix was committed on the 21st June so the first version you'll see it working is 4.3-beta1 .

            Ashton Treadway added a comment -

            This is still broken when using JIRA 5.1 and Confluence 4.3m11.

            Ashton Treadway added a comment - This is still broken when using JIRA 5.1 and Confluence 4.3m11.

            Steve Smith added a comment - - edited

            Count me in as a user affected. This is a big deal as we embed Confluence pages on the JIRA System Dashboard to welcome users to our Atlassian-based support system. HELP!

            Like Aleksander, I don't want to disable the Like button as it has so many obvious benefits.

            I think it also goes without saying that similar to other services (ahem) that implement "Like" that one should be able to "Like" a Confluence page from ANYWHERE (including JIRA) through the REST interface. Cheers

            Steve Smith added a comment - - edited Count me in as a user affected. This is a big deal as we embed Confluence pages on the JIRA System Dashboard to welcome users to our Atlassian-based support system. HELP! Like Aleksander, I don't want to disable the Like button as it has so many obvious benefits. I think it also goes without saying that similar to other services (ahem) that implement "Like" that one should be able to "Like" a Confluence page from ANYWHERE (including JIRA) through the REST interface. Cheers

            Chad Barnes added a comment -

            This is a pretty obvious escape - one that affects many of our JIRA dashboards.

            Chad Barnes added a comment - This is a pretty obvious escape - one that affects many of our JIRA dashboards.

            Dirk Bromberg added a comment -

            We got the same error after Upgrade to conf 4.2 and jira 5.0.3 ...

            Dirk Bromberg added a comment - We got the same error after Upgrade to conf 4.2 and jira 5.0.3 ...

            Aleksandar Borojevic added a comment -

            Hi, is there a plan to fix this issue soon?
            I don't want to disable like button either.

            Regards,
            Aleksandar

            Aleksandar Borojevic added a comment - Hi, is there a plan to fix this issue soon? I don't want to disable like button either. Regards, Aleksandar

            Deleted Account (Inactive) added a comment -

            We have this issue on our system. It's dissapointing because i don't want to disable the Like feature. Hope you guys fix this otherwise the integration Confluence -> Jira cannot be used.

            Deleted Account (Inactive) added a comment - We have this issue on our system. It's dissapointing because i don't want to disable the Like feature. Hope you guys fix this otherwise the integration Confluence -> Jira cannot be used.

              pcurren Paul Curren
              scahyadiputra Septa Cahyadiputra (Inactive)
              Affected customers:
              19 This affects my team
              Watchers:
              17 Start watching this issue

                Created:
                Updated:
                Resolved: