-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
5.4.4, 5.5.2, 5.5.3, 6.4.3, 6.14.3, 6.15.9
-
Confluence standalone
-
14
-
Severity 3 - Minor
-
2
-
NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.
Consider the following setup:
- A confluence page contains the 'Blog Posts' macro with the display setting set to 'excerpts'
- A blog post that does not have an excerpt set, and does contain a URL within its first few sentences
Result:
The URL is displayed in full, rather than the link text and HTML link (like what is displayed if an excerpt were to contain a link).
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
-
- Closed
-
-
-
- Closed
-
[CONFSERVER-34197] Blog Posts Macro renders URLs as text when content = excerpts and post contains no excerpt
Also affects v6.15.9 - as expected...
5 years as yet.
Came across this thing here after filing CSP-262419.
Pretty much remebers me of CONFSERVER-57934 which has a similar timeline and, of course, doesn't have a fix version either, so it still impairs not only v6.15.9 but any version, even the most recent v7.0.4.
Dunno what to say...
I implemented a "News" display (Blog in separate space and display the Blog entries with excerpt in the main page of other spaces) and get the same issue: Links, whether inserted by "recently viewed" or by "shared" will be shown by macro BLOG POSTS as text.
So our users cannot get directly from the Blog Post display to the mentioned link directly but have first to select the Blog Post in which the correct link is exposed.
This should be corrected...
Addendum: Workaround is to put the whole text of a blog entry in an EXCERPT macro, so the links will be kept by BLOG POSTS. As we use these blog entries for short "News", I will change the status from "necessary" to "inconvenient" 
The error is still very topical. Unfortunately I can't increase the priority.
Can you please take a look at this bug?
Please prioritize higher after all these years.
Confluence Server 6.4.3
such a small error, which can be easily corrected.
unbelievable that this takes so much time. not a good approach for atlassian
GATHERING IMPACT? since 4 years?
PLEASE FIX this stupid bug!!!!
will take you 10 minutes, right?
Unbelievable not to solve issue like this so long.... We all sue Microsoft not to release update for own bugs after few weeks and this bug it still unsolved after FOUR YEARS????? How we can sell Confluence to new customers, if this didnt work and many times its used on company intranet first page.....
It's just weak not fixing simple but obvious bugs like this one... 
It's just weak not fixing simple but obvious bugs like this one...
When will the bug be fixed?