Solved

Multiple separated home pages in Sharepoint Services 3.0

Posted on 2011-09-20
4
211 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
Comment Utility
Not possible out of the box.
0
 
LVL 16

Expert Comment

by:jessc7
Comment Utility
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
Comment Utility
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
Comment Utility
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

What Should I Do With This Threat Intelligence?

Are you wondering if you actually need threat intelligence? The answer is yes. We explain the basics for creating useful threat intelligence.

Join & Write a Comment

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…
ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

744 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

15 Experts available now in Live!

Get 1:1 Help Now