I think the random hex guest ids generated for guests should be made clear in the chat room, especially knowing what your own guest ID is. This would help when guests are trying to refer to other guests in the chat.
Say I'm guest 00000 and there's a guest 00001 that wants to refer to me without confusin…
Suggested by Patrick Schmalstig on 29th July 2016
Currently, Composr uses the MyISAM database engine for MySQL installations. MyISAM is no longer maintained and probably should not be used.
Instead, Composr should use the INNODB engine as it has active development and has some performance improvements over MyISAM (for large sites).
Suggested by Patrick Schmalstig on 24th August 2016
Have a search block parameter that will automatically add quotes around search terms if not included.
This is useful if a particular search context always needs to respect word order, but the users can't be expected to know to add the quotes.
Suggested by Chris Graham on 20th September 2016
I think it is a nice feature to have some form of "Topic author" indicator on posts made by the author of a topic in cns_forums. That way, it's easy to distinguish who the topic author is without having to go back to the first post. It also gives eye prevalence to replies made by the author.
Suggested by Patrick Schmalstig on 21st October 2016
Make two new options for the blocking system. Allow the ability for staff to prohibit the ability of members being able to block staff (communication blocking implication if they do), and to prohibit staff from being able to block any members (again, communication block implication... also widely considere…
Suggested by Patrick Schmalstig on 25th November 2016
Have a backend_ical.php (to mirror backend.php which does RSS).
This would export all events the accessing user has access to, in a dynamic iCal feed that can be plugged into anything.
(Currently iCal is only available from the CMS zone)
Suggested by Chris Graham on 21st January 2017