[#TRACK-31] does not work when used in the "Site Welcome Message" text

Confluence Extension: Tracking Plugin

does not work when used in the "Site Welcome Message" text

Created: 02/May/07 07:55 AM Updated: 02/May/07 01:34 PM

Component/s:

None

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

Environment:

Confluence 2.5

Description

« Hide

When I enter the {tracking-table} macro in the "Site Welcome Message" text block which can be defined in the Confluence Administration section, General Configuration, I get this error message:

tracking-table: @self cannot be used in the current context.

All

Comments

Work Log

Change History

Sort Order:

[ Permalink | « Hide ]

David Peterson added a comment - 02/May/07 08:03 AM

That's because the tracking plugin doesn't work on the Dashboard.

Could you post your full table, as well as what information you would like it to display?

[ Permalink | « Hide ]

Arne Schirmacher added a comment - 02/May/07 09:14 AM

Please see http://www.schirmacher.de/dashboard.action . This table is actually a fake (a static table).

I am using Atlassian's {popular:display=icon,count|types=news,pages} here: http://www.schirmacher.de/display/INFO/Index . This macro doesn't work on the Dashboard either (http://jira.atlassian.com/browse/CONF-8419). Also the hit counts do not match the tracking-table hit counts, most likely because it is a new Atlassian feature, my website is using the tracking plugin since mid 2006 but the upgrade to Confluence 2.4.5 happened only a couple of weeks ago.

I actually like the icon and the selectable page types from the Atlassian {popular} macro. The {tracking-table} macro looks a bit more messy and it also lists image hit counts which are of not much interest to the user.

My ideas how to resolve this:

* emulate the {popular} behaviour and design, but make it work with the tracking data
* or migrate the tracking plugin hit count data to the format expected by the {popular} macro and get rid of the {tracking-table} macro altogether.

[ Permalink | « Hide ]

David Peterson added a comment - 02/May/07 01:33 PM

Yeah, it's not the world's prettiest output. You could use the Reporting Macro - you can emulate the {tracking-table} with it by using something like this (which will work in the dashboard):

{cache:refresh=6h}
{report-table:maxResults=10}
{content-reporter:spaces=@global|type=page}
  {number-sort:track:view count}
{content-reporter}

{report-column:title=Title}{report-info:content:title|link=true}{report-column}
{report-column:title=Views}{report-info:track:view count}{report-column}

{report-table}
{cache}

This can be customised to any of the other report types ({report-block}, {report-list}) if you want to change the layout.

Otherwise, feel free to modify the {popular} macro to your heart's content.

[ Permalink | « Hide ]

David Peterson added a comment - 02/May/07 01:34 PM

Oh, I meant to mention, I've put the {cache} macro around the report because it will not be a fast-generated report, particularly when run across the whole server. This way it will only be slow for one person, once every 6 hours. You can change the refresh time to suit...