ez3.1b1: Subtree Subscription Attribute

«

Previous topic

|

|

Next topic

»

Author	Message
Tristan Koen	Tuesday 10 June 2003 5:54:26 am This attribute has been added in ez3.1b1 Does anyone know what it does, or how it works? Our website has some free and some 'pay' content. Can this attribute be used to implement this mechanism in ezPublish?
Paul Borgermans	Tuesday 10 June 2003 6:23:48 am I posed a similar question, and looking at the code: The subscription attribute is to be used to allow visitors to be notified when something changes or is added to the object as a child. I guess this will be most useful in forums, and comments with articles as it will create a notification rule for the user who clicks it (not seen in the svn templates yet). To have free and pay content, you will have to implement roles (access to) and workflow (payment). This is not really in the base distribution, but the provided samples may give you a headstart. The "subscription" feature is probably useful too. hth Paul eZ Publish, eZ Find, Solr expert consulting and training http://twitter.com/paulborgermans
Bård Farstad	Tuesday 10 June 2003 6:28:32 am The subtree subscription datatype works as follows. You create a class ( e.g. forum message ), which has this attribute. When a user creates a new message he sees a checkbox. When this checkbox is ticked off and the object is published a notification rule is created for the nodes this object is published in. Then when someone creates an object under the created object the user will be notified about an update via the notification system. --bård Documentation: http://ez.no/doc
Thomas Brandl	Thursday 24 July 2003 9:34:13 am Sounds just like a cool feature!
Vaskin Kissoyan	Thursday 13 May 2004 11:27:33 am is the notification just for the owner?

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 31 2025 03:31:58
Script start
Timing:	Jan 31 2025 03:31:58
Module start 'layout'
Timing:	Jan 31 2025 03:31:58
Module start 'content'
Timing:	Jan 31 2025 03:31:58
Module end 'content'
Timing:	Jan 31 2025 03:31:58
Script end

Main resources:

Total runtime	0.0246 sec
Peak memory usage	8,192.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0057	588.2500	151.2266
Module start 'layout'	0.0057	0.0046	739.4766	220.7031
Module start 'content'	0.0103	0.0128	960.1797	1,001.7891
Module end 'content'	0.0231	0.0015	1,961.9688	33.9922
Script end	0.0246		1,995.9609

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0026	10.3709	14	0.0002
Check MTime	0.0010	4.2142	14	0.0001
Mysql Total
Database connection	0.0010	3.8648	1	0.0010
Mysqli_queries	0.0029	11.6882	3	0.0010
Looping result	0.0000	0.1703	1	0.0000
Template Total	0.0012	4.7	1	0.0012
Template load	0.0009	3.4950	1	0.0009
Template processing	0.0003	1.1566	1	0.0003
Override
Cache load	0.0005	2.2242	1	0.0005
General
dbfile	0.0003	1.3705	8	0.0000
String conversion	0.0000	0.0407	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