Request: Unanswered forum threads view template

Next topic

Author	Message
Heath	Thursday 10 December 2009 7:27:49 pm I would find the addition to share.ez.no forums of a recursive top down listing of unanswered forum topic threads per forum a very useful feature for those like me who would like to see that every thread gets at least one fair response and a template view to see which threads in all the various forums that are unanswered (no replies). In this way unanswered forum threads would stand out in a easy way to find, read and respond to each quickly. Please let me know if this idea is any good. Cheers, Heath Brookins Consulting \| http://brookinsconsulting.com/ Certified \| http://auth.ez.no/certification/verify/380350 Solutions \| http://projects.ez.no/users/community/brookins_consulting eZpedia community documentation project \| http://ezpedia.org
Kristof Coomans	Friday 11 December 2009 2:36:50 am Very good idea. However, some questions don't get solved from the first reply on. It would be nice if there would be a feature to completely close a forum topic as well. This would allow for a listing of "open" topics as well. independent eZ Publish developer and service provider \| http://blog.coomanskristof.be \| http://ezpedia.org
Gaetano Giunta	Saturday 12 December 2009 3:30:40 am I think we should do more than simply add an open/closed button for that to work well... some topics are help requests, some other are not. Principal Consultant International Business Member of the Community Project Board
Nicolas Pastorino	Monday 14 December 2009 4:36:14 am Hello Heath, This is a great idea. Adding this right away to the Use Cases the share.ez.no team takes care of. There is, as Kristof and Gaetano tell, even more to do on this topic. But the first round could comprize your proposal only. Cheers ! -- Nicolas Pastorino Director Community - eZ Member of the Community Project Board eZ Publish Community on twitter: http://twitter.com/ezcommunity t : http://twitter.com/jeanvoye G+ : http://plus.tl/jeanvoye
Heath	Thursday 25 March 2010 4:57:40 pm While I thank the share.ez.no team for their work on this use case. I see now we do indeed have the basis for storing the resolved, unresolved attribute [0-1]. It still seems we lack a way to search or filter the views by this attribute in any useable way .. yet. It would be nice if more development could go into adapting templates to provide more support for these features. Cheers, Heath [0] http://share.ez.no/blogs/share.ez.no-team/mark-your-forum-topics-as-solved-when-you-got-an-appropriate-answer [1] http://share.ez.no/forums/discussions/mark-your-forum-topics-as-solved-when-you-got-an-appropriate-answer Brookins Consulting \| http://brookinsconsulting.com/ Certified \| http://auth.ez.no/certification/verify/380350 Solutions \| http://projects.ez.no/users/community/brookins_consulting eZpedia community documentation project \| http://ezpedia.org
Nicolas Pastorino	Friday 26 March 2010 6:57:53 am Hi Heath, I totally agree on this. Already reacted in this direction there : http://share.ez.no/forums/discussions/mark-your-forum-topics-as-solved-when-you-got-an-appropriate-answer/comment57909 Cheers! -- Nicolas Pastorino Director Community - eZ Member of the Community Project Board eZ Publish Community on twitter: http://twitter.com/ezcommunity t : http://twitter.com/jeanvoye G+ : http://plus.tl/jeanvoye

eZ debug

Timing:	Jan 18 2025 02:19:55
Script start
Timing:	Jan 18 2025 02:19:55
Module start 'layout'
Timing:	Jan 18 2025 02:19:55
Module start 'content'
Timing:	Jan 18 2025 02:19:56
Module end 'content'
Timing:	Jan 18 2025 02:19:56
Script end

Main resources:

Total runtime	0.4556 sec
Peak memory usage	4,096.0000 KB
Database Queries	73

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0041	589.5156	152.6875
Module start 'layout'	0.0041	0.0025	742.2031	39.5234
Module start 'content'	0.0065	0.4479	781.7266	680.4453
Module end 'content'	0.4544	0.0012	1,462.1719	20.0938
Script end	0.4556		1,482.2656

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0030	0.6594	16	0.0002
Check MTime	0.0013	0.2773	16	0.0001
Mysql Total
Database connection	0.0005	0.1145	1	0.0005
Mysqli_queries	0.3928	86.2131	73	0.0054
Looping result	0.0007	0.1481	71	0.0000
Template Total	0.4304	94.5	2	0.2152
Template load	0.0022	0.4741	2	0.0011
Template processing	0.4283	93.9992	2	0.2141
Template load and register function	0.0001	0.0165	1	0.0001
states
state_id_array	0.0005	0.1198	1	0.0005
state_identifier_array	0.0011	0.2487	2	0.0006
Override
Cache load	0.0019	0.4163	37	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0005	0.1106	4	0.0001
Fetch class attribute name	0.0010	0.2189	10	0.0001
XML
Image XML parsing	0.0016	0.3456	4	0.0004
class_abstraction
Instantiating content class attribute	0.0000	0.0040	12	0.0000
General
dbfile	0.0010	0.2154	35	0.0000
String conversion	0.0000	0.0013	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
6	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
6	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
4	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
8	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
1	content/datatype/view/ezxmltags/link.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/link.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 27 Number of unique templates used: 7

Time used to render debug report: 0.0001 secs