Page History
...
Magnolia WebDAV module is deprecated in the 5.7 branch. Deprecation means that we stop bundling the WebDAV module with the product. You can still get the code from our Nexus repository but we don't recommend using it anymore. The deprecated status lasts for one year. On June 20, 2019 we will remove the module from the product completely and donate it to the community on the Magnolia Forge.
The purpose of the module was to access the Magnolia repository through the The purpose of the module was to access the Magnolia repository through the WebDAV API, typically allowing users to edit resources and templates on the file system.
...
- To edit CSS files or template scripts on the file system, use light modules. You can edit any light module resources on the file system. Use your favorite text editor tool or an IDE that supports syntax highlighting and provides helper functions.
- To edit Groovy scripts on the file system, use the Groovy console. The console provides autocompletion, keyboard shortcuts and help but is not a complete replacement for a local script editor. You can also create the Groovy script locally, run tests on it locally, and then paste it into AdminCentral.
To access DAM assets on the file system, for example with Photoshop:
Put assets that you need to edit often such as logos and banners into a light module, commit the light module into Git, and clone it to a local file system.
Put assets that you need to edit only once such as product images into the DAM.
To upload multiple documents into the DAM:
Use the zip upload.
Create a local folder and a custom import command that ingests files from the folder.
Use Amazon S3 for asset storage. Mount the S3 bucket as a drive letter on your local file system.
...
.
| Anchor | ||||
|---|---|---|---|---|
|
...
Overview
Content Tools