|
[
Permalink
| « Hide
]
Wolfram Richter added a comment - 08/Feb/05 08:29 AM
The current ordering is in fact based on the time of the last update, which is indeed not to useful.
I just just reordering my browser bookmarks (using drag-and-drop) when I realized something: how come I couldn't reorder my Confluence pages with drag-and-drop too?
Ajax is already being used to play with drag-and-drop functionality in the tasklist macro...seems like a logical extension for moving content around. Scheduling bug fix for 1.4.3 release.
+1 – it would be really nice to be able to sort child nodes ({children}) in ascending/descending order. right now my sorted list of releases appears with the oldest release first.
This was scheduled for 1.4.3, I dont see where it was fixed. Did it make it to 2.0?
Sean, what was fixed was
Regards, Can we get an update on the status of this feature request? Are there any plans to support this in the near future?
Guys,
Just so we're clear here... are you looking to control the order of pages in a space, or in the PDF export? Ordering pages in a space doesn't really make sense, as we provide alphabetical view, recently updated and a page tree. From what I've gathered with the comments, most people are referring to PDF export. What sort of ordering would be necessary? Alphabetical (within hierarchy) Any others? Ordering is not just important for PDF but also for wiki pages. When I have a book page with several chapter pages underneath, I want to list those chapters in a fixed order when I print them with the {children} macro on the book page. There are many other usecases where this is important:
{scrollbar}, {pagetree}. We use the {pagetree} macro to add navigation on the left side. However, we cannot control the order of the navigation items (unless you do ugly prefixing, which as explained previously has serious drawbacks). If you use {scrollbar} for a tutorial, you want to make sure that the order of your pages is correct, again avoiding the prefix hack. I believe the fix should be generic enough so that it applies to both PDF, spaces and html export. I'd really like to be able order pages in a arbitrary order with an up arrow / down arrow next to each page, or maybe something a la the method I used to order my netflix.com queue, where I have a listing of all the objets and a int filed next to each in which I enter a number as to the order I want them to appear.
Manual ordering is what I'm looking for. If you're producing documentation you need to order it by the logical flow, not some sort of attribute.
I'm also missing some options that could be toggled for PDF export like:
And probably heaps of other stuff I havn't thought of yet. My internal clients want to be able to list child pages in a specific order, to make readability easier.
I want to leverage existing macros such as child and pagetree to reduce the cost of maintenance. For example, using pagetree in a left navigation bar, but with section in the order as per client's desire. This is useful when migrating content manually in order. The sequence specified should applicable to child, pagetree, and exported pdfs. The following Use Cases assume that the relationship between pages is heirarchical, Use Cases
If the old sequence number is less than the new sequence number, If the new sequence number is less than the old sequence number, ! Other Advantages Hope this helps ! I wish to support this request. Jason Pouflis's comment (above) describes the requirements I have perfectly.
For those wanting to use Confluence primarily as a documentation tool, i.e. to build a structured documentation system, manual, electronic book, or similar, this requirement is a must-have. It simply must be possible to define the order of the "chapters" arbitrarily, whilst retaining automatic generation of table of contents, and without having to resort to manually defined chapter or section numbers. Anthony Dyson PS Hey site administrators, how about removing the mail cascade currently occupying most of this comments block?! This issue may prove to be a showstopper for my organisation.
It would be a good thing to have it assigned and scheduled. Ville Valtasaari Our space home pages almost always have a children macro as a table of contents. I support this issue because I'd like to be able to order how the children are displayed.
Everyone here who spends any time working with Confluence has requested this feature. It would make self - assembling documents a slam dunk. A simple move it up / move it down interface would do just fine here.
Indeed, specifying an ordering for child pages is crucial in any sort of documentation work, be it for print or just for navigable online documentation. Not everyone reads online documents by jumping around via hyprelinks, for many readers the structure we provide via page organization is a crucial help to finding content and reading it in a logical and natural order. A Wiki that allows for structure in addition to the unsorted ocean of keywords and the confusing mesh of links has a big usability advantage.
Bump. bump. bump. Another me too. This is pretty important and can be done easily enough: assign a weight to each page. Pages are then sorted first by weight (heavier pages sink to the bottom) and then alphabetically if two pages have the same weight. This might be easier to implement then numbering each page with a unique sort order: inserting a page in the middle would then require lots of renumbering.
When is this going to get fixed. This is a major issue with the product and basically makes it unusable for documentation.
I'm still rooting for this, too. FWIW I do note that it is #4 on the list of most popular issue.
 It isn't though yet on the roadmap, but at least it is filtering to the top. Being able to order how the Children are displayed is critical! I was trying to figure out how to change the default order from alphabetical and couldn't believe the sort order can't be change. We need to be able to set a "logical order" for our pages - not just ordered alphabetically. PLEASE FIX THIS.
Am currently looking into Confluence ... using another wiki right now. This issue is one of the major things missing from this product in order for us to jump ship. (Not that our current wiki can do this, but I don't have a good enough reason to change yet,).
Milt Taylor wrote:
> This issue [..] are the major things missing from this product in order for us to jump ship Hey Atlassian, with other words, this feature will be paid at least partially since you gain a new customer Milt, there is a {toc} (table of content) macro (at least as a plugin) available plus another which lists a child-document-tree. So TOC should not be a problem. Was hoping to use Confluence for collaborative authoring of documentation set, exporting the space to HTML and then converting that to .chm in a Help Development Kit. Absolutely out of the question until I can order and insert pages at will within a level. My appraisal of Confluence stops here. Pity.
I agree – this would be incredibly useful.
I very nearly persuaded our company to buy Confluence based around the MS Word import tool and being able to re-export back to PDF – but the PDF export is not useful for a printed manual because it's completely out of order. If the reordering of pages work, this can become a substitute for manual writing... Is there any estimate of when we might have it? My company bought a confluence license to use it as a documentation wiki. The pdf export was one of the key issues to decide for this product. Unfortunately, because of the missing page ordering, we cannot use it to create documentation pdf files. We really need this feature.
This issue is over 3 years old. It is a frequently requested feature. It is over a year since any comment by Atlassian, and that was off the mark. Could we have some commentary here on why this is difficult? Or, if it's not, then why it has not been implemented yet? It would be nice to just have some feedback.
Also evaluating Confluence - this request is really important for my criteria too. What is more concerning is the lack of response from Atlassian...
In general, if an issue has a lot of votes, has not been closed as "won't fix" or "invalid", and doesn't have a comment from someone at Atlassian explaining why we don't want to do it, you can assume that it's something we are interested in implementing at some stage.
We generally don't comment on our feature schedule beyond the next few releases because historically our roadmap has been so volatile, we'd annoy far more people by promising one thing and delivering another than we do right now by not promising anything. There's a reasonably accurate screed about how we choose what to implement, and how to influence the process here: http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+and+Improvements Ordering pages is a reasonably non-trivial feature. Between the issues of interaction with exporting, various macros, and having a user interface for re-ordering pages that isn't painful to use, there's a fair chunk of work involved. As such, the feature has to compete with a lot of other frequently requested but non-trivial features for developer time. All I can say now is that we're currently focusing development on highly voted-for features. Charles,
Thanks for the response. So, this issue is Number 4 in the charts, is ages old, but has never been on the horizon? Seems like it may be in the too hard basket to me. Is there a page where the features for the next release are listed? I had a look but couldn't find it. See ya at the Sporters The "charts" are slightly misleading, as they only show open issues. As such, there's always going to be something at the top that's been open a while, attracted a lot of votes but isn't fixed yet, regardless of priority.
I understand the "non trivial" aspect of supporting ordering in Wiki...
What I don't understand is how can it be that a real need doesn't find a simple an elegant solution. We are in the business of creating software to facilitate needs. If this is a real need, we need a real solution and we cannot just not solve it. Of course you guys are only prioritizing between many other needs, and that is understood. my 2 cents towards getting us a real solution: I know this is possible because there is an open source wiki to which someone wrote a plugin that does exactly that. Unfortunately I found it few months ago and cannot re-find it now for this thread reference. If I find it again, I will. regards. Sorry, but I couldn't agree less with hernan. This issue here is ordering on the page. Confluence is not just a wiki, it is a structured wiki. When you introduce structure that brings along additional considerations, and page ordering is one of them. Having the concept of children naturally raises the concept of ordering your children. This is a fundamental consequence of the main selling point of the product, and should be addressed as a priority.
Pete I saw a tantalising flicker photo with this feature in: http://www.flickr.com/photos/mcannonbrookes/497274503/
Any idea which fix version is planned to into? David Hi David,
Sorry, that tantalising photo is from a Fedex V project, see http://blogs.atlassian.com/developer/2007/05/fedex_v_page_ordering_for_conf.html Cheers, This is related to http://jira.atlassian.com/browse/CONF-5055
I second the comment of Pete Miller above. This is an absolute must feature for a hierarchy imho.
Another feature I'd like to see would be automatic page level numbering for a space or hierarchy so when exported or showing in the hierarchy view we could see chapter, section, subsection numbering such as 1.4.5. If you inserted a page within two subpages, it would automatically renumber all of the following pages. This would be very useful when referring to pages in media outside of the wiki. I am developing a plugin that may solve your page ordering issues: http://confluence.atlassian.com/display/CONFEXT/Outline+Plugin
Take a look and let me know what you think. Cheers, Geert, unfortunately I don't think so
This is an absoltue dealbreaker for me - without the ability to structure topics in a meaningful way, any hard copy is going to be useless.
If Confluence provided the basic mechanism to order pages, I'm sure the developer community would jump all over it and provide tools for re-ordering, etc. We just need some standard property of pages in Confluence that allows us to set their order.
Like others, our firm is strongly considering Confluence (actually Confluence + Jira, so perhaps Jira Studio) – in our case as the basis for a client-facing extranet. One very important use of a CMS for us, as for others, is the ability to produce structured documentation. As a first cut, some sort of simple ordering mechanism, like the "weight" values given to content nodes in Drupal, for example, would be OK. And indeed if this just creates a basic mechanism that folks like Adaptavist can run with that seems like a great thing.
Long-term it would be nice to have fairly full features for document hierarchy, like the ability apply various canned or customer numbering schemes. The ordering of numbered Pages like 1.bla, 2.bla is not logical.
1. Chapter 1 If you order this by scrollbar macro, children macro etc. you will get 1. Chapter, Confluence uses bitwise ordering which results in 1 and 10 appearing together then 2, etc.
The pagetree plugin has a natural sort routine which puts 10 after 9, etc. It's open source and Atlassian are more than welcome to grab it and use it in Confluence. It's also been tested on unicode sites and seems to work well in all cases. The only way I've found it to work is by ordering 01, 02.... 10. Pagetree gives me the alphanumeric 1, 10, 2, ... order. Is it Pagetree2 that orders naturally ?
The functionality first appeared in pagetree (the open source plugin) - it defaults to bitwise ordering so it works the same way as everything else in Confluence, however there is a sort or order param (can't remember which) that allows you to specify natural sort order.
Confluence 2.8 milestone 3 release has first implementation of native page ordering within Confluence
 It's true, I'm happy to say we are working on an implementation of Page Ordering for the 2.8 release. We were going to wait until the functionality was a bit more stable and announce the Page Ordering functionality in an up and coming milestone, but it appears Guy has let the cat out of the bag, so to speak.
We have a component here in JIRA that we are using to track our progress, you can see it here Also, 2.8 milestone 4 will be available shortly that has some bug fixes and more features. Moved to Page Ordering Component
Heh, it was your Confluence 2.8-m3 release notes that let it out of the bag:
http://confluence.atlassian.com/pages/viewpage.action?pageId=127369710
Damn that "open company" thing!
@Charles - it would be hugely useful if there was a page explaining how plugins can take advantage of the new page ordering features, eg. there are a great many macros that render lists of pages that could, I assume, just hook in to this? If the API is fairly stable, it would be sweet if plugin developers could start working on new versions ahead of Confluence 2.8 release
Guy, there isn't a page with this information as yet. I can say a few things about it.
Most plugins that we've seen will use the page.getSortedChildren method which used to just return them in alphabetical order. Now it will return them sorted in the expected way which should make it easy for plugins to use this functionality. It'd also be useful if the new events/methods at the core of this feature could be used with collections other than a page's children... e.g. attachments, labels, etc.
Is the scope of this jira to be expanded, or is that ability already included and not mentioned? It would be good to specifically include page break tags that the PDF export understands, for maximum flexibility. Jim,
This case does not cover page break control, only the order setting of pages. Sorry for the confusion. Cheers Matt The first implementation of Page Ordering will be in Confluence 2.8.
There is a workaround for the page ordering problem, using the metadata and reporting plugins.
Simply assign a metadata entity - e.g. "Sortkey" to each page with an appropriate value. Use the reporting plugin to generate your document by selecting the required pages and ordering them according to your metadata value. Saving the result as PDF works fine, but unfortunately you still can't control the pagination! At least with the built-in export to PDF, each wiki page starts on a new page in the resulting PDF. Nick Paged Ordering (and more) has been resolved in a very elegant way for Confluence 2.8. Have a look at the documentation at http://confluence.atlassian.com/display/DOC/Moving+Pages+within+a+Space
and at http://confluence.atlassian.com/display/DOC/Moving+Pages+within+a+Space Thanks for the fix, it was a 4-year old, long-awaited issue.
Thank you to everyone who voted for Page Ordering. As Per says above we are very happy to deliver Page Ordering in Confluence 2.8:
You can read about Page Ordering and about the many other new features and fixes in Confluence 2.8 in our release notes: http://confluence.atlassian.com/display/DOC/Confluence+2.8+Release+Notes Confluence 2.8 can be downloaded here: http://www.atlassian.com/software/confluence/ConfluenceDownloadCenter.jspa |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Resolved
Critical
Page ordering
So my hack failed there.