Category: Wiki Structure (book & table of content)

Wiki Structure (book & table of content)
Show subcategories objects

Name Type
"Hide namespace indicator in structure path" Doesnt work in "Structures drill down menu"
tracker item
"Open page as structure" seems to be broken
tracker item
"print all" from home of wiki structure
When you are on a page of a wiki structure, you can click on the print icon, but you will only print that single page.

The icon and option to "__print this page and all the subpages__" (= in the the sub-structure) right from there (without going through all the clicks at "Wiki > multiprint > select structure > print") would be very welcome, since the base feature to rpint the full structure exists.

From the home of the structure, it would print the full structure (as it can be done with one click from a structure within a Workspace through ((doc:AulaWiki)) mod, or through many clicks as usual, as explained above).

If the user is on a subpage of the structure, that button would print that page and all subpages from the same structure.

Does it make sense?
tracker item
"tiki-edit_structure.php" Add Pages To Current Node list truncates at 50 records.
"tiki-edit_structure.php" Add Pages To Current Node list truncates at 50 records.
tracker item
"tiki-edit_structure.php" Add Pages To Current Node list truncates at 50 records. Fix included.
The list of tiki pages presented for selection and addition to a structure is truncated at 50 records for no apparent reason and there's no way to add records >50 without running a filter.

I just parroted what I saw in tiki-admin_categories.php for its similar page list and it works.

The diff is below - hope I did that correctly.

*.backup is the original file from the official tiki releast. *.php is the version I modified.
tracker item
Add existing pages to structures at page edition time through the structures header box
tracker item
14.x: Print Structures doesn't print page titles just their numbers from toc
tracker item
18.x Structure reports inappropriate error if page already exists
tracker item
18.x Structures can create bad pages names
tracker item
3.0 bug: problem with categorize.tpl affects number of categories shown and use in Structures
The new 3.0 release of categorize.tpl doesn't show all the available categories to a user when a hierarchy of categories is used if the user is not in the 'top' category.

There are also problems with the use of categorisation in the Structures admin screen where categorisation of all the wiki pages in the Structure does not show the changes after submitting the request - although the changes are made.

No longer relevant
tracker item
User must have global permission tiki_p_edit for adding a new page in categorized structure also he has it in the categorie.
I defined a structure Helpdesk FAQ and a categorie Helpdesk.
Now I give a group Helpdeskadmin the permission tiki_p_edit (and a lot of others).

If a helpdeskadmin trys to add a page with the button on the top of the wikipage with over the toc, the message "You do not have permission to edit this page." appears.

The problem seems to be the following permission test in tiki-editpage.php:

// Permissions
$tikilib->get_perm_object($page, 'wiki page', $info, true);
if ($tiki_p_edit !== 'y') {
$smarty->assign('errortype', 401);
$smarty->assign('msg', tra("You do not have permission to edit this page."));

If I give the permission tiki_p_edit to the group, the helpdeskadmin comes to the wysiwyg-edit-page, also he gets a message like the page must have a categorie. I didn't analyzed that yet.
tracker item
Ability to use a structure as a menu {menu structureId=1}
I can't see the reason for the separation between the structures feature and the menu feature - structures are massively easier to create and edit, but only menus can be shown collapsibly. Separation of functions leads to confusion and harder support.
tracker item
Add ability to generate RSS from a specific structure (and maybe category)
The ability to subscribe to a specific structure via RSS feed would be very useful. Currently one can subscribe to an RSS feed related to the entire wiki, but if several groups are using the wiki for different projects or purposes or topics, this may not be at all useful. For example, on the Southern New Hampshire University wiki, we have the online faculty handbook plus a variety of page sets related to different course projects. Most faculty should be alerted of changes to the faculty handbook, which resides in a structure, and some students and faculty may want to track changes to structures involved with specific courses or departments, but few if any users need to be alerted of every change to the wiki as a whole. The ability to generate an RSS feed specific to a structure (and possibly also specific to a category) would be very helpful.
tracker item
add history & rollback capabilities to structures
add history & rollback capabilities to structures (record dump somehow when struct. changes, or allow saving structure dump for backup...)
This way, when the structure gets mixed by machine or human error, the structure can be rolled back to the previous state.

This way, we could be more open for registered users to manage http://doc.tikiwiki.org/Documentation (or others) without the risk of failure when nodes get moved to the wrong place (due to some bug in the code). Or due to mistake by benevolent newbies mixing things without bad intention.


UPDATE: Still desired for some LTS version. {sign user="xavi" datetime="2013-11-17T09:31:50+00:00"}
tracker item
add page to structure button regression
Bugs & Wish list
tracker item
add to structure: if page exists, update instead of refusal
This is annoying because you have to go via the admin structure instead of the simple add interface.

tracker item
adding a new page to a structure from an existing page
Adding a page by putting its name in the box at the top of a page in a structure no longer adds the page to the structure. It only creates the page.
tracker item
Admin option to force newly created pages to be part of the structure they were created from
Guys, I have to set up a company wiki, which is completely structured from top to bottom. So I noticed a very annoying thing about tiki.

Currently if you want to create a page, that is destined to be part of a structure, you have to create it using the navigation bar and set the option "as child".

But what if a user creates a new page from within a structred wiki page? I.E. If he simply sets up a new link to an non existing site. The new page is created as an orphan which is definitely a "no go" for a completely structured wiki. Pages like this have to be manually assigned to a structure by the admin.

So I request an option, that __forces pages created from within a page in a structure to be automatically part of the same structure__.

I guess even in pages like doc.tw.org this would be very helpful.
tracker item
admin user doesn't have permission to edit structures by default
After a clean install of r15460 w/ a new database, using the default enabled profile, i enabled structures via the wiki admin area.

Even though I was admin, I coulden't create / edit structures until I gave myself permission in the privileges settings.

The admin user should probably have most permissions by default, unless there is a particular reason to exclude a permission.

tracker item
admin user doesn't have permission to edit structures by default
After a clean install of r15460 w/ a new database, using the default enabled profile, i enabled structures via the wiki admin area.

Even though I was admin, I coulden't create / edit structures until I gave myself permission in the privileges settings.

The admin user should probably have most permissions by default, unless there is a particular reason to exclude a permission.

tracker item
Admin>Login>User defaults or Admin>Groups: Ability to Subscribe new users to specific Tiki objects
It would be lovely to set some new user defaults at
* Admin (home) > Login > User defaults, and/or
* Admin > Groups > (Edit a single group)

The ability to Subscribe/watch/monitor new users in the site or to that specific group, to specific Tiki objects.

Which tiki objects?: I would say, in this order:
# specific forums
# specific blogs
# specific calendars
# specific newsletters (ML: we can already subscribe groups to newsletters)
# specific wiki pages
# specific structures
# specific trackers
# specific categories
# new articles

This is specially useful for new users of the site, where they don't know yet how to subscribe to specific areas, etc. Very needed for educational scenarios, but I can see many other places where new users are a bit lost for some time while they learn how to use the Tiki site.

*[wish988|Forum: Let forum admins/moderators add groups and/or users as watching the forum]
*[tiki-index.php?page=Business%20Plans|Let small business start ups access collaborative sharing where the document being shared is not visible by anyone else]

Anywhere there is a watch eye, it should be possible for an admin to have group members watch this category
tracker item
Chinese in last item of a structure won't be translated after switch site language
tracker item
Better user notification when removing item from Wiki Structure
tracker item
tracker item
can't create new structure, because structlib has problem
When trying to add a new page to an existing structure or create a new structure, I got the following error:

Field 'structure_id' doesn't have a default value

I check mySQL DB tiki_structure table, find the field 'structure_id' is not NULL,I check structlib.php,I find structlib.php not set the value of 'structure_id',only set 'parent_id',I guess that struclib.php have wrong.
structure is important feature ,wish to solve this problem

__''kerrnel22:''__ Unable to reproduce this in CVS ...are you running CVS or release package 1.9.x? Also unable to reproduce in 1.10.0b1 CVS ...same question, are you running CVS or release package 1.10.0b1? If you are running the package in either, then it may be that the bug has been fixed in a patch to the CVS tree and you may need to wait for the next beta release.

re ''kerrnel22:'',i edit structlib.php line 202 :"$query = 'insert into `tiki_structures`(`parent_id`,`page_id`,`page_alias`,`pos`) values(?,?,?,?)';",to "$query = 'insert into `tiki_structures`(`structure_id`,`page_id`,`page_alias`,`pos`) values(?,?,?,?)'; ,then out tiki can run,and can create a new structure.
tracker item


The following is a list of keywords that should serve as hubs for navigation within the Tiki development and should correspond to documentation keywords.

Each feature in Tiki has a wiki page which regroups all the bugs, requests for enhancements, etc. It is somewhat a form of wiki-based project management. You can also express your interest in a feature by adding it to your profile. You can also try out the Dynamic filter.

Accessibility (WAI & 508)
Articles & Submissions
BigBlueButton audio/video/chat/screensharing
Browser Compatibility
Communication Center
Contacts Address book
Contact us
Content template
Custom Home (and Group Home Page)
Database MySQL - MyISAM
Database MySQL - InnoDB
Date and Time
Debugger Console
Directory (of hyperlinks)
Documentation link from Tiki to doc.tiki.org (Help System)
Draw -superseded by Diagram
Dynamic Content
Dynamic Variable
External Authentication
Featured links
Feeds (RSS)
File Gallery
Friendship Network (Community)
i18n (Multilingual, l10n, Babelfish)
Image Gallery
Inter-User Messages
Kaltura video management
Live Support
Logs (system & action)
Lost edit protection
Meta Tag
Missing features
Visual Mapping
OS independence (Non-Linux, Windows/IIS, Mac, BSD)
Organic Groups (Self-managed Teams)
Performance Speed / Load / Compression / Cache
Revision Approval
Search engine optimization (SEO)
Semantic links
Shopping Cart
Site Identity
Smarty Template
Social Networking
Spam protection (Anti-bot CATPCHA)
Staging and Approval
Syntax Highlighter (Codemirror)
Tell a Friend
Terms and Conditions
Token Access
Toolbar (Quicktags)
User Administration
User Files
User Menu
Webmail and Groupmail
Wiki History, page rename, etc
Wiki plugins extends basic syntax
Wiki syntax text area, parser, etc
Wiki structure (book and table of content)
Workspace and perspectives

Useful Tools