Solved

Multiple separated home pages in Sharepoint Services 3.0

Posted on 2011-09-20
4
222 Views
Last Modified: 2012-05-12
We are running a Sharepoint Services 3.0 site on a Windows 2003 server without any problem until now, but now the customer faces the situation of the organization splitting in two halves. As a consequence we're wondering if there is any simple way to make two different home pages for the site, choosing one of them for every user depending on him belonging to a user group, for example. I understand that's something similar to audiences in MOSS, but we are limited to SPS 3.0. Any ideas?
0
Comment
Question by:quicogil
4 Comments
 
LVL 38

Expert Comment

by:Justin Smith
ID: 36566776
Not possible out of the box.
0
 
LVL 16

Expert Comment

by:jessc7
ID: 36567526
If you could create two SharePoint groups, it seems like you could do it.

If you created a JavaScript redirect, and secured it somehow based on the SharePoint group the user was a member of, you could send them to a different page depending on which redirect was visible to their web browser.

I forget in WSS 3.0 if you can secure a Content Editor web part on a page to a particular SharePoint Group. You would probably have two, and secure by group, with the respective JavaScript redirect in the appropriate Content Editor web part.

There are probably other ways to accomplish this method as well.
0
 
LVL 2

Accepted Solution

by:
rayaan_wasty earned 500 total points
ID: 36579540
I can think of one solution , distribute the users into two permission groups and based on the permission re-direct them to the relevant page . or if their is a user profile property that can distinguish between the two then you can avoid the above step , after this simply deploy a webpart that would redirect based on the user property.
It will be a custom development but will be fairly simple.
0
 

Author Closing Comment

by:quicogil
ID: 36579655
I'll be going for something very close to this, but instead of troubling myself with webparts and deployments I'll be trying first putting a default.aspx with just some inline code that hopefully will do the trick. I know it's not the right way to do it, but we need something fast and don't want to mess with deployments anymore than what's strictly necessary (we've had some bad experiences in the past). Thanks a lot everyone for your comments.
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

There is one common problem that all we SharePoint developers share: custom solution deployment. This topic can't be covered fully in this short article, so all I want to do in this one is to review it from a development-to-operations perspectiv…
A quick step-by-step overview of installing and configuring Carbonite Server Backup.
This Micro Tutorial will teach you how to censor certain areas of your screen. The example in this video will show a little boy's face being blurred. This will be demonstrated using Adobe Premiere Pro CS6.
As a trusted technology advisor to your customers you are likely getting the daily question of, ‘should I put this in the cloud?’ As customer demands for cloud services increases, companies will see a shift from traditional buying patterns to new…

920 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now