Loading...
 
Skip to main content

Custom Share Module 0.1dev

Features / Usability

Features / Usability


Two sites (sort of) using the one tiki?

posts: 27 Australia

Hey all...

We run tikiwiki for our intranet. However we're a school and we'd like to have separate sections for staff and students. We'd have them both enter the site on separate pages (by using aliases on the webserver or something like that.. that's the easy bit). The pages would have some similar components but some different ones, so for example, on the staff entry page we might have a different poll showing to the student one, and there might be two different links modules between the pages.

Is this possible without major hacking of things to get it working? And if so, how could I do it?

Thanks.

posts: 2881 United Kingdom

Hi There

RecipeMultiTiki

Should have the answers you need
Highly experimental in 1.9 aka HEAD, but 1.8 should be good.

Damian

posts: 27 Australia

Sorry,

That shows how to setup 3 separate tikis with three separate databases using the http headers in the request to differentiate.

I want one tiki with two entry points that are mildly different (ie. one shows some modules the other doesn't). For example I would have the domain point to http://intranet.domain/tiki-index.php?page=Staff for the second entry point, but I need to construct that page so that the modules showing are different to what you'd get if you went to http://intranet.domain/tiki-index.php.

Is that more clear? It's a tough one to explain! ๐Ÿ˜‰

> Damian:
> Hi There
>
> RecipeMultiTiki
>
> Should have the answers you need
> Highly experimental in 1.9 aka HEAD, but 1.8 should be good.
>
> Damian
>

posts: 34 Canada
I think this is possible if you turn off 'display modules to all groups always' from Admin->General and then go into administration of modules and for each module assign which groups you want to be able to see the module.
posts: 27 Australia


It's not really something that's achievable using groups though is it? Because these are entry pages (the first page the user sees in the site) they need to appear this way before the user logs in.

L8r.

> superdude:
> I think this is possible if you turn off 'display modules to all groups always' from Admin->General and then go into administration of modules and for each module assign which groups you want to be able to see the module.


posts: 27 Australia

Sorry,

That shows how to setup 3 separate tikis with three separate databases using the http headers in the request to differentiate.

I want one tiki with two entry points that are mildly different (ie. one shows some modules the other doesn't). For example I would have the domain point to http://intranet.domain/tiki-index.php?page=Staff for the second entry point, but I need to construct that page so that the modules showing are different to what you'd get if you went to http://intranet.domain/tiki-index.php.

Is that more clear? It's a tough one to explain! ๐Ÿ˜‰

> Damian:
> Hi There
>
> RecipeMultiTiki
>
> Should have the answers you need
> Highly experimental in 1.9 aka HEAD, but 1.8 should be good.
>
> Damian
>

posts: 34 Canada
I think this is possible if you turn off 'display modules to all groups always' from Admin->General and then go into administration of modules and for each module assign which groups you want to be able to see the module.
posts: 27 Australia


It's not really something that's achievable using groups though is it? Because these are entry pages (the first page the user sees in the site) they need to appear this way before the user logs in.

L8r.

> superdude:
> I think this is possible if you turn off 'display modules to all groups always' from Admin->General and then go into administration of modules and for each module assign which groups you want to be able to see the module.


posts: 1001 Canada
If you think you can do what you want with registered users, anonymous is a group too just like others so there should be no problem.
posts: 27 Australia

Yes,

However, that's beside the point. This would just result in the two entry pages both displaying the same modules (albeit, per group) wouldn't it? I want different modules displayed (or not displayed) depending on the page the users enter the site on.

> Chealer9:
> If you think you can do what you want with registered users, anonymous is a group too just like others so there should be no problem.

posts: 34 Canada

Alright, i think i'm closer to understanding. Try admin->features icon->bottom of the screen is 'General Layout Options'->check 'Layout per section'->click change preferences->click 'admin layout per section'

Edited: Actually i don't think this really does what your trying to do. What you can do with this is use it to show the left column of modules on certain sections of the site and show the right column on others, so that way you can control the modules shown for different sections. But this wouldn't help if you wanted different modules shown for different Wiki pages. Hmm, maybe someone else has some more helpful suggestions.

> Speculator:
> Yes,
>
> However, that's beside the point. This would just result in the two entry pages both displaying the same modules (albeit, per group) wouldn't it? I want different modules displayed (or not displayed) depending on the page the users enter the site on.
>
> > Chealer9:
> > If you think you can do what you want with registered users, anonymous is a group too just like others so there should be no problem.
>


posts: 27 Australia

Yes,

However, that's beside the point. This would just result in the two entry pages both displaying the same modules (albeit, per group) wouldn't it? I want different modules displayed (or not displayed) depending on the page the users enter the site on.

> Chealer9:
> If you think you can do what you want with registered users, anonymous is a group too just like others so there should be no problem.

posts: 34 Canada

Alright, i think i'm closer to understanding. Try admin->features icon->bottom of the screen is 'General Layout Options'->check 'Layout per section'->click change preferences->click 'admin layout per section'

Edited: Actually i don't think this really does what your trying to do. What you can do with this is use it to show the left column of modules on certain sections of the site and show the right column on others, so that way you can control the modules shown for different sections. But this wouldn't help if you wanted different modules shown for different Wiki pages. Hmm, maybe someone else has some more helpful suggestions.

> Speculator:
> Yes,
>
> However, that's beside the point. This would just result in the two entry pages both displaying the same modules (albeit, per group) wouldn't it? I want different modules displayed (or not displayed) depending on the page the users enter the site on.
>
> > Chealer9:
> > If you think you can do what you want with registered users, anonymous is a group too just like others so there should be no problem.
>


posts: 1001 Canada
I don't think you can do that without code. Of course, there's always PluginModule.
posts: 27 Australia


Yeah, it's proving difficult. Maybe someone in the future could think about implementing a way to show/hide modules when displaying a page?

From what I know of it PluginModule is just about embedding modules into pages.

Layout Per Section, that only allows you to show/hide the top/bottom bars and left/right columns.

This doesn't look promising.

> Chealer9:
> I don't think you can do that without code. Of course, there's always PluginModule.

posts: 2881 United Kingdom

> Speculator:
>
> Yeah, it's proving difficult. Maybe someone in the future could think about implementing a way to show/hide modules when displaying a page?
>

Maybe that someone is you ? ๐Ÿ˜‰

Damian


posts: 27 Australia


Yeah, it's proving difficult. Maybe someone in the future could think about implementing a way to show/hide modules when displaying a page?

From what I know of it PluginModule is just about embedding modules into pages.

Layout Per Section, that only allows you to show/hide the top/bottom bars and left/right columns.

This doesn't look promising.

> Chealer9:
> I don't think you can do that without code. Of course, there's always PluginModule.

posts: 2881 United Kingdom

> Speculator:
>
> Yeah, it's proving difficult. Maybe someone in the future could think about implementing a way to show/hide modules when displaying a page?
>

Maybe that someone is you ? ๐Ÿ˜‰

Damian


posts: 63 United Kingdom

WARNING: MONSTER POST

Have you considered using group homepages?


Stay with me on this one. It's a long post but I think it hits on all the things you want. There is a summary at the bottom.

1.8.2 includes this feature which will redirect users to a wiki home page you specify on a PER-GROUP basis, that way all students and techers will see the same stuff until they login, then students, when logging in will get redirected to - for example - a page including "Don't forget your homework!!" or something equally evil, while teachers are forwarded to - example - a teachers list of things to worry about in the near future. Get the idea? If tiki can be made to differentiate between the groups, I think group-homepages should allow you to modify the page they start by seeing.

Then you can use the PluginModule to embed the relevant modules to that page. Viola, groups go to different home pages with different modules in 'em. Not exactly right I know, but you can then (if you were so inclined) drop the group-specific modules from the left and right cols adn just have default stuff like navigation and search in there etc.

You could go a step further and add groups for specific year-groups of students so that the later year groups get different homepages to the newer students. So you can include "Welcome to the school website new students" articles and orientation information on the starting year page and "upcoming events for X year" on the later years homepages.

The only problem with this is that each user needs their default group set to be the relevant group manually for group-hompages to work. Otherwise I think they are treated wrongly on accasion, which would be a pain with several hundred users.

Although you could make this play in your favour by assigning the teachers group with a custom homepage and use the regular registered group for students. In that way you don't have to go and assign hundreds (making assumptions about the number of students, I know) of users one by one with specific groups, but the teachers can be manually assigned to the teachers group giving a different homepage.
(Registered but non-"default gruoped" users will default to the homepage specified in admin > general)

Alternatively you could modify the registration system to make registered users default groups "registered" - you'd still have to manually specify teachers.
Then again - if you're authenticating outside of tiki (Did I understand that right?) then you may need to modify the "add users if not in tiki" logic to set the default group instead.

You could also modify the group-homepage system to accept full URL's instead of wiki page names and use HTML pages for group homepages with extra stuff and Custom Home for the default with school information in the form of articles / RSS modules etc. Maybe I'll add that to my list of "things I wanna mod" myself.

okay, I know I never put things in an easy-to-follow way so here's the simplified breakdown:

  1. Students authenticate as registered users of tiki,
  2. Teachers have a custom group with a group home-(wiki)-page set to something other than the default,
  3. Teahers must be manually assigned the techers group AND have it set as their default group,
  4. The teachers group home wiki page can be secured from students using per-object permissions I think,
  5. Modules can be embedded into the teachers group home page as suggested already,
  6. Modules in the left / right cols can be set to disply for teachers but not students.


Note if you don't include the students (registered) group in the techers group when creating it (include the permissions but not the group), turn off show modules to all users always, you should be able to to get exclusive per-group modules shouldn't you?

yes, no, Maybe?
RW

posts: 27 Australia

Okay,

Well, we're getting closer, now it seems you guys have a fairly good grasp of what I want to do.

What would be an interesting thing to try would be to pair an idea like this with the mechanism used in RecipeMultiTiki. But instead of using the http virtual host headers to point tikiwiki at a particular database, rather assign one of two groups with the same perms (or more maybe) as anonymous, thereby setting up the possibility of defining things for different entry points automatically, based on group membership.

Anyone care to guess at how hard/possible this is. I'm no coder and my knowledge of PHP, and my time are limited, but I could have a closer look sometime down the track.

L8r.

> RussWilde:
> !WARNING: MONSTER POST
> !!Have you considered using group homepages?
>
> Stay with me on this one. It's a long post but I think it hits on all the things you want. There is a summary at the bottom.
>
> 1.8.2 includes this feature which will redirect users to a wiki home

snip

> yes, no, Maybe?
> RW

posts: 2881 United Kingdom

Hi

How did you get on with this? Im interested to see, as it could be the answer for those real security geeks, who want a read only based site then a full access.

You could always run a stripped tiki on the server, and then a local PC with the remotes database connection giveing you all the FULL tiki.

Stripped tiki wouldnt contain any editing interface/admin section.

Damian
too many ideas, and not enough hours