Timeline for Accessing pdf as a Component using url
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 23, 2017 at 18:15 | comment | added | Rick Pannekoek |
You would have to change the implementation of class Localization (part of the DXA Framework) so it can use multiple regular expressions to detect Static Content Items. See github.com/sdl/dxa-web-application-dotnet/blob/master/…
|
|
| Jan 23, 2017 at 17:35 | comment | added | Suresh | Hi Rick, As per the direction we were asked to have as /documents only. Is there anyway we can achieve this. | |
| Jan 19, 2017 at 18:17 | comment | added | Rick Pannekoek |
That is correct; DXA assumes that all Static Content Items are in a single URL subtree. Would it be a problem to use, say /media/images and /media/documents ?
|
|
| Jan 18, 2017 at 21:22 | comment | added | Suresh | Multimedia URL can be used for setting only path which we are already using for Images. For pdfs, we want to have different path like /document. DXA is able to recognize images since it is configured in image path in publication properties. DXA is not able to recognize pdf's and it is searching for views and redirecting to 404 page. How DXA can recognize custom asset folder /documents/. | |
| Jan 18, 2017 at 21:19 | comment | added | Suresh | Hi Rick, We had created a separate documents structure group where the pdf files are placed. What I see for images, we can set the path in tridion. | |
| Jan 17, 2017 at 20:11 | history | answered | Rick Pannekoek | CC BY-SA 3.0 |