Notification list - report of user's subscriptions?

«

Previous topic

|

|

Next topic

»

Author	Message
Mark Marsiglio	Friday 25 August 2006 11:26:27 pm We have a few thousand users signed up for notifications of various pags/sections of the site. As part of our analytics, we would like to see what areas are the most popular. Also useful would be a count of how many subtree subscriptions each user had. At the most basic, we would need to see which users have a subtree notification on a particular node. The docs on the notification module only deal with the fetching the subscriptions of the current logged in user. Is there a way to extract this information based on a fetch of the node id, or to modify a template like the line.tpl to show a subscription count in it? http://www.thinkcreative.com Turning Ideas Into Strategic Solutions
Kristof Coomans	Sunday 27 August 2006 2:20:51 am Hello Mark I think there are no such template fetch functions at the moment, but it would be a nice enhancement. Can you post an enhancement request in the bug tracker? independent eZ Publish developer and service provider \| http://blog.coomanskristof.be \| http://ezpedia.org
Marco Zinn	Sunday 27 August 2006 6:11:29 am Hi Folks, as i had to answer the same question before and solved it with some SQL query, i posted this suggestion http://ez.no/bugs/view/8906 in order to adress the common "reporting" tasks. So, Mark, i guess, your question can be answered with SQL queries. If you have access to your DB with some GUI (phpMyAdmin, sqlPlus), i can look up the query i had. Please note, that your question "which users have a subtree notification on a particular node" aint that easy, because the notifications are stored for the top node of that tree. Do you want to see the users that have notifications for EXACTLY this node or notifications on any subtree, that includes the particular node? Marco http://www.hyperroad-design.com
Norman Leutner	Sunday 27 August 2006 11:10:14 pm If you want to the query within ez, just take a look at this extension, it show how to execute a sql query into ez and return the result. http://ez.no/community/contribs/template_plugins/topauthors Mit freundlichen Grüßen Best regards Norman Leutner ____________________________________________________________ eZ Publish Platinum Partner - http://www.all2e.com http://ez.no/partners/worldwide_partners/all2e_gmbh

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing:	Jan 18 2025 21:00:51
Script start
Timing:	Jan 18 2025 21:00:51
Module start 'layout'
Timing:	Jan 18 2025 21:00:51
Module start 'content'
Timing:	Jan 18 2025 21:00:51
Module end 'content'
Timing:	Jan 18 2025 21:00:51
Script end

Main resources:

Total runtime	0.0172 sec
Peak memory usage	4,096.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0063	591.6875	152.6406
Module start 'layout'	0.0063	0.0036	744.3281	39.4766
Module start 'content'	0.0100	0.0051	783.8047	93.3359
Module end 'content'	0.0150	0.0021	877.1406	34.3047
Script end	0.0172		911.4453

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0027	15.9532	14	0.0002
Check MTime	0.0013	7.3917	14	0.0001
Mysql Total
Database connection	0.0007	4.3265	1	0.0007
Mysqli_queries	0.0033	18.9367	3	0.0011
Looping result	0.0000	0.1163	1	0.0000
Template Total	0.0018	10.2	1	0.0018
Template load	0.0009	5.2554	1	0.0009
Template processing	0.0008	4.9301	1	0.0008
Override
Cache load	0.0006	3.6924	1	0.0006
General
dbfile	0.0003	1.6184	8	0.0000
String conversion	0.0000	0.0651	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	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs