Loading...
 
Skip to main content

Features / Usability

Forum List Topic List

 
Thread actions
Print this page
  • Print all pages

    • Subpages?

    Posted by Tikij

    Hey guys. Is there a simple way to create subpages? I've read about structures, but I just want something simple like in mediawiki (putting a / to create a subpage):

    site.com/dog
    site.com/dog/pitbull
    site.com/dog/shihtzu

    Something like that.

    Reads: 5770
    Posted by Rick Sapir / Tiki for Smarties

    In Tiki, all the wiki pages are "flat." If you want to show a parent-child relationship between pages, use a structure.

    Alternatively, you can simply use categories and subcategories:

    • Category: Dog
      • Subcategory: Pitbull
      • Subcategory: Shihtzu

    Then simply categorize the wiki pages, as necessary.

    HTH,

    - RickQuestion | My Tiki Blog | My Tiki UserPage

    Why be a dummy? Get smarty! TikiForSmarties.comQuestion
    Tiki for SmartiesQuestion, your source for the best (and only) Tiki books, guides, and tutorials.

    Posted by Tikij
    Thanks ricks.

    Posted by michael314

    I second Tikj's request.  Categories and Structures are not suitable for creating true-subpages.  I don't want flat pages.

    For instance, neither categories nor structures seem to make it possible to create pages which always have the category in the URL.  I can create a structure called, e.g. Dog, and if I access the structure from the Structure page and click on a page under Dog I get a URL that ends with "?structure=Dog" which I could use to do an Apache re-write so that the URL looked something like "http://site/Dog/DogPage1", but then there are many cases where the structure parameter get dropped from the URL (for instance, if it is accessed from the List Pages page), which breaks that nomenclature.

    Likewise, categorization doesn't seem to happen until a newly created page is actually saved, which means that I can't enforce a user being required to create pages in a given category, because the only way to do that is to deny global edit permissions and grant category edit permissions, but then they can't create any new pages at all!  This is important because you can't use Flagged Revisions on uncategorized pages, and an admin that is watching a category to see when there are page they need to approve won't get any notification if the user forgets to categorize.

    Namespaces seem like they might work, but (1) they don't allow you to use the '/' character as the separator, and (2) they don't seem to be permissionable, so I can't e.g. require that a user in Group X is required to always use namespace X for pages they create.

     


    Posted by Torsten Fabricius

    Hello michael314 and Tikij,

    I am thinking about such a feature since a good while, but I do not see that this will be implemented in the next future.
    I would see such a domain-category tool necessary for a real multisite capability and there might be other use cases aswell where it could be an asset.

    If I am right, I have seen such in Drupal and I thibk that was made with some kind of rewrite rule or so.

    On the other hand I do not see it as a very important or necessary feature for Tiki at this time - we will see in future. Anyway, I am quite interested about the use cases where you think you need that.

    You mentioned namespaces.

    For a collaborative Intranet platform I use namespaces with the seperator -- (two dashes).

    Using perspectives and wiki structures I can indeed force the creation of auto-namespaced and auto categorised pages.

    I a perspective non-namespaced links can optionally auto-link to their namespaced expressions and you can hide the namespaces in menus and table of contents.

    So depending on your plans and concepts, namespaces and structures might possibly provide what you need.

    Regards,
    Torsten


    Posted by Rick Sapir / Tiki for Smarties
    neither categories nor structures seem to make it possible to create pages which always have the category in the URL

     
     Correct. Only the page's name is reflected in the URL. This allows you to recategorize a page or add it to a structure without changing the URL and breaking any incoming links.
     

     

    I can't enforce a user being required to create pages in a given category

     

    You can use the Force and limit categorization... option to require users to select from a set of categories for newly created pages. Pleasesee the docsQuestion for details.

    Additionally, if you're using the Quick Edit module to create new pages, you can use the categId paramter to automatically make the newly created page be in a specific category. Please see the docsQuestion for details.

     

    HTH,

    - RickQuestion  |  My Tiki Blog |  My Tiki UserPage

    Why be a dummy? Get smarty! TikiForSmarties.comQuestion
    Tiki for SmartiesQuestion, your source for the best (and only) Tiki books, guides, and tutorials.
    Posted by michael314

    Thanks for your reply Rick.

    There is actually no issue with breaking incoming links, because we are trying to model Categories/Groups on organization structure.  Every document belongs in exactly one department, and the chances of one department's documents being re-categorized to another department are almost non-existent.

    Is it possible to create a Quick Edit module to parameterize the categId parameter?  One issue with the Force and limit categorization... option is that it seems to force the same categorization for everybody, but we need each department to be forced into their own category.  I was looking at the Wiki Argument VariablesQuestion page in the hopes that there was a permanent variable to refer to the user's default group or something to otherwise set up the correct category ID for the user.

    Posted by michael314

    Ok, so I created a page with just a quick edit module in it, with the desired categId as well.   But the Quick Edit module doesn't appear to automatically assign the new category. If I create a new page with it as admin, there are no categories selected under the category tab, and if I try to use it as a non-admin who only has permission to create in this category, I get redirected to the unauthorized page.

    But when I try to edit the page to verify everything is correct, the page won't load.  As in, I click on the edit button, and I get a new blank page with no content (checked in developer tools, it's an empty head and body), but the lock on the file is acquired so another user can't edit without overriding.

     

     

    Posted by michael314

    Maybe a configuration somewhere is wrong?  Not sure how to troubleshoot this and my login here doesn't work there.  Is there some way I can register to get sandbox access on that page so I can (e.g.) edit the page or look at permissions / admin settings to compare against my own?

     

    Posted by michael314

    Thanks Rick, that did the trick.

    Turns out that the failure to edit a QuickEdit page is a bug when in WYSIWYG mode (which we use exclusively).  I've posted a query to the dev page asking if this is planned to be fixed.  It's not really a show-stopper that such a page is not editable at the moment, just something to work around.

    The more serious problem is that it doesn't seem possible to use a QuickEdit module to allow a user to post to a category.  I created a new Category "Production" which is editable by a new group "Production" and added a user "prod" (password "prod1234") to that group, but when they try to create a new page is says permission denied. If I try to create a new page from the quickedit as "admin" the editor comes up, but under the "Categories" tab there is no category selected.

    I must be doing something wrong because I see the correct behavior from the page you created.  However, I can't edit the page to see what the source looks like - the default editor doesn't have a "Source" button that I can find, and when I enable the WYSIWYG editor I run into the above mentioned bug.

    Can you tell me how to get into the source so I can see how you did it?

    Posted by michael314
    To answer my own post, I found the "Source" button at the bottom of the page to let me see the actual source.
    Posted by michael314

    Ok, viewing the source it appears that the correct parmeter is "addcategId" and not "categId" as this pageQuestion claims.

    With that change, admin can create a new page and the category is assigned. But "prod" still can't create a new page.  (On my tiki, it just redirects me to the not-logged-in-user page, and I haven't had enough luck getting the editor to recognize my changes on the demo tiki as a plug-in, it currently is just showing up as plain text for some reason.  Out of time for now, I'll look at it more later.

    Posted by Rick Sapir / Tiki for Smarties

    Sounds like a permissions issue (if it works for the Admin but not other users. Confirm that your Group and Category permissions are correct. Remember, the Category permission will override the Group's permisison.

     

    Posted by michael314

    http://demo.tiki.org/12x/CategoryTesting2Question

    user "prod", password "prod1234".

    User "prod" gets permission denied trying to create a new page from QuickEdit on above page.  New page is auto-categorized by QuickEdit to category 4.  User "prod" in Group "Production"; Category 4 gives that group all Wiki permissions, which should override the group permissions, which only give view permission.

    So my understanding is, since "prod" has all wiki permissions in category 4, this should allow "prod" to create a new page in this category, but it is not working.

    Posted by Rick Sapir / Tiki for Smarties

    Ah... I think I understand now...

    You need to grant tiki_p_edit permission to the Prod group. Then, remove the group's edit permission for the non-Prod categories.

    Because the pages are not categorized until they're saved, without the Group-level permission, users in the Prod group can't create a new page.

    HTH,

    - RickQuestion  |  My Tiki Blog |  My Tiki UserPage

    Why be a dummy? Get smarty! TikiForSmarties.comQuestion
    Tiki for SmartiesQuestion, your source for the best (and only) Tiki books, guides, and tutorials.
    Posted by Torsten Fabricius

    This is sad, but true.

    And it is one of a number of reasons, why I for example do intranet and public website on two seperate instances - configuration requirements are too different for some use cases.

    T.