Hello, i am using Plone for a few small but content based websites and i am really happy with what is provided out of the box.
Plone setup and Content management/editing is real straightforward, not to say easy, and the users provide good feedback about the intuitive interface when they use it to edit their sites and provide content. For me as the maintainer of the Plone system in use it is my job to provide the features the users need, and one of it is a guestbook. While migrating from Plone 3.3 to 4.3.2 the quintagroup.plonecomments comments were successfully converted to plone.app.discussion ones. While digging into the code to see where the requirements i have could be implemented i ended up with the conclusion that the plone.app.discussion package itself is the best place to make the changes or extend. One of the key requirements, so the users tell me, of guestbook-style comments compared to the plone.app.discussion provided comments is the order they apear. A new guestbook entry should appear on top of the others, but with related replies below. This is what the users of my sites tell me. The thing to modify is the way the generator object returns the comments from the IConversation object in the CommentsViewlet. When i subclass this viewlet in my lets say collective.guestbookcomments product, i end up with the following problems: 1: How to implement a way a site manager can decide which content object should have comments, and which guestbook-style comments? When i subclass and overwrite the plone.app.discussion machinery, normal comments would no longer be possible. So i thought of a switch in the properties tab of a content object. But i have no clue how to achieve that, it looks to me digging too deep into Plones internal machinery. Is there a safe and upgrade compatible way to stick a checkbox from an addon product onto content objects? Maybe via an Interface? 2: When i provide new translations via .po files for the guestbook style comments, i just overwrite the plone provided comment ones, too. This is not the way to go, but duplicating the whole discussion machinery to have one for comments and one for guestbookentries just to get proper strings on the labels looks much too heavy for me. So i ended up in that the plone.app.discussion package needs to be extended to cover described use case. But tampering with core plone packages is two levels above my knowledge, sorry. Thanks for any hints and helps and clues ! _______________________________________________ Product-Developers mailing list [email protected] https://lists.plone.org/mailman/listinfo/plone-product-developers
