Perspectives are to override a preference. Think Theme Control but for any of 1000 preferences. In fact, it's all the Preferences that have been converted to Dynamic preferences less the features which shouldn't been overrideable per workspace.
As user with admin rights.
- Ensure that you have enabled the feature (Admin > Features)
- Create one perspective through tiki-edit_perspective.php Provide any name.
- Search for preferences at the search box that you will see at the bottom. For instance, logo, theme, site title, home page, ...
- Once found the preference that you were looking for, drag it and drop it on the section above corresponding to the perspective that you have created.
- Repeat the previous step as many times as needed
- Click at Save
You can edit this perspective at any time on a later stage.
If using different subdomains, you can set them up linked to perspectives through:
Admin > General > General configuration > Multi-domain > Multi-domain Configuration:
- subdomain1, 1
- subdomain2, 2
- whateverdomain, IdX
See: module perspective
Another trick is to use a link like
This is a one time use of that perspective, as after, the perspective reverts back.
Starting in Tiki5, you can manage via tiki-edit_perspective.php (It is probably better to be in the default perspective when you are using tiki-edit_perspective.php)
To get going quickly, you can use the Jailroot demonstration.
Starting in Tiki7, you can switch and stay on the same page by adding a &back to the switch perspective link.
- PluginPerspective permits to display content based on the reader's current perspective
Mobile mode is essentially a perspective. If you want some modules to appear or not to appear in your mobile perspective, find out what your mobile perspective ID is (tiki-edit_perspective.php) and configure Modules accordingly. For example, If you wish to hide your login box in mobile version(mobile perspective) of your website, then simply go to Admin>Modules>login_box>visibility>perspective> Enter value "0" and click assign. By doing so your login box would be visible only to your original website and invisible to your mobile perspective. This method can be used to simplify your mobile version.
- Note: "0" is default perpective for tiki website while "1" or "2" etc are for your mobile perspective or other custom made perspectives.
Generally speaking I promised to extend the perspectives related documentation since a while.
Still I am too busy with private stuff and not completely up to date with all knowledge about perspectives, workspaces etc.
For that we do not forget things and that other users can anyway benefit from the help that was given to me, I just summarize my points where I think we are right now.
I do that a bit quick and dirty and will do a wrap up later on.
different points of view / layers of the website
"responsible" for an important part of the roles&rights / permissions management
- category jail:
applies to a perspective and is kind of a preference
limits search results and listings to content wich categories are applied to a category jail in a perspective
categories IDs are typed in as numbers, seperated by semicolons
search results just give the typed in perspectives
all content can be seen in all perspectives at this point, if appropriate rights
For a start, I just name the perspectives and categories the same way and set them up in the same order.
So the first some same named categories and perspectives have the same Ids, what eases work especially for a beginner with that.
At some point, thats not working out any more, but then it woulkd be still possible to remind the IDs to the names.
Names of perspectives and categories should apply either to the content or to the use case of the perspective or to both, if possible That eases life aswell.
- perspectives plus categories -> workspaces:
with perspectives and categories and some kind of smart structuring you can +create kind of "logical areas" in between the Tiki website.
that means you can create spaces for workgroups, usergroups, subwebsites, etc.
perspectives and categories are the features with that you can create workspaces, thus a workspace is more a logical area of the site and not a feature by itself.
using for ex. subdomains for workspaces, not only the categories can be jailed in respect of search results and listing, but further more the hole content of different perspectives can be kept apart from each other independantly.
- swith perspective and stay at content
recently a nice feature was added by Louis-Philippe:
at the perspectives module, there is a tic box now, where you can set eather switching the perspective staying in the existing content, for ex. to just get different modules or to switch to the new perspectiveshome page.
- go to a specific page in a specific perspective
once you type the adress http://foo.bar/PageName, you will be sent to PageName in the default perspective.
using perspectives for navigation purposes you would need a number of subdomains, if you´d like users be able to copy and paste links to appropriate content/perspective combinations
using additional ?perspectiveId=X in the context: http://foo.bar/PageName?perspectiveId=X you will be linked to PageName in Perspective X (thank LPH for mentioning that)
a shortener like http://foo.bar/PageName?PId=X is requested.
- next focus
next to learn would be how to use Datachannels on the one hand – to setup automatically a set of a number of perspectives / categories / workspaces / project management tools with preset configuration
organic group including leadership and demoting / promoting etc.
Following an excerpt of an IRC conversation between mikebeary and nkoth, that the both guys allowed to use for the documentation:
can someone please give me a general idea of how workspaces are different than perspectives? I'm having trouble finding a concise definition
a workspace is a use case - there is technically not really a workspace feature. Perspectives, combined with other features such as category jailroots are the features that enable
so its a general term that just describes the work area a person is in based on what they've clicked on, who they are, etc.? As opposed to a separate page or something?
yes, workspaces is a rather general term describing a work area that could consist of a certain way it looks, certain permissions that exist in that state, and things presented, etc..
I want to create a wiki that begins with a site for all the colleges in a Missouri, from which you select your college, and then select your campus and then your club. Would each of the different colleges just have their own workspace and then each campus would have their own workspace, etc? as opposed to making a totally separate page? I'm guessing perspectives and jailroot features would bring them to their workspace based on them selecting their college or their campus?
possibly , but you have to consider what is your reason for dividing up the wiki into multiple workspaces to begin with.
Is it to prevent one person from seeing the other group's things?
Is it to present a different screen layout?
Is it to limit the amount of things a person is seeing while in a particular workspace so that he is not information overloaded but he can still switch between workspaces?
not to limit, but just so that each level can have their own calendar, their own forums, their own file galleries, etc.
Sounds like you need to create some categories some perspectives and then configure each of the different perspectives to have different jailroot
each perspective would have also its own different home page so that when you switch to it
(the perpective), the user sees that home page
and while they are in that perspective they are exposed only to things in the category jail root of that perspective
really, it'd be the same .php file, but a different theme kind of thing?
basically tiki has a lot of preferences right?
for each perspective you can have a different "setup" of preferences
so the possibilities are really up to your imagination the UI is at tiki-edit_perspective.php
you search for a pref, drag it into the perspective and configure it (basically overriding the global value) for that specific perspective
So say for instance I go to Missouri's website. I'd be at the tiki-index.php. Then I'd select my local college. Are you saying at that point, I could be at my college's "site" but without ever leaving tiki-index.php? I'd just be changing everything based on jailroot and persepective settings?
the link to switch perspectives is tiki-switch_perspective.php?perspective=3 to switch to perspective 3
So that could very well be how you "goto" to the college's "site" which is perspective 3
And essentially what I’ve done by selecting my college's "site" is to select a different workspace
technically speaking, you switch to a different perspective which yeah I suppose it sounds synonymous with workspaces, but the point is that a perspective could be used for something as simple as say, having a different page header and not necessarily to the extent of creating workspaces which is what you are doing.
ok, that makes sense.
and what exactly is a jailroot
it is a pref (and so you can configure it globally or for any specific perspective)
Basically it is a list of category IDs . If you set it to e..g 2, 3, and 5, then users can only see/search for/are exposed to items that are in categories 2, 3, and 5
so kind of like bulk-processing for perspectives? So you don't have to change a whole lot of perspectives to achieve what you can with categories?
well, the point is that categories are just that, you put things in them and you can set permission for them by setting a category jailroot for a perspective, say the college's perspective
you are basically saying that "while a user is in the college's 'site' he is exposed only to things inside those categories specified in that jailroot
it could just be one category, or it could be many categories - it's up to you
if you could perhaps cut and paste this conversation into the wiki page where you expected this info to be in the first place on doc.tiki.org, it could be useful for now, until you have developed more fancy documentation liek that youtube video you talked about
Ok, I will definitely do that.