google-code-export / digitalus-cms

Automatically exported from code.google.com/p/digitalus-cms
1 stars 1 forks source link

adding modules to pages from the back end #171

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
it would be nice to have a feature to add modules from the back end rather than 
editing the layout file 
or 
to have a feature that enables editing of the layout files

Original issue reported on code.google.com by jspe...@gmail.com on 25 Jan 2011 at 10:48

GoogleCodeExporter commented 9 years ago
That might generate problems with file access rights

Original comment by lowtower1974@gmail.com on 31 Jan 2011 at 10:59

GoogleCodeExporter commented 9 years ago
didn't get you. i mean if you are hosting a web site you can change file 
permissions when ever you want only for editing purposes and even you can show 
weather a file can be edited or not 

Original comment by jspe...@gmail.com on 31 Jan 2011 at 12:09

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
i have a better idea why not store the layout files in the db as an xml file or 
what ever and use the javascript editors (ckeditor,fckeditor,...) for editing 
them ....... ..........

Original comment by jspe...@gmail.com on 4 Feb 2011 at 10:01

GoogleCodeExporter commented 9 years ago
Hello jspeshu,

I am not an expert with javascript editors like ckeditor, but I think there 
might be a problem with the Digitalus-Tags.
The latest versions of digitalus make use of the digitalus-tags like 
<digitalusNavigation /> and <digitalusControl />.
How would ckeditor handle these tags?

Cheers,
LT.

Original comment by lowtower1974@gmail.com on 16 Mar 2011 at 3:18

GoogleCodeExporter commented 9 years ago
i don't get you..

Original comment by jspe...@gmail.com on 17 Mar 2011 at 6:18

GoogleCodeExporter commented 9 years ago
Well, a key thing in the templates is the use of the already mentioned 
digitalus-tags. They are something like placeholders for ZF view helpers.
That means that Digitalus parses the template and replaces the digitalus-tags 
with (html-)content.
If I created the template with e.g. ckeditor I wouldn't have the possibility to 
add such a tag in the wysiwyg-mode as ckeditor doesn't know about these tags.
Thus, I would have to switch to the source-editor and wouldn't really have won 
anything.
Plus, I don't kow, whether ckeditor changes the tags when saving them.
In general, the templates are designed in a way that design and business logic 
are separated. All information needed for designers are compacted in the 
template directory. I wouldn't like to see the layout.phmtl files in a 
different place than the css files etc.

Hth,
LT.

Original comment by lowtower1974@gmail.com on 17 Mar 2011 at 3:47