-
Bug
-
Resolution: Fixed
-
Medium
-
4.3.7, 5.5, 5.7, 5.10.8, 6.6.0, 6.8.1
-
None
-
6
-
1
-
Issue Summary
In email notifications when the content of a page is displayed, all Confluence internal links (attachments, pages,...) are wrong and only point to the address http://server.base.url/#.
For issues regarding anchor links in the notifications mail, watch the following bug report: CONFSERVER-58737
Steps to Reproduce
- Have a confluence that has a mail server
- Create a page that contains a link of the following
- Link to another page
- Link to attachments
- Send the content of that page in a mail notificaitons
Expected Results
Clicking the link will take you to the correct link
Actual Results
The link does not work and only take you to a link with the following address
http://server.base.url/#
Notes
Links to external pages (i.e.: http://www.google.com) work as expected.
Workaround
No workaround
- causes
-
CONFSERVER-47777 Links to Confluence pages are broken in answer notifications
-
- Closed
-
- is duplicated by
-
CONFSERVER-33506 Links broken in Confluence "edited comment" email notifications
-
- Closed
-
-
CONFSERVER-33981 invalid links on notification email when editing an existing page
-
- Closed
-
- is related to
-
CONFSERVER-58737 Anchor links in mail notifications are not working correctly
-
- Gathering Impact
-
- relates to
-
CONFSERVER-37189 ac:link broken links in E-Mail notifications
-
- Closed
-
-
CONFSERVER-9435 Anchor link within an email notification is invalid
-
- Closed
-
-
CONFSERVER-33872 Links to pages and anchors are broken after Space/Page export to Word doc
-
- Gathering Impact
-
-
CONFSERVER-43401 Change to link permission check when rendering pages
- Closed
- was cloned as
-
CONFSERVER-40262 Internal Confluence links in notification email not correct
-
- Closed
-
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
[CONFSERVER-33673] Internal Confluence links in notification email not correct
Link | New: This issue is related to CONFSERVER-58737 [ CONFSERVER-58737 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Needs Triage [ 10030 ] | New: Closed [ 6 ] |
Description |
Original:
In email notifications when the content of a page is displayed, all Confluence internal links (attachments, pages,...) are wrong and only point to the address {{[http://server.base.url/#]}}.
Links to external pages (i.e.: [http://www.google.com|http://www.google.com/]) work as expected. h4. Update 11/16/2018: It appears that this fixed bug has regressed. When viewing the underlying URL of an anchor link embedded within a task notification email, the URL appears in the following format: <base-url>/#pagename-anchorname . When you click on a link like this, Confluence does not display a page. According to [Anchors|https://confluence.atlassian.com/conf68/anchors-947170225.html], the format should be like: {{[<base-url>/display/spacekey/pagename#pagename-anchorname|http://myconfluence.com/display/spacekey/pagename#pagename-anchorname]}} h4. Steps to reproduce: * Create a page. * Create an anchor link. * Create a task that includes a reference to the anchor link. * Assign task to a user. * In resulting email notification, view and click on anchor link contained therein. Tested in 5.10.8, 6.6.0 and 6.8.1 |
New:
h3. Issue Summary
In email notifications when the content of a page is displayed, all Confluence internal links (attachments, pages,...) are wrong and only point to the address {{[http://server.base.url/#]}}. For issues regarding anchor links in the notifications mail, watch the following bug report: CONFSERVER-58737 h3. Steps to Reproduce # Have a confluence that has a mail server # Create a page that contains a link of the following ## Link to another page ## Link to attachments # Send the content of that page in a mail notificaitons h3. Expected Results Clicking the link will take you to the correct link h3. Actual Results The link does not work and only take you to a link with the following address {code} http://server.base.url/# {code} h3. Notes Links to external pages (i.e.: [http://www.google.com|http://www.google.com/]) work as expected. h3. Workaround No workaround |
Support reference count | Original: 5 | New: 6 |
Support reference count | New: 5 | |
UIS | New: 1 |
Description |
Original:
In email notifications when the content of a page is displayed, all Confluence internal links (attachments, pages,...) are wrong and only point to the address {{[http://server.base.url/#]}}.
Links to external pages (i.e.: [http://www.google.com|http://www.google.com/]) work as expected. h4. Update 11/16/2018: It appears that this bug has reappeared. When viewing the underlying URL of an anchor link embedded within a task notification email, the URL appears in the following format: <base-url>/#pagename-anchorname . When you click on a link like this, Confluence does not display a page. According to [Anchors|https://confluence.atlassian.com/conf68/anchors-947170225.html], the format should be like: {{[<base-url>/display/spacekey/pagename#pagename-anchorname|http://myconfluence.com/display/spacekey/pagename#pagename-anchorname]}} h4. Steps to reproduce: * Create a page. * Create an anchor link. * Create a task that includes a reference to the anchor link. * Assign task to a user. * In resulting email notification, view and click on anchor link contained therein. Tested in 5.10.8, 6.6.0 and 6.8.1 |
New:
In email notifications when the content of a page is displayed, all Confluence internal links (attachments, pages,...) are wrong and only point to the address {{[http://server.base.url/#]}}.
Links to external pages (i.e.: [http://www.google.com|http://www.google.com/]) work as expected. h4. Update 11/16/2018: It appears that this fixed bug has regressed. When viewing the underlying URL of an anchor link embedded within a task notification email, the URL appears in the following format: <base-url>/#pagename-anchorname . When you click on a link like this, Confluence does not display a page. According to [Anchors|https://confluence.atlassian.com/conf68/anchors-947170225.html], the format should be like: {{[<base-url>/display/spacekey/pagename#pagename-anchorname|http://myconfluence.com/display/spacekey/pagename#pagename-anchorname]}} h4. Steps to reproduce: * Create a page. * Create an anchor link. * Create a task that includes a reference to the anchor link. * Assign task to a user. * In resulting email notification, view and click on anchor link contained therein. Tested in 5.10.8, 6.6.0 and 6.8.1 |
Affects Version/s | New: 6.8.1 [ 78526 ] | |
Affects Version/s | New: 6.6.0 [ 75132 ] | |
Affects Version/s | New: 5.10.8 [ 63921 ] |
Description |
Original:
In email notifications when the content of a page is displayed, all Confluence internal links (attachments, pages,...) are wrong and only point to the address {{[http://server.base.url/#]}}.
Links to external pages (i.e.: [http://www.google.com|http://www.google.com/]) work as expected. Update 11/16/2018: It appears that this bug has reappeared. When viewing the underlying URL of an anchor link embedded within a task notification email, the URL appears in the following format: <base-url>/#pagename-anchorname . When you click on a link like this, Confluence does not display a page. According to [Anchors|https://confluence.atlassian.com/conf68/anchors-947170225.html], the format should be like: {{[<base-url>/display/spacekey/pagename#pagename-anchorname|http://myconfluence.com/display/spacekey/pagename#pagename-anchorname]}} |
New:
In email notifications when the content of a page is displayed, all Confluence internal links (attachments, pages,...) are wrong and only point to the address {{[http://server.base.url/#]}}.
Links to external pages (i.e.: [http://www.google.com|http://www.google.com/]) work as expected. h4. Update 11/16/2018: It appears that this bug has reappeared. When viewing the underlying URL of an anchor link embedded within a task notification email, the URL appears in the following format: <base-url>/#pagename-anchorname . When you click on a link like this, Confluence does not display a page. According to [Anchors|https://confluence.atlassian.com/conf68/anchors-947170225.html], the format should be like: {{[<base-url>/display/spacekey/pagename#pagename-anchorname|http://myconfluence.com/display/spacekey/pagename#pagename-anchorname]}} h4. Steps to reproduce: * Create a page. * Create an anchor link. * Create a task that includes a reference to the anchor link. * Assign task to a user. * In resulting email notification, view and click on anchor link contained therein. Tested in 5.10.8, 6.6.0 and 6.8.1 |
Description |
Original:
In email notifications when the content of a page is displayed, all Confluence internal links (attachments, pages,...) are wrong and only point to the address {{http://server.base.url/#}}.
Links to external pages (i.e.: [http://www.google.com]) work as expected. |
New:
In email notifications when the content of a page is displayed, all Confluence internal links (attachments, pages,...) are wrong and only point to the address {{[http://server.base.url/#]}}.
Links to external pages (i.e.: [http://www.google.com|http://www.google.com/]) work as expected. Update 11/16/2018: It appears that this bug has reappeared. When viewing the underlying URL of an anchor link embedded within a task notification email, the URL appears in the following format: <base-url>/#pagename-anchorname . When you click on a link like this, Confluence does not display a page. According to [Anchors|https://confluence.atlassian.com/conf68/anchors-947170225.html], the format should be like: {{[<base-url>/display/spacekey/pagename#pagename-anchorname|http://myconfluence.com/display/spacekey/pagename#pagename-anchorname]}} |
Hi Everyone,
Since this ticket was addressing issues in links to pages and attachments which has been fixed in 5.7.4, I've closed this ticket. I've created a new ticket here CONFSERVER-58737 to address the additional issue regarding anchor links that aren't working correctly in mail notifications. Please please watch that issue for further updates.