Feature Areas

• Dogfood on a *.tiki.org site
• Feature request

Hi,

I have the idea for a new feature or better to say a major extension of the use of existing features.

Areas would be related with the usability of the Website, where you can assigne content to certain perspectives in a way, that a link to this content will guide you sametime aswell to the content as to the related perspective.

Anonymous users (and registered) would find the content in the context of menus and modules, the webdeveloper decides.

I see "Areas" Important for certain usecases, it could be built with up mainly with existing features - only few code should be necessary.

See more description on http:dev.tiki.org/Areas

Cheers
Torsten

1) Areas is NOT a feature (any more)
2) Areas is a concept of structuring and setting up the navigation through out a website.
3) An Area is kind of a Spaces on a website. Areas divide the site into several subspaces with individual modules, menus and content which are "bend" together with categories.

On a website that does not use the feature "Perspectives", it is mainly possible to build "Areas" only with modules and theme control, which should be more easy in Tiki 10, since tere it is possible to limit and exclude module visibility to/from subtrees of categories.

If "Perspectives are used, the "Areas" will have to use the "Perspective" feature.
On a "Perspective" or "Workspaces" using Website it is quite easy to build Areas on Top of Workspaces, as a Workspace is just "converted into a "defined Area" by binding together the default category of the "Workspace" with the allocated "Perspective".

This can be done with a custom module and some smarty code, where we include some "Smarty" syntax.

Here is an example of the content of such a custom module, which I recommend to call it

"perspective_autoswitch"

The plugin "perspective_autoswitch" should be assigned to the "pagetop" and get the parameter "nobox=y" to make it invisible.

{if isset($objectCategoryIds) and in_array(1, $objectCategoryIds)}
{wiki}{literal}{REDIRECT(perspective=1) /}{/literal}{/wiki}
{elseif isset($objectCategoryIds) and in_array(2, $objectCategoryIds)}
{wiki}{literal}{REDIRECT(perspective=2) /}{/literal}{/wiki}
{elseif isset($objectCategoryIds) and in_array(7, $objectCategoryIds)}
{wiki}{literal}{REDIRECT(perspective=3) /}{/literal}{/wiki}
{elseif isset($objectCategoryIds) and in_array(9, $objectCategoryIds)}
{wiki}{literal}{REDIRECT(perspective=4) /}{/literal}{/wiki}
{elseif isset($objectCategoryIds) and in_array(10, $objectCategoryIds)}
{wiki}{literal}{REDIRECT(perspective=5) /}{/literal}{/wiki}
{elseif isset($objectCategoryIds) and in_array(11, $objectCategoryIds)}
{wiki}{literal}{REDIRECT(perspective=6) /}{/literal}{/wiki}
{elseif isset($objectCategoryIds) and in_array(12, $objectCategoryIds)}
{wiki}{literal}{REDIRECT(perspective=7) /}{/literal}{/wiki}
{/if}

Hints:

• The preference "Categories used in Templates MUST be activated to get themodule working (tiki.admin.php?page=category)

• To not unnessesarily extend the server load I suggest to assign the module specifically only to the affected categories.

• In each affected category the Redirect Plugin has to be approve once or you approve the plugin at tiki-plugins.php.

After the Areas as Feature and the file binderlib.php (originally tiki-perspectivebinder.php) turned out to be a dead end, at the TikiFestBarcelona3 (August 2012) Luci and me figured out a completely different way to generate Areas -> see "Solution"

This bug has been demonstrated on show2.tiki.org

Please demonstrate your bug on show2.tiki.org

This bug has been demonstrated on show.tikiwiki.org

Please demonstrate your bug on show.tikiwiki.org