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

Links in macro bodies not updated on rename page

XMLWordPrintable

      Links in the body of some macros do not get changed when the page is renamed. Worked correctly on 2.5.2 and is broken on 2.6.1. This is important because a site's links could be messed up after renaming and it would be a nightmare to try to find and repair all the damaged links. The puzzling fact is that links get renamed properly inside some macros but not others. I checked a few:

      • Working: panel, section/column, excerpt, color
      • Not working: table-plus (3.3.1), chart (1.8)

      I looked through issues related to rename and did not notice any related changes between 2.5.2 and 2.6.1. Was there some incompatibility introduced that requires a plugin change?

      Simple example:

      {table-plus}
[Rename this page]
{table-plus}

      Related issue is TBL-38

            [CONFSERVER-10058] Links in macro bodies not updated on rename page

            Fred Bunting added a comment -

            Yes, thanks Partha for the update. At least we know someone is listening.

            Fred Bunting added a comment - Yes, thanks Partha for the update. At least we know someone is listening.

            Klaus Feldmann added a comment -

            Thanks for this reply. That gives us at least some hope and let us stay tuned - but please hurry up. Databases are growing and so many workarounds have been already implemented. Cheers.

            Klaus Feldmann added a comment - Thanks for this reply. That gives us at least some hope and let us stay tuned - but please hurry up. Databases are growing and so many workarounds have been already implemented. Cheers.

            Partha added a comment -

            Dear Fred, Carl and Klaus,

            Thank you for your feedback.

            As Klaus pointed out, we are not able to work on this issue for the 3.x branch as the new editor in 4.0 (still being developed) changes everything.
            We believe the issue may be fixed as part of the 4.0 work. If not, we hope to address it soon after the 4.0 release.
            It is definitely high on the bug fixing backlog.

            Please accept my apologies for the inconvenience.

            Kind Regards,
            Partha Kamal

            Partha added a comment - Dear Fred, Carl and Klaus, Thank you for your feedback. As Klaus pointed out, we are not able to work on this issue for the 3.x branch as the new editor in 4.0 (still being developed) changes everything. We believe the issue may be fixed as part of the 4.0 work. If not, we hope to address it soon after the 4.0 release. It is definitely high on the bug fixing backlog. Please accept my apologies for the inconvenience. Kind Regards, Partha Kamal

            Klaus Feldmann added a comment - - edited

            For us and my customers this feature is mandatory too. From my investigation about this issue it seems that Atlassian either like to drop this mandatory feature or that they can only solve this issue with 4.0 new RichText and WikiMarkup editor. I hope the later is at least the case. If I would be a programer at Atlassian I wouldn’t try to fix it in 3.x as 4.0 will be a new Editor from scratch on as I did understand. You see this missing feature on pages at Atlassian confluence documentations – they have broken links too – so they must do know it. They don’t assign this bug, don’t really answer questions about it and they don’t talk about officially. Frustrating for me is not that this bug exists – it is that they do not communicate about it and leave us in a doubt about confluence state – I always keep an I open for any system that provides this feature so far.

            Klaus Feldmann added a comment - - edited For us and my customers this feature is mandatory too. From my investigation about this issue it seems that Atlassian either like to drop this mandatory feature or that they can only solve this issue with 4.0 new RichText and WikiMarkup editor. I hope the later is at least the case. If I would be a programer at Atlassian I wouldn’t try to fix it in 3.x as 4.0 will be a new Editor from scratch on as I did understand. You see this missing feature on pages at Atlassian confluence documentations – they have broken links too – so they must do know it. They don’t assign this bug, don’t really answer questions about it and they don’t talk about officially. Frustrating for me is not that this bug exists – it is that they do not communicate about it and leave us in a doubt about confluence state – I always keep an I open for any system that provides this feature so far.

            Fred Bunting added a comment -

            Hey Atlassian!

            Imagine my frustration as I look at my own comment from June '08 describing how serious and BASIC this bug is ... and two years, 4 duplicate tickets, 40 pleading voters, and several Confluence versions later it hasn't even been assigned to someone to work on.

            I notice by pure coincidence that it is almost 3 years to the day since this issue was first reported.

            Is there anything we can do to make this a priority?

            Fred Bunting added a comment - Hey Atlassian! Imagine my frustration as I look at my own comment from June '08 describing how serious and BASIC this bug is ... and two years, 4 duplicate tickets, 40 pleading voters, and several Confluence versions later it hasn't even been assigned to someone to work on. I notice by pure coincidence that it is almost 3 years to the day since this issue was first reported. Is there anything we can do to make this a priority?

            Carl Gherardi added a comment -

            Watching this task as the one I was watching was marked as a duplicate of this.

            This is still an issue in v4, and is preventing at least 1 interesting plugin - numbered-headings from functioning.

            Carl Gherardi added a comment - Watching this task as the one I was watching was marked as a duplicate of this. This is still an issue in v4, and is preventing at least 1 interesting plugin - numbered-headings from functioning.

            Robbie Lee added a comment -

            This is an issue for us when it comes to panels:

            {info}

            ,

            {wanring}

            ,

            {note}

            .

            Robbie Lee added a comment - This is an issue for us when it comes to panels: {info} , {wanring} , {note} .

            Jonathan Simonoff added a comment -

            This deficiency has bitten me again in a bad way, this time with a user macro with an unrendered body that emits wiki format, which I thought didn't have this problem.

            We're using 3.1.1.

            Come one! Help!

            Jonathan Simonoff added a comment - This deficiency has bitten me again in a bad way, this time with a user macro with an unrendered body that emits wiki format, which I thought didn't have this problem. We're using 3.1.1. Come one! Help!

            Egon Nijns added a comment -

            come on Atlassian, this should be fixed!

            (or at least investigated so that someone could come up with a workaround for plugin developers to implement)

            Egon Nijns added a comment - come on Atlassian, this should be fixed! (or at least investigated so that someone could come up with a workaround for plugin developers to implement)

            David Goldstein added a comment -

            +1. Please get to the bottom of this. This was a fundamental selling point of Confluence w/ our clients. Thx.

            David Goldstein added a comment - +1. Please get to the bottom of this. This was a fundamental selling point of Confluence w/ our clients. Thx.

              smansour Sherif Mansour
              bob.swift@charter.net Bob Swift
              Affected customers:
              51 This affects my team
              Watchers:
              35 Start watching this issue

                Created:
                Updated:
                Resolved: