Details
-
New Feature
-
Resolution: Won't Do
-
Major
-
None
-
None
-
None
-
None
-
-
Empty show more show less
Description
This is usefull for smaller applications or for an Magnolia-Wiki implementation
- a context parameter defines the mode in which the instance is running
- activation does not transfer the data, but changes the flag
- public view checks the activation flag
see later discussion: http://jira.magnolia.info/browse/MAGNOLIA-411
Snippet from list post:
—
I uploaded my patch to http://www.punainen.org/~janne/magnolia-single.patch and my web.xml to http://www.punainen.org/~janne/web.xml. The modifications also require moving of admindocroot and admintemplates to directory "edit".
After that site can be browsed normally for example from url http://www.site.com/features.html, and then switch to edit mode by modifying the url to http://www.site.com/edit/features.html.
I was first thinking about using two repositories as you suggested, but that would need a little bit more of tweaking mainly on Syndicator. I think that would take an another hour of work, so not really a huge effort. I'm not really familiar with magnolia or it's codebase, but I think the decision of which repository is in use can be done in the Aggregator.
– end snipped