[MAGNOLIA-3391] Invalid references in copied richtext fields Created: 16/Nov/10 Updated: 19/Dec/16 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | core, fckeditor |
| Affects Version/s: | 4.3.8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major |
| Reporter: | Jan Christian Haddorp | Assignee: | Unassigned |
| Resolution: | Won't Do | 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 |
|
One of our paragraphs contains a richtext field. If you add an image into the richtext field using the FckEditor and then copy the enclosing page everything looks fine at first sight. But the new page this references to the original embedded image. The image has been copied as well; however the references inside the richtext field have not been updated. As long as you keep the original page you won't recognize anything. But if removing the original page you get problems inside the copy... Can you please fix the copy process. While coping richtext fields including image references have been adjusted. |
| Comments |
| Comment by Philipp Bärfuss [ 17/Dec/10 ] |
|
We store the binary link as a uuid link. Similar to all other links they don't get rewritten if the content gets copied. While this is normally an acceptable default behavior, it is not in this particular case. Unfortunately it might be a bit tricky to fix this. Ideally we would rewrite the content on copy. |
| Comment by Michael Mühlebach [ 04/Nov/15 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |