Currently, the initial LiveFirst import will automatically place non-html files under Assests/uploads/site_name/import location. Alternately, the bulk-upload widget can allow users to upload files at various locations under Assets folder. In this way, it will result in having at least 2 different locations to store these files of the same website.
In order to prevent file cluttering, do you recommend us to move the files stored under uploads folder to the centrally located Files folder after bulk upload?
Do you recommend us to always use bulk upload to upload single file or multiple files?
If we store pdf files under Assets/site_name/pdf folder, how can we configure them to always publish to the root directory of website. For example, publishing Assets/site_name/pdf/test.pdf on CM1 to d:\site_name\pdf folder on web server. On the same token, publishing Sitessite_name/en/index on CM1 to d:\site_name\en folder on web server. How can it be done?
Hi Eric,
Most customers elect to structure their own asset folder tree off of the root Assets directory, in order to keep things intuitive for their end users, and also to allow for more specific workflow assignment. If you were to do this in your case, you could then drag the files that were created in the “Assets/uploads/{site_name}/import” folders into your customized folder tree. Because all content housed in your Assets library (unlike your web_resources directory) are referenced based on a database ID, all managed links pointing to these relocated assets should still resolve.
Once you have this structured Assets library built out, you can use the Bulk Upload gadget to upload new assets into whatever asset folder makes sense for the content you are uploading.
There is no way to configure Percussion to publish content in your Asset library to your server’s root directory – it will always be contained off of a path such as “/Assets/folder”. What is the reason you would want to house your assets at your server’s root?