[MGNLSTK-1403] Download list does not work properly Created: 14/Jul/14 Updated: 16/Apr/15 Resolved: 21/Nov/14 |
|
| Status: | Closed |
| Project: | Magnolia Standard Templating Kit (closed) |
| Component/s: | None |
| Affects Version/s: | 2.8 |
| Fix Version/s: | 2.8.6 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Andreas Doebeli | Assignee: | Federico Grilli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | support | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||
| Template: |
|
||||||||||||||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||||||||||
| Description |
|
The download list component lists all in the dam available documents. Furthermore, the path selection dialog shows an error after selecting a node that is not an asset. Steps to reproduce:
I'm using: Browser: Firefox 30.0 (not tested on others, but it seems to be a backend problem) |
| Comments |
| Comment by Andreas Doebeli [ 01/Sep/14 ] |
|
Are there any news on this issue or plans to resolve it? This behavior is still reproducable on the demo. |
| Comment by Zdenek Skodik [ 09/Oct/14 ] |
|
Andreas, the first part of folder selection has been fixed by |
| Comment by Christoph Meier [ 10/Oct/14 ] |
|
What should be done if the user selects a folder? Magnolia 4.5 does it like (c). => I will implement (c). |
| Comment by Christoph Meier [ 14/Oct/14 ] |
|
Added a new field (checkbox) which allows to list all children (and sub-children) of a folder or the direct descendants only. => Bootstrap and ModuleVersionHandler has been adapted. |
| Comment by Christoph Meier [ 27/Oct/14 ] |
|
Merged master into the feature branch ' |
| Comment by Christoph Meier [ 27/Oct/14 ] |
|
To ease integration and keep git history short, i've created a new branch from master and added the changes to this new branch. |
| Comment by Federico Grilli [ 18/Nov/14 ] |
|
As found by a user on the forum https://forum.magnolia-cms.com/forum/thread.html?threadId=ca1ef931-ae0c-47ee-9482-cd97a41ea80c the feature basically didn't make into master (due to some mishap during integration) and thus was not released. |
| Comment by Mikaël Geljić [ 19/Nov/14 ] |
|
i18nBasename property was added in bootstrap, but nothing was done in MVH in this regard. This will trigger a migration diff. |