[MGNLEE-84] UUID's not correct in 'Link' paragraph when a page is copied Created: 12/Feb/08 Updated: 19/Mar/10 Resolved: 19/Mar/10 |
|
| Status: | Closed |
| Project: | Magnolia DX Core |
| Component/s: | build / bundling |
| Affects Version/s: | 3.5.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Chris Allan | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
3.52EE, bdb |
||
| 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 the versionining gets corrupts you are unable to activate pages, so it is neccessary to copy and paste a branch, delete the original branch, and change the name of the new branch to the original name. I have a page with a link paragraph on, linking to another magnolia page in the same branch of the web repository. When I go through the described steps of copy and replace, the link no longer works, providing a link to a broken UUID, rather than to the correct path in the repository. |
| Comments |
| Comment by Boris Kraft [ 12/Feb/08 ] |
|
Did you try exporting, deleting, importing the branch instead? |
| Comment by Chris Allan [ 12/Feb/08 ] |
|
No, I haven't tried that. This is not really a problem for us, but definitely looks like a bug. |
| Comment by Magnolia International [ 19/Mar/10 ] |
|
Well, the links point to the UUIDs of nodes you just deleted, so it's hardly a bug of the software. These kinds of problems could be solved or avoided via link checkers or processors. Closing as outdated; please reopen if this is still a (support?) issue. |