Bo Wang's dashboard

Hi Christian,

If you put my code within your report, it should be generating a list of the child pages, please try it out, the final macro should look like this:

{report-block}
{local-reporter:content:children}
{text-sort:content:title|mode=bitwise}
{local-reporter}
{report-body:injected=true}
h4. [%title%]
{report-body}
{report-block}

Within the context of the report, it is actually reporting on the children pages, so %title% would give the title of each child page (not the current page).

Regards,
Bo Wang

Hi Kay,

I am unsure about the cause of this behavior, it might be best to raise this issue with the authors of the plugin (Atlassian) to find the cause, please raise an issue in the public issue tracker for this plugin at: https://studio.plugins.atlassian.com/...

Regards,
Bo Wang

Hi Ariella,

This is the expected behavior, you will have to click "Save" to actually save your changes, otherwise it is treated as just a temporary draft and if you leave the page without saving, you will lose the changes.

Just remember to press "Save" after making any changes and you should not experience any lost data.

Regards,
Bo Wang

Hi Eric,

This should be working, I have been using this in quite a few places, it might just be that the Supplier is not working properly, can you please use the following on the actual blogpost itself and see if it is correct?

Just go into a couple blog posts and put the following macro:
----------------------------
This page has been viewed {tracking-info:value=view count}zero{tracking-info} times.
----------------------------

If the numbers do not match up, there might be something wrong with the Tracking Supplier.

One note is that the tracking stats only counts visits that occurred AFTER the plugin has been installed and does not include visits by the last modifier for the particular blog.

Regards,
Bo Wang

Hi Christian,

I believe the reason this is happening is because the report-info macro generates the links as relative links (/contextpath/display/SPACE_KEY/PAGE_NAME), this works well on the page when rendered, but does not appear so well in exports as the base URL you are accessing it in is not part of Confluence and thus the links end up being broken.

Only way I can think of to resolve this issue is to use something like the following:
...
{report-body:injected=true}
h4. [%title%]
{report-body}
...

Let me know if this works out for you.

Regards,
Bo Wang

Hi Eric,

Another option is: instead of using the {include} macro, you can use the {redirect} macro (see http://www.customware.net/repository/... ), this sets up a redirect, so when they visit the sub categories in the Operating system space, they are automatically redirected to the appropriate space for the sub category. This way they can sign up for alerts, add new blogs and such, basically its just seemlessly relocating the users to a new space without them noticing.

You CAN actually sort pagetree pages :) please refer to the documentation for the pagetree macro (see: https://studio.plugins.atlassian.com/....
Here is an excerpt from the documentation:
-------------------------------------------------------------
sort may be one of the following

* position - sort pages using the Confluence 2.8 sorting rules which uses the position if set, otherwise reverts to natural ordering (default for versions 1.7 onwards).
* natural - sort pages in natural order, eg: title1, title2, title10 (default for versions before 1.7).
* bitwise - sort pages using standard alphabetical sorting on the page title, eg:title1, title10, title2
* creation - sort pages by creation date
* modified - sort pages by modification date
-------------------------------------------------------------

Regards,
Bo Wang

Hi Alex,

Thanks for that clarification, I do not believe that the plugin indexes the data that it stores (the search is only able to search indexed data) and thus you will not be able to search for them, if you would like this type of functionality, please raise an issue in our issue tracker (see: https://greenhouse.customware.net/jir... ) so we can investigate and possibly look at implementing this feature in future releases.

Regards,
Bo Wang

Hi,

Are you familiar with the Reporting Plugin (see: http://www.customware.net/repository/...?

Basically, what this plugin allows you to do, is to gather up all of the scaffolding input information, filter them down based on a list of requirements, and report on the results.

For example, if you wanted a table of all of the articles which was written by "John Smith" that is in the current space, you can use the following:
{report-table}
{content-reporter:space=@self|type=page}
{text-filter:data:article_author|include=John Smith}
{content-reporter}
{report-column:title=Author}{report-info:data:article_author}{report-column}
{report-column:title=Issue No.}{report-info:data:issue_number}{report-column}
{report-column:title=Year}{report-info:data:publish_year}{report-column}
{report-column:title=Subject}{report-info:data:article_subject}{report-column}
{report-column:title=Location}{report-info:data:article_location}{report-column}
{report-column:title=Abstract}{report-info:data:article_abstract}{report-column}
{report-table}

Regards,
Bo Wang

Hi Eric,

Yeah, that is a slight problem, it is hard to separate blogs within a space, the only ways I have found to do this is with labels on the blogs, but it is a bit difficult to manage them since you will have to remember to label every blog.

What you could do is build the subcategories as separate spaces, and in your operating system space references that space, try using:
{include:SUBCATEGORY_SPACE_KEY:Home}, this is basically a live copy of the referenced page (it copies all of the contents from that page and is automatically updated everytime the referenced page is updated).

So it would look something like this:

* Space: Operating System 1
** Home
*** Sub Category 1 - {include:OS1SC1:Home}
*** Sub Category 2 - {include:OS1SC2:Home}

* Space: Operating System 1 - Sub Category 1 (space key is 'OS1SC1')
** Home

* Space: Operating System 1 - Sub Category 2 (space key is 'OS1SC2')
** Home

This way you can have all of the sub categories as separate spaces to have your individual blogs and still have the hierarchy you are looking for.

The concept of sub-spaces within a space is still not implemented in Confluence but is quite a popular request so workaround like this is sometimes required.

Please let me know if you find this answer adequate for your needs.

Regards,
Bo Wang

Hi Eric,

This is an interesting case you have brought up.

I believe this will require a quite standardized space layout to achieve what you are looking for, basically, you will need your spaces like this:
* Space: Operating System 1
** Home
*** SubCategory 1
*** SubCategory 2
* Space: Operating System 2
** Home
*** SubCategory 1
*** SubCategory 2

Once it is in that format, simply add a space label to each of these spaces (eg. "operating_system") and then put the following macro:
{composition-setup}
{report-block}
{space-reporter:label=operating_system}
{space-reporter}
{report-body:injected=true}
h4. {toggle-cloak:id=%key%} [%name%|%key%:]
{cloak:id=%key%|visible=false}
{pagetree:space=%key%}
{cloak}
{report-body}
{report-block}

This uses both the Reporting plugin, Composition plugin and the Pagetree macro (bundled with Confluence) to achieve the functionality you are after.
It will list all of the spaces with the "operating_system" space label, displaying the space name (you can click the name to go to the space) and have a blue arrow which you can click to display the cloaked content, the cloaked content contains the pagetree macro which shows all of the sub categories, you can click on the sub category to go directly to it, or click the + sign next to them to expand even further down (this is default pagetree functionality).

Please let me know if this solves your problem.

Regards,
Bo Wang

You are very welcome. – Bo Wang, on February 01, 2010 19:17

The data is stored within the database (as part of the Bandana table) so the data should not be affected by uninstalling the plugin, once the new plugin (version 3.3.1) is installed, your data should still be available to you.
Please let us know how you go with it and if you come across any further problems, just post another thread here and we will assist where we can.

Ok, I have released a new version of the plugin (version 3.3.1), you can download the plugin here:
http://www.customware.net/repository/...
Please uninstall version 3.3.0 of this plugin before installing version 3.3.1 to avoid any conflicts.
This plugin is not yet available in the plugin repository but should become available shortly (within an hour or so).
Once again, thanks for raising this issue.

Thanks for raising this issue so quickly, I have reviewed the code and it seems one of the web resources was not declared properly, I will try and push out a new release for this fix as soon as possible for those who are affected by this issue.

I will leave a post here to update you once the issue is resolved.

Hi,

I have used the version 1.7.1 of the plugin in a Confluence 3.1 instance and have yet to come across any problems (the standard show-to and hide-from works fine from my usages so far), however the plugin has yet to go through the standard formal testing and release process yet.

If you do decide to use it, I recommend testing it out on a staging server first before installing it into your production server and let us know if you come across any issues and we will look into fixing it as soon as possible so that it is completely compatible with Confluence 3.1

Regards,
Bo Wang