[MAGNOLIA-1343] Relative image paths produced by <cms:out> result in broken images for certain URLs Created: 05/Feb/07  Updated: 23/Jan/13  Resolved: 27/Nov/07

Status: Closed
Project: Magnolia
Component/s: taglibs
Affects Version/s: 3.0.1
Fix Version/s: 3.5 RC2

Type: Bug Priority: Minor
Reporter: Miranda Jones Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

When outputting the content from a fckEdit control with <cms:out>, the link and image paths are made relative by the taglib. This works ok when accessing the page via a URL like "/foo.html" or "/foo", but when accessing the page via a URL like "/foo/" (with the ending slash) the relative image path results in a broken image.

To fix in my local environment, I adapted the code from info.magnolia.cms.gui.dialog.DialogFckEdit.convertToView(String), which makes the href and img paths absolute for the fckEdit window, for info.magnolia.cms.taglibs.Out, so that image paths are made absolute when outputting the content with <cms:out>.



 Comments   
Comment by Philipp Bracher [ 06/Feb/07 ]

Link resolution in 3.1 will change. There we can fix this properly. Pehaps we make a backport.

Comment by Magnolia International [ 22/Nov/07 ]

Will check this for RC2 - if no change required, will reset "fix version" to RC1.

Comment by Philipp Bracher [ 27/Nov/07 ]

image links are resolved as absolute path by default now

Generated at Mon Feb 12 03:26:00 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.