Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

bpcf.aspx

  Asked By: Tara    Date: Jun 06    Category: Sharepoint    Views: 1366

What I want:
When someone goes to a given Document Library (this one is called
"NatureLink") and clicks on New Document, I want two links to show up
of the basic page.

I have the default document type for the library to be a "Basic Page."
I see where SPS goes to the _basicpage.htm and it in turn looks at
/_layouts/1033/bpcfNL.aspx. Is it impossible to make a basic page with
what I want and force it as the default.aspx for that library?

I tired saving what I wanted on a blank page (save the links) as a
dwt. But I don't see how I would get it to look for that.

I am doing this from a Document Library in a Sub Area of SPS. It may
be that it's easier to try this from a WSS site...?

Share: 

 

8 Answers Found

 
Answer #1    Answered By: Christop Mcfadden     Answered On: Jun 06

First DWTs are not recommended.

Second, calling a custom bpcf page  should be done from a custom list definition.

Third, SPS 2003 is an odd bird abandoned in the next release. IMHO, everything
is unnecessarily over complicated by SPS 2003. OK, that is an overstatement but
the sentiment is true. Remember, stick to the intended purpose of SPS 2003 (that
is to provide browse and search services and little more) and moving to the next
version will be far less painful.

 
Answer #2    Answered By: Victoria Bell     Answered On: Jun 06

Well we are just about to implement 2003. In fact some
Mindsharpies are coming up to do some training in less than 2 weeks.
As a gov't body it will likely be some time before we will be able to
move to 2007. (for example they just finally felt like XP Service Pack
2 was "stable enough" about two months ago). I'll keep that in mind.

 
Answer #3    Answered By: Cassidy Sharpe     Answered On: Jun 06

I understand how governments can sometimes be slow to adopt. Still, SPS
is only intended to provide browse and search facilities. Everything
else should, IMHO, be done in WSS.

 
Answer #4    Answered By: Linda Mason     Answered On: Jun 06

I’m new to sharepoint – when you say “Everything
else should, IMHO, be done in WSS.” you mean create all major team sites in wss  and link them to the portal (I’m guessing)

Whats the difference between that and creating a site  in SPS and why wouldn’t you go that route ?

Like I say, I’m interested and new at this and haven’t really understood the different between a site created in portal and a site created at the wss level.

 
Answer #5    Answered By: Hans Weiss     Answered On: Jun 06

site  (SPWeb) created in SPS from the Sites Area _IS_ a WSS site
(SPWeb). No problem there.

An Area (SPArea - AKA Sub Area for no good reason) created in SPS is a
specialized WSS site (SPWeb) adorned with SPS proprietary attributes or
metadata and some unique Web Parts. The primary purpose of an Area is to
house Listings (another SPS-only thing). Listings are just links  with
some extra metadata (image, expire date, optional HTML, etc.)

Each Area is a unique site definition. Areas use a different security
model than sites (SPWebs). Areas can reflect a different hierarchical
position in the navigation than their physical location. All Areas after
the first 20 are created in Bucket Webs (C1, C2, C3... C19, C0). When
each bucket has 20 Areas a new set of buckets will be created under C1
(C1/C1, C1/C2, C1/C3, etc.). Bucket Webs are gone in MOSS 2007.

The purpose of an SPS Portal is to provide a centralized place where
people in a given enterprise can come and find corporate news
(potentially filtered by audience), can discover where information they
didn't know existed can be found by browsing a taxonomy, can locate
typically top-level sites (SPWebs) in a phone book of sites (called the
Sites Area), and can search for federated, security trimmed, information
that can reside at any URL accessible location within your company
(including databases, file system, and Exchange).

All collaboration should be done in a site (SPWeb). I would create as
few Areas as you can and still accomplish the goals of an SPS Portal
within your enterprise.

I could go on and on and on about this topic. If you ask a specific
question I will try to address that specific "Area" (pun intended).

 
Answer #6    Answered By: Alison West     Answered On: Jun 06

Its just that the courses I’ve been on seem to hint that an sps  site is different from a wss  site and I’ve never seen why – probably because as you say, they’re not actually different !

 
Answer #7    Answered By: Freddy Heath     Answered On: Jun 06

Unfortunately, many people don't realize that a site, sub site, web, sub
web, workspace, area, sub area, etc. are all implemented as SPWeb
objects by WSS v2:
mindsharpblogs.com/.../923.aspx

 
Answer #8    Answered By: Joanna Dixon     Answered On: Jun 06

We are planning on using the SPS Sub Areas as
sort of the public zones that the customers of each dept utilize to ge
t the common items/services those depts provide. The WSS sites are to
used by the actual employees of the depts to collaborate and
"do-the-work." Or that is our 'philosophy' thus far.

 
Didn't find what you were looking for? Find more on bpcf.aspx Or get search suggestion and latest updates.




Tagged: