You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be incredibly useful if it was possible to use webdav to add/update files in a static resource directory.
plone.resource requires that directories provide IObjectManager and that files are instances of OFS.Image.File. It provides the following methods to create the correct types:
plone.app.theming makes use of the importZip method when uploading a new theme.
I'd like to be able to use webdav to connect to the server, open portal_resources/theme, then copy or update a theme from my local filesystem using my webdav client.
If you attempt to use Webdav (or FTP), the PUT method (webdav.NullResource) creates the wrong file types and then fails.
I think to allow this, we possibly need a custom PUT_factory for the static resource directory. Does this idea seem reasonable/possible? I am happy to implement it if someone can point me in the right direction.
The text was updated successfully, but these errors were encountered:
It would be incredibly useful if it was possible to use webdav to add/update files in a static resource directory.
plone.resource requires that directories provide IObjectManager and that files are instances of OFS.Image.File. It provides the following methods to create the correct types:
plone.app.theming
makes use of theimportZip
method when uploading a new theme.I'd like to be able to use webdav to connect to the server, open portal_resources/theme, then copy or update a theme from my local filesystem using my webdav client.
If you attempt to use Webdav (or FTP), the PUT method (webdav.NullResource) creates the wrong file types and then fails.
I think to allow this, we possibly need a custom
PUT_factory
for the static resource directory. Does this idea seem reasonable/possible? I am happy to implement it if someone can point me in the right direction.The text was updated successfully, but these errors were encountered: