Cotonti / Open Source PHP Content Management FrameworkContent Management Framework

Foren / Cotonti / Core Labs / In Progress / NEW Comments System

Lombi
#1 21. August 2008, 01:26
Let's make this topic the place to gather oppinions on what the new/future/better commenting system should look like....

First of all some improvements to the existing code, if code is kept:

FOR SKINNERS
- make it templateable (only username is given to the xTemplate, should have at least the amount of tags that exist in the forum.posts code. My vote is that a forum post and a page post should not be/look different.

- make it count somewhere (again if you have pagecount plugins for whatever reasons (people downloading stuff, access to new categories, whatever) you could give your users actual reason to comment, but maybe to just have a bigger number in the "comments count")

- gravatar support (or even integration with cotonti avatars??) - more gravatar ideas in the next section

FOR DEVELOPERS
- AJAX EDIT COMMENTS: http://www.raproject.com/wordpress/wp-ajax-edit-comments/ (would make things so much easier)

- http://www.justinshattuck.com/comment-relish/ (omg i would merry people for this functionality, perhaps even cron-ed to a 3 month period on when it would mail the user if he didnt register yet that THANK YOU AGAIN AND COME VISIT THE SITE AGAIN...)

- Post Comments Via AJAX -> http://wordpress.org/extend/plugins/moojax-comment-posting/ (mootools, sorry Vlad)

- even better avatar support for guests -> http://kamajole.dk/plugins/mbla/ (combining mybloglog and gravatar)

- even better seditio/cotonti integration -> if registered user's email contains a gravatar and he didnt upload one, get it and apply it to his account. This could even be done on registration.add.done!

FOR PEOPLE THAT ADMIRE THE WAY DRUPAL/WORDPRESS WORKS
- threaded comments (while i'm aware that it's a 50/50 thing it's a clear way to see what replies go where, but in any case, this is the CODE -> http://meidell.dk/archives/2006/12/19/brians-threaded-comments-159/)

- subscribing to comments (http://www.theblog.ca/?p=21 what a great idea)

- Publish The Commenter's Latest Headline (a way to say thank you for commenting -> http://www.fiddyp.co.uk/commentluv-wordpress-plugin/)

- list recent comments (http://freepressblog.org/wordpress-plugins-2/wordpress-recent-comments-plugin-widget/)

I'm sure there a lots more! Your thoughts?
<a href="http://www.domenlo.com">Surreal Art</a>
Trustmaster
#2 21. August 2008, 04:21
I shall buy someone a cookie to implement it all :yes

The only problematic thing is putting user's comment count into database. Basically it would require adding one more field to sed_users, which is somewhat rude for an "optional plugin". But seems like 90% of sites would like to have this plugin enabled.
May the Source be with you!
Lombi
#3 21. August 2008, 21:02
Right. Also would could just stick everything into the postcount, only serialized. So no real action needed, just unserialize when needed.
<a href="http://www.domenlo.com">Surreal Art</a>
Trustmaster
#4 22. August 2008, 06:10
Postcount is INT, isn't it? Anyways, comcount could be done this way if no special field available:
SELECT COUNT(*) FROM sed_comments WHERE com_author = {$usr['id']}
May the Source be with you!

Dieser Beitrag wurde von Trustmaster (am 3. September 2008, 16:29, vor 13 Jahre) bearbeitet
Ronni
#5 27. März 2009, 05:33
Instead of showing the count-comments-link like this "Icon(x)", it would be nice with this format: "1 comment" and "2 comments" etc. Maybe in config you could choose between these?
Kilandor
#6 27. März 2009, 06:51
Don't forget future comment system will be a module, so some of the above which likely will never be put in, can be done by someone, then the different comment module can be dropped in.
Ronni
#7 28. März 2009, 06:22
When you say module, you mean a normal Cotonti plugin right?
I think it's a good idea to move it from core to plugin!
Elgan
#8 28. März 2009, 07:38
but the comments plugin int he future should still be hookable. or some plugins may fail and not all want to "replace" a whole plugin.

as the plugin will be used by so many is it really needed to become a plugin? just imrpove the abilities of the comments. I agree it should be exactly like forum post. Its going to be that bit slowly as a plugin. how many core hooks for comments are there? really? just improve it to be like the forum post which isnt a plugin and its sorted.


I have a plugin that uses comments, I have writtena subscribe section into the plugin too, which pms the owner when they geta comment and then you can "subscribe" to that item, with an option for when either the auther or anyone repliesm, get a pm, or email. All this will be broken if i lose the hooks it uses. Last time i rewrote the whole comment section for myself to be identical to the forum post section with a few tid bits.

What do we really gain from not just improving it?
what do we lose ?
musiconly
#9 28. März 2009, 19:27
# Elgan : which pms the owner when they geta comment and then you can "subscribe" to that item, with an option for when either the auther or anyone repliesm, get a pm, or email.

Sorry for offtopic, but can this be used with regular pages - so it notifies the OWNER of a page.
Kort
#10 28. März 2009, 20:03
I'm sure there a lots more! Your thoughts?
Built-in "Comments for Guests" CAPTCHA-protected feature
Seditio.by - создание сайтов, разработка плагинов и тем для Котонти
Elgan
#11 28. März 2009, 21:27
# musiconly : Sorry for offtopic, but can this be used with regular pages - so it notifies the OWNER of a page.

probably yeah, i just filter out for use with my config and to make sure the part is my plugin.
Sergeich
#12 30. März 2009, 16:32
Lombi, agree with your suggestions :)
Born in the Wild Wild East!
code_87
#13 8. Mai 2009, 08:45
captcha for guest comment and quote comments? and comment voting??
[b]I give you stuffs... and my stuffs i give you![/b] :D
esclkm
#14 8. Mai 2009, 13:22
captcha (4 types) is exists now.
All what you want must be only plugins
littledev.ru - мой маленький зарождающийся блог о котонти.
снижение стоимости программирования и снижение стоимости производства разные вещи. Первое можно скорее сравнить с раздачей работникам дешевых инструментов, чем со снижением зарплаты