<emit source="site-news"></emit>

Provided by module: CMS: Site News

List editing events in the site history.

The attributes are translated to a SQL-query on this form:

SELECT * FROM history JOIN paths USING (path_id) [WHERE [action IN (action1, action2...)] [AND] [path LIKE path1 [OR path LIKE path2 [OR ...]]] [AND] [path NOT LIKE not-path1 [AND path NOT LIKE not-path2 [AND ...]]] [AND] [(type LIKE type1 OR type LIKE type2 or ...)] [AND] [(type NOT LIKE not-type1 AND type NOT LIKE not-type2 AND ...)] [AND] [time > from-date] [AND] [time < to-date]] [GROUP BY path] ORDER BY [time|publish] DESC

The number of returned entries are by default limited to 10. You can change this by setting the maxrows attribute.

There is usually no need to use the nocache tag with the site-news emit source because its cache entry is updated automatically through internal notification.

History entries for directories are excluded by default, but they may be included with the 'type' attribute described below.

Attributes

action="{create, edit, delete, undelete, join}"

Comma-separated list of wanted action types. Omitting this attribute means all actions. None of these actions are supported on frontends, where this attribute therefore should be omitted. Frontends may support actions in the future.

It's also possible that the action is '(external)' if the file has been committed outside Roxen CMS without the CMS specific formatting of the commit message. In such cases the user fields are typically empty as well.

order-by="{time, publish, random}"

Order results by time of event, by date of publish, or at random. Date of publish can be configured by the Visible From value in the External Visibility wizard. Otherwise the date when the file was created is used.

undelete

Allows deleted files to be listed.

invisible

Allows files which are time based published to be listed.

path="string"

Comma-separated list of globs or exact paths from which files resides within the SiteBuilder storage.

not-path="string"

Comma-separated list of globs of where to not match files from within the SiteBuilder storage.

type="string"

Comma-separated list of wanted content types. It can also be one or more global expressions; "*/xml*" to match all xml types within Roxen CMS.

If the special value "dirs" is included in this list then directories get included, otherwise they are filtered out. To include all files and directories, use "dirs,*".

not-type="string"

Comma-separated string of unwanted content types. It can also be one or more global expressions; "*/xml*" that excludes all xml files within Roxen CMS.

unique-paths

Indicates that each file only should appear once, with it's latest action.

from-date

A date from which to search for changes. When specified, from-publish-date and from-publish-time are not used. Use together with from-date-parse for faster execution.

from-time

A date and time from which to search for changes. When specified, from-date, from-publish-date and from-publish-time are not used. Use together with from-date-parse for faster execution.

from-publish-date

A date from which to search for changes. Used instead of from-date to search on publication date instead of time of event. Publication date can be configured by the Visible From value in the External Visibility wizard. Use together with from-date-parse for faster execution.

from-publish-time

A date and time from which to search for changes. Used instead of from-time to search on publication time instead of time of event. Publication time can be configured by the Visible From value in the External Visibility wizard. When specified, from-publication-date is not used. Use together with from-date-parse for faster execution.

to-date

A date from which to search for changes. When specified, to-publish-date and to-publish-time are not used. Use together with to-date-parse for faster execution.

to-time

A date and time from which to search for changes. When specified, to-date, to-publish-date and to-publish-time are not used. Use together with to-date-parse for faster execution.

to-publish-date

A date from which to search for changes. Used instead of to-date to search on publication date instead of time of event. Publication date can be configured by the Visible From value in the External Visibility wizard. Use together with to-date-parse for faster execution.

to-publish-time

A date and time from which to search for changes. Used instead of to-time to search on publication time instead of time of event. Publication time can be configured by the Visible From value in the External Visibility wizard. When specified, to-publish-date is not used. Use together with to-date-parse for faster execution.

from-date-parse

Parse the from-date, from-time, from-publish-date or from-publish-time value with this format:

%Y	absolute year
%y	dwim year (70-99 is 1970-1999, 0-69 is 2000-2069)
%M	month (number, name or short name) (needs %y)
%W	week (needs %y)
%D	date (needs %y, %m)
%d	short date (20000304, 000304)
%a	day (needs %y)
%e	weekday (needs %y, %w)
%h	hour (needs %d, %D or %W)
%m	minute (needs %h)
%s	second (needs %m)
%f	fraction of a second (needs %s)
%t	short time (205314, 2053)
%z	zone
%p	'am' or 'pm'
%n	empty string (to be put at the end of formats)

Requires from-date, from-time, from-publish-date or from-publish-time to be useful. Speeds up execution somewhat.

to-date-parse

Same as from-date-parse but is used on to-date, to-time, to-publish-date or to-publish-time.

Searches for xml-files in a site that any action was done on between 12 and midnight december 12 2002. Display only paths once even though actions may have occured more and only display max 100 rows. <noindex> <emit source='site-news' action='*' type='*/xml*' from-time='2002-12-12 12:00' to-time='2002-12-13 00:00' from-date-parse='%Y-%M-%D %h:%m' to-date-parse='%Y-%M-%D %h:%m' unique-paths='' maxrows='100' skiprows='0'> <div><a href='&_.path;'>&_.title;</a> &_.time; &_.action;</div> </emit> </noindex>

&_.action; (provided by CMS: Site News)

The action that was performed on the page. One of create, edit, delete, undelete or join. This entity is not available on frontends.

&_.fullname; (provided by CMS: Site News)

Fullname of the user who performed the action. This entity is not available on frontends.

&_.message; (provided by CMS: Site News)

Commit message. This entity is not available on frontends.

&_.path; (provided by CMS: Site News)

Path of the file.

&_.publish; (provided by CMS: Site News)

Date of publish can be configured by the Visible From value in the External Visibility wizard. Otherwise the date when the file was created is used. Format is YYYY-MM-DD HH:MM:SS. See &_.pubtimestamp; for same data as an integer.

&_.pubtimestamp; (provided by CMS: Site News)

Same as &_.publish; but returned as an integer representing number of seconds since Jan 1, 1970.

&_.revision; (provided by CMS: Site News)

Revision of the file. This entity is not available on frontends.

&_.time; (provided by CMS: Site News)

Time the event took place. Format is YYYY-MM-DD HH:MM:SS. See &_.timestamp; for same data as an integer.

&_.timestamp; (provided by CMS: Site News)

Same as &_.time; but returned as an integer representing number of seconds since Jan 1, 1970.

&_.title; (provided by CMS: Site News)

The page current title (from metadata), if there exists one.

&_.type; (provided by CMS: Site News)

Content type of the page.

&_.user; (provided by CMS: Site News)

Username of the user who performed the action. This entity is not available on frontends.

&_.userid; (provided by CMS: Site News)

Numeric user id of the user who performed the action. This entity is not available on frontends.