[EXTDAM-358] Navigating into S3 folders is breaking proper creation of component in JCR Created: 20/May/22 Updated: 16/Aug/22 Resolved: 13/Jun/22 |
|
| Status: | Closed |
| Project: | External DAMs |
| Component/s: | s3 |
| Affects Version/s: | 1.1.3 |
| Fix Version/s: | 1.1.4, 1.2.0 |
| Type: | Bug | Priority: | Major |
| Reporter: | Raphael Falvo | Assignee: | Jesus Alonso |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | VN-Testing, cs-bk | ||
| Σ Remaining Estimate: | Not Specified | Remaining Estimate: | Not Specified |
| Σ Time Spent: | 3h 35m | Time Spent: | 35m |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Attachments: |
|
||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||
| Sub-Tasks: |
|
||||||||||||||||||||
| Template: |
|
||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||
| Task DoD: |
[X]*
Doc/release notes changes? Comment present?
[X]*
Downstream builds green?
[X]*
Solution information and context easily available?
[X]*
Tests
[X]*
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: | |||||||||||||||||||||
| Epic Link: | AuthorX Support | ||||||||||||||||||||
| Sprint: | AuthX 11 | ||||||||||||||||||||
| Story Points: | 2 | ||||||||||||||||||||
| Team: | |||||||||||||||||||||
| Description |
|
Using an s3 link within a component is preventing component to be created properly in JCR. The double click on a folder/bucket makes also a strange reload of the background page.
You can find attached a light module EXTDAM-358-lm.zip
[EDIT on 20/05/2022 12:03]: I just updated the light module, adding a standalone s3 dam link field within the Link component form, to show that it doesn't relate to switchable field. You can also see that s3 link nodes are properly saved in JCR when used at page level. You can edit page properties of a basic page, a s3 link field is present there. |
| Comments |
| Comment by Roman Kovařík [ 20/May/22 ] |
|
Discovery: Since |
| Comment by Raphael Falvo [ 24/May/22 ] |
|
Hello rkovarik , I had a quick look to the patch you attached, and wanted to let you know that this change actually breaks the navigation. It's not possible anymore to navigate into buckets/folders. I know that this is not the final implementation, it's an exploration patch, but I just wanted you to be aware of that |