search

zillo32 / vosao

Automatically exported from code.google.com/p/vosao
GNU Lesser General Public License v2.1
0 stars 0 forks source link

Feature to allow editing of any text content under /files #504

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
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

Original issue reported on code.google.com by char...@ackdev.com on 30 Jul 2011 at 1:19

GoogleCodeExporter commented 8 years ago 
A bulk upload feature is what I'm after

Original comment by char...@ackdev.com on 30 Jul 2011 at 1:25

GoogleCodeExporter commented 8 years ago 
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.

Original comment by kinyelo@gmail.com on 30 Jul 2011 at 1:52

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
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 
easier for those with existing content vs creating everything from scratch.

Original comment by char...@ackdev.com on 30 Jul 2011 at 3:02

GoogleCodeExporter commented 8 years ago 
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.

Original comment by kinyelo@gmail.com on 30 Jul 2011 at 6:41