We're about a week out from releasing a beta of pkContextCMSPlugin,
which is a Doctrine-based plugin that borrows from sfSimpleCMS,
although we've also gone in new directions - most importantly, custom
slot types are implemented as Symfony modules, and Doctrine column
aggregation inheritance can be used for storage (although the old
serialize/unserialize approach is often suitable too). Mainly we just
need to clean up a few dependencies on other plugins and make sure
those are also available.

We'll definitely be interested in third-party contributions,
especially where internationalization is concerned.

-Tom

On Sat, Feb 21, 2009 at 2:13 PM, Sebastian Schulze
<[email protected]> wrote:
>
> Hey around.
>
> We had a little discussion going on at #symfony-de today,
> if there is a suitable CMS implementation around that can
> be used with Doctrine as an ORM.
> So far - there is an ancient fork of the sfSimpleCMSPlugin
> for Doctrine, but it's completely outdated and (as I would say)
> far from being 1.1-compatible.
>
> The one that looks most promising - to me - is the sfInstantCMS
> Plugin,
> but that one is Propel-based - so that one's also out (for me).
>
> So the short way would be to create another fork of a plugin that
> suits that
> case best and port that to doctrine, but thats far from DRY - and
> would
> probably end up in an unmaintained branch.
>
> Now what are your experiences or ideas? I'm sure there
> aren't only the few guys hanging around at #symfony-de that are in
> need
> of a feasible symfony + doctrine cms-solution. :-)
>
> Sebastian
>
>
> >
>



-- 
Tom Boutell

www.punkave.com
www.boutell.com

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/symfony-devs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to