Table of contents
Status/RoadMap
Work is in progress. Please see PluginCategoryDev
New feature_category_reinforce in 1.10 when selected appears to be the original 1.9 "better-safe-and-sorry" approach when checking for perms when item is in multiple categories (i.e. once user has no perm to any one of the cat, he has no perm). When unchecked, it's the reverse, i.e. so long as user has perm to one of the cat, that will be enough for access. This is a great feature. It appears implemented in function get_object_categories_perms in categlib. Not sure if it needs to be elsewhere as well.
todo:
- add possibility to change the parent of a category (as it is possible in links directory)
- Check for category recursive loops. Let’s make sure we don’t get into a group loop.
- on tiki-admin_categories.php (Add objects to category).
- also, filter should be remembered after adding an object (listing all remaining objects which still correspond to filter). This a "clear filter" button may be added to show complete list.
- description of category should be visible as overLIB of category name + description of current category should be visible when browsing.
- all links should overLIB the "Description" field
- since two categories can have the same name, whenever categories are chosen in a drop-down menu, it should have the complete path
- tiki-browse_categories.php and tiki-admin_categories.php could be better integrated where you see extra options if you have permission to.
- listing of orphan objects (like orphan wiki pages)
- Zaufi: "Looked in source: then page categorized its description copied ... and never updated... -- so the only way to update categorized page is to remove and add it to caterogy again..."
- AuditTrail for category system
- xfml compliance
Done:
- Renaming & deleting of objects should be reflected in category system Done by Terence
- title of category should be clickable to the category browser Done by Terence
- the drop-down menu of "Add objects to category" should permit multiple selections by holding down SHIFT Done by Terence
- Cannot uncategorize objects
- Included a confirmation of deletion to the php script preventing accidental deletion of categories see attached file. Done by sdl.
Trackers
Bugs
- What CSS theme do you people use? EVERY theme except tiki.css cuts off the rights side of the Categories admin screen, making it impossible to edit or delete categories. What part of the .tpl for tiki-admin_categories.php do I need to change to make the tree column stop hogging all the screen space? What part do I change to make it stop preventing me from horizonatlly rsizing the screen? Thnaks. --alexboko February 12, 2005
- {SF(aid=>799372)}{SF}
- {SF(aid=>812792)}{SF}
- {SF(aid=>834783)}{SF}
RFEs
- smart categorisation
- {SF(aid=>738081,tag=>rfe)}{SF}
- {SF(aid=>796674,tag=>rfe)}{SF}
- {SF(aid=>792473,tag=>rfe)}{SF}
- {SF(aid=>744625,tag=>rfe)}{SF} (priority 2)
- Also, filter should be remembered after adding an object (listing all remaining objects which still correspond to filter). This a "clear filter" button may be added to show complete list.
- Interface : There is no indication that a page is displaying the category's content or the result of a category search. This can be confusing if you search for something not found in an empty category (page doesn't change, appears bugged). (priority 1)
- Show full category name in wiki pages
- Category translations
Competition and standards
CVS Doc section
Discussion/participation
Here's a discussion on IRC about Categories and Structures to formalize some of the thinking from that discussion.
Perhaps we can all start putting together out thinking about how Categories and Structures work or should work in the future. This is long term planning not something that has been defined for a particular version. Lets develop the requirements for what we want.
This is an edited snip of that conversation:
| albrown | what is wrong with structures? | |
| mose | delete a file don't delete it from struct | |
| albrown | should it, I think that I can argue that either way | |
| mose | interesting move | |
| albrown | 😉) | |
| mose | structure can be considered many ways | |
| mose | for me, it's just a list | |
| albrown | if you delete the page without deleting it from the structure you would still have the chance to rebuild the page perhaps completely differently without losing your position within the structure | |
| gmuslera | is a way to give order to wiki pages 😊 | |
| mose | but because we lack of structuration for content, it can be considered as a skeleton | |
| albrown | I thought that that was the intent of the structure -- Skeleton | |
| mose | skeleton is inside | |
| mose | I see something that is apart | |
| teedog | it'd be nice if we could keep it that way | |
| albrown | I don't know if I ever agreed with using existing pages in a structure | |
| teedog | how come? (marc requested that btw) | |
| gmuslera | albrown: manual is a good example .) | |
| gmuslera | manual should have some order, in general is a way to do multipage documents | |
| albrown | I like the idea of outlining using a structure, butr unless you could use an existing page in many structures and have it properly displayed as a member of the correct structure when it is used in a structure then using it would be wrong, I think | |
| gmuslera | you can do a cooperative work with a lot of people separating permissions at page level | |
| teedog | gustavo, al is not concerned about structures, but adding pre-existing pages to structures | |
| gmuslera | albrown: lets separate concepts from implementation. Concept is great, implementation is fixable 😊 | |
| teedog | right, al? | |
| albrown | gmisera, I understand what you mean | |
| albrown | For structures to be completely useful and valid we need to be able to use "any" page as a member of any structure and for the page to be smart enough to know if it is being accedssed by structure a or structure c or all alone, i think | |
| albrown | now you can use a page in two structures but the next and previous for both structures would show on the page and a user would have to be "smart" enough to folow the correct structure. Even if you access the page stand alone the next and previous links still show up. | |
| albrown | how would be the best way to seperate the concept and implementation guys | |
| marclaporte | I think cat and strucuture should be tied | |
| albrown | absolutely marc! | |
| marclaporte | we improve category system to add ordering and depth | |
| gmuslera | when following an structure, the "next" link should carry the structure you are viewing | |
| marclaporte | then we retire the "structure" feature | |
| albrown | then some sort of {toc-Cat_Struct} | |
| gmuslera | category=collection, structure=order | |
| marclaporte | advantage: cat system is also for other objetcs than wiki pages | |
| marclaporte | Gus: tes, but it has to be managed all at one place | |
| marclaporte | yes, but | |
| gmuslera | but you can have ordered collections, the next step of a page could be an image or an image gallery 😊 | |
| albrown | when starting from or following that cat_struct the struct= could part of the url? | |
| marclaporte | yup | |
| albrown | we should be able to use anything in this ordering-category thing | |
| gmuslera | integration, remember? 😊 could be nice to follow with order categories and from a page jump to a blog to an image to a quiz | |
| albrown | a blog or a post within a blog? | |
| gmuslera | maybe a listing of the blog | |
| albrown | I think that any object should be fair game within this |
koth: IMHO, I have to disagree with marclaporte that categories should be extended to provide ordering of items in it. Structures are better for this - for things such as manuals. As for how categories and structures should interact, I propose that there be a new feature option "categorize structure items together". When activated, there will be a means under tiki-edit_structure.php to categorize all items in the structure simultaneously and the usual way to categorize wiki pages will be replaced by a message and link to tiki-edit_structure.php if it is detected that a page is in a structure. To avoid problems with structure items being in multiple structures (hence causing conflicts), a check for this will be done before categorization is done, and an error message saying "items within structure can be categorized together only if they belong only to one structure" will be shown if necessary.
marclaporte: any solution which works is good! 😊