Category: Wiki Structure (book & table of content)

"Hide namespace indicator in structure path" Doesnt work in "Structures drill down menu", but works in the Structure navigation bar. It used to work before though.

Show instance http://fvtorres-11800-5959.show.tikiwiki.org
User: admin
Pass: 12345

I set the "Open page as structure" option on tiki-admin.php?page=wiki#contentadmin_wiki-2 but when I navigate to the page, only the page itself displays. There's no structure navigation, etc.

I tried using both underbars and empty spaces in the address, as well as plus signs.

If I go to the page from tiki-edit_structure.php, then the structure navigation, etc. display as expected.

This is in my localhost WAMP installation. I haven't tested yet in a remote server or show instance.

Update: Created a show instance, but URL for that was initially "http://chibaguy-342-6248.show.tikiwiki.org/snapshots/". Why the snapshots directory? I went up a level to find the show instance itself.

In the show instance, "Open page as structure" seems to work as expected. I'll have to check if I have some local glitch, and will revise this bug report later.

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?

"tiki-edit_structure.php" Add Pages To Current Node list truncates at 50 records.

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.

Add pages to structures at page edition time

The workflow in this screenshot below worked when adding the name of a brand new page, or when adding the name of a pre-existing page. In both cases, that page was added to the structure as a sister of the current one.
{img src="http://doc.tiki.org/display628?x=600"}

But this has stopped working in 12.x, for the cases of pre-existing pages. It's been reproduced in doc.t.o. And since then, it has never been fixed.
This is a missing feature which facilitated non-admin users to add pages to structures in an organic way (without the need of an admin, or a manual on how to use structures).

Hi, this feature used to work in 6.x or so. I'm trying to use it for production, and it doesn't work in 14.x (nor in 12.x, etc)

When you print a whole structure, you expect to have page names added in the titles of sections from the html printed document, and there are only numbers shown there, not the title.

Reproduced here in a show instance, thanks to the "Structured Master Documents" profile:
http://xavidp-1553-5661.show.tikiwiki.org/tiki-print_multi_pages.php?printstructures=%255B%25221%2522%255D&find=&print=Print
u: admin
p: 12345

{img fileId="997" thumb="y" rel="box[g]"}

If a new structure is created using an existing wiki page as the root of the new structure, an error is reported "TikiLib:: create_page: Cannot create page "user-page-name", it already exists.)"

{img fileId="1260" thumb="box"}

TW15.x did not report such an error.

A user typo whilst creating a structure can create a new page which then isn't (easily) accessed.

Whilst creating a new structure and adding pages with aliases using the "Tree" feature, if hyphen space greater-than rather than simply hyphen greater-than is entered the new page is created without an alias but with a longer that expected page name.

For example
Test_01 -> Page1 creates new page called Test_01 and alias Page1 as expected.
But
Test_02 - > Page2 creates a new page called "Test_02 - > Page2" with no alias.

Accessing this page and removing it is challenging :-))

--(Can't currently create a show instance for you, no database connection available, but I can reproduce this on the demo 18x/system)--

Using the Structures "next page" button from page Test_01 causes a wiki error "Page not found" for "Test_02 - Page2" (sic without greater-than sign).

Likewise wikilink from toc generated on pages within the structure also results in "Page not found".

Adding the plugin listpages with options find="Test_0" to the root of the structure shows the pages as expected.

Note the wikilink URLs generated by toc and listpages are different, but wikilink from listpages also results in the same "Page not found error" for the same page "Test_02----Page2"

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

{syntax type="tiki" editor="plain"}
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."));
$smarty->display("error.tpl");
die;
}

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.

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.

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.

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"}

{syntax type="tiki" editor="plain"}

{syntax type="tiki" editor="plain"}
This is annoying because you have to go via the admin structure instead of the simple add interface.

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.

{syntax type="tiki" editor="plain"}
At the Structure admin screen you can add text to be used as a page alias for any of the pages in the structure - useful to show more meaningful text or to use characters that cannot be in the 'real' page name.

This works fine for all the subpages in the Structure but when adding the alias text to the top/main page of the structure it triggers an Error which says:
''Your attempt was blocked as a suspected malicious operation. If you are a real person and this is an incorrect report, please report to the site administrators with the following code: CRSF_some_different_number_each_time''

The edit will eventually happen if you keep trying but each attempt still shows an Error message.

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.

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.

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.

{syntax type="tiki" editor="plain"}
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.

Related:
*[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

if build a structure as below
item1
item2
中文A
中文B
中文1
中文2

the last level won't be auto translated in random case, but if put as below, it works.
item1
item2
中文B
中文1
中文2
中文A

looks the problem is due to boundary handling issue for last item in a Structure.

Is it possible to automate the creation of a structure(s) eg( run every night as a cronjob). I really like the keyword concept list and I think this could be deployed as a feature for sites that are drowning in wikipage content and maintaining menus is just too trouble sum.
Is the keyword page auto generated? If you could set a category to include all pages in that category in the auto-maintained structure.

When trying to remove an item from a Structure, the page refreshes and there are 2 options at the top of the page that aren't very obvious to the user.

This is inconsistent with our typical Tiki UI. Usually we either have a Popup with a request for action OR a page that requests Confirmation.

I would like to see a Popup with request for action