New issue 504 by char...@ackdev.com: Feature to allow editing of any text
content under /files
http://code.google.com/p/vosao/issues/detail?id=504
Would be great to allow security management & editing of content under
/files by text based or ckedit
A possible alternative path to this would be to allow upload of content
with structure under content pages to use existing editing & security
features.
Upon upload allow choice selecting defaults:
Restful
Template
Publication date (dd.mm.yyyy) 24-hour clock -
Enable comments
Include in search results
Velocity processing
Mediawiki syntax processing
Enable CKEditor
Skip page post-processing
Cache enabled
Page type
Tags
A bulk upload feature is what I'm after
Comment #2 on issue 504 by kinyelo: Feature to allow editing of any text
content under /files
http://code.google.com/p/vosao/issues/detail?id=504
1. You can adjust security restrictions to files and folders under /files
in the "Resources" tab.
2. You can edit text files located in "Resources". In the site
configuration there is a config option for text files extensions. Currently
you can freely edit css, js, xml files.
3. You can bulk upload by importing ZIP file.
4. It's possible to create Vosao VZ file by third party tools. Actually
it's a ZIP archive containing folders and xml files.
Searched around a bit for #4 seems more trouble than it's worth - can you
give me some guidelines to pass along to one of my coders on where to start
code wise to read a zip file and create the dependences needed for bulk
uploaded content to show up in /cms/pages.vm ?
BTW this is the sort of feature that may make adoption of this product much
easier for those with existing content vs creating everything from scratch.
Searched around a bit for #4 seems more trouble than it's worth - can you
give me some guidelines to pass along to one of my coders on where to start
code wise(high level pseudo code pls) to read a zip file and create the
dependences needed for bulk uploaded content to show up in /cms/pages.vm ?
BTW this is the sort of feature that may make adoption of this product much
Simple way is to export to VZ file and then look inside.
It will contain some config xmls in the root and page content in the
/page/*,
templates will be in /theme/* and all other folders will be from resources.