you should try to contribute your enhancements to Magnolia so... this way you don't have to maintain custom code through releases ;)
fabrizio On 9/28/05, Kyle Gabhart <[email protected]> wrote: > Ha! If only it were that easy. My customized version of Magnolia has > the following enhancements: > > - Delete function restricted to all except for superuser > - The ability to deny access to certain parts of the tree (prior to the > deny setting be added to magnolia security roles) > - Security authentication via LDAP rather than the built-in Magnolia > security > - The definition of a 'publisher' role which grants the ability to > activate/deactivate content (non-publishers can only edit content) > - LDAP-secured pages. Every page can be configured via the page > properties to be open, secure, or hidden (hidden pages will only appear > in the navigation tree if you have sufficient security privileges). > - Content searching via nutch (this was prior to the Lucene integration) > - A directory search mechanism (connects to LDAP and provides full > directory searching capabilities across all employee attributes) > - 7 custom templates > - a host of customized dialogs > - A "recent content updates" section of the home page that shows the > last 5 content updates along with the author, the page name, a link, and > the date/timestamp > - A news management and publishing mechanism > > So, I need to do a bit of porting and testing to get things working. :) > > -KG > > > Fabrizio Giustina wrote: > > >Hi Kyle > > > >On 9/28/05, Kyle Gabhart <[email protected]> wrote: > > > > > >>Is there sufficient compatibility between the 2.0 APIs and the 2.1 > >>repository to allow them to coexist? I was hoping that I could go ahead > >>and upgrade my 2.0 app with the latest repository (70% reduction in the > >>tree, increased reliability, etc.) and then migrate in the new code once > >>I have finished my customizing and testing. > >> > >> > > > >the "70% reduction in the tree" depends from the new Magnolia code, > >not from the repository... I will suggest you to try copying your > >templates and activate your content to a 2.1 instance: for simple > >templates the migration should be easy, fixes in the code should be > >pretty limited. > > > >fabrizio > > > >---------------------------------------------------------------- > >for list details see > >http://www.magnolia.info/en/magnolia/developer.html > >---------------------------------------------------------------- > > > > > > > > ---------------------------------------------------------------- > for list details see > http://www.magnolia.info/en/magnolia/developer.html > ---------------------------------------------------------------- > ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
