| Author |
Message |
Mike Hacker
Guest
|
Posted:
Wed Jan 12, 2005 2:07 am Post subject:
Templates, ONET.XML and WebPart frames and titles |
|
|
I am working on a template for a SharePoint Area. I have everything working
except for a few minor details.
I have an announcements, contacts and events list created. I then use the
<view> element under the <modules><module><file> section in the onet.xml
file to display these lists.
How can I set the toolbar type to none (I don't want to see the "Add a
new... link")? Do I need to use the <AllUsersWebPart> element instead of
the <view> element? If so, how do I get all of the necessary info for the
<AllUsersWebPart> element for each of the lists? How do I make sure the
webpart is linked to the correct list if I use the <AllUsersWebPart> element?
Thanks,
Mike |
|
| Back to top |
|
 |
Kit Kai
Guest
|
Posted:
Wed Jan 12, 2005 8:44 am Post subject:
Re: Templates, ONET.XML and WebPart frames and titles |
|
|
Are you talking about the link at the bottom of the webpart?
"Mike Hacker" <mphacker@newsgroup.nospam> wrote in message
news:275A07AE-FB71-4E73-B0FC-2B0C333A91CB@microsoft.com...
| Quote: | I am working on a template for a SharePoint Area. I have everything
working
except for a few minor details.
I have an announcements, contacts and events list created. I then use
the
view> element under the <modules><module><file> section in the onet.xml
file to display these lists.
How can I set the toolbar type to none (I don't want to see the "Add a
new... link")? Do I need to use the <AllUsersWebPart> element instead of
the <view> element? If so, how do I get all of the necessary info for
the
AllUsersWebPart> element for each of the lists? How do I make sure the
webpart is linked to the correct list if I use the <AllUsersWebPart
element?
Thanks,
Mike
|
|
|
| Back to top |
|
 |
Mike Hacker
Guest
|
Posted:
Wed Jan 12, 2005 8:55 am Post subject:
Re: Templates, ONET.XML and WebPart frames and titles |
|
|
yes, the add new ... whatever link at the bottom. Also wonder how you can
set any of the other web part properties for the list.
-Mike
"Kit Kai" wrote:
| Quote: | Are you talking about the link at the bottom of the webpart?
"Mike Hacker" <mphacker@newsgroup.nospam> wrote in message
news:275A07AE-FB71-4E73-B0FC-2B0C333A91CB@microsoft.com...
I am working on a template for a SharePoint Area. I have everything
working
except for a few minor details.
I have an announcements, contacts and events list created. I then use
the
view> element under the <modules><module><file> section in the onet.xml
file to display these lists.
How can I set the toolbar type to none (I don't want to see the "Add a
new... link")? Do I need to use the <AllUsersWebPart> element instead of
the <view> element? If so, how do I get all of the necessary info for
the
AllUsersWebPart> element for each of the lists? How do I make sure the
webpart is linked to the correct list if I use the <AllUsersWebPart
element?
Thanks,
Mike
|
|
|
| Back to top |
|
 |
Mike Walsh
Guest
|
Posted:
Wed Jan 12, 2005 11:34 am Post subject:
Re: Templates, ONET.XML and WebPart frames and titles |
|
|
If by "SharePoint Area" you mean the functionality called specifically
"Area", please note that this is purely SharePoint Portal Server 2003
functionality and does not appear in any WSS implementation (standalone; SBS
2003; Project Server 2003)
Please therefore post questions on Area to the SPS newsgroup at
microsoft.public.sharepoint.portalserver
as it is not covered in this newsgroup.
If you were using "Area" in a generic sense, just ignore the above.
Mike Walsh, Helsinki, Finland
WSS FAQ at http://wss.collutions.com
Please post questions to the newsgroup only.
"Mike Hacker" <mphacker@newsgroup.nospam> wrote in message
news:275A07AE-FB71-4E73-B0FC-2B0C333A91CB@microsoft.com...
| Quote: | I am working on a template for a SharePoint Area. I have everything
working
except for a few minor details.
I have an announcements, contacts and events list created. I then use
the
view> element under the <modules><module><file> section in the onet.xml
file to display these lists.
How can I set the toolbar type to none (I don't want to see the "Add a
new... link")? Do I need to use the <AllUsersWebPart> element instead of
the <view> element? If so, how do I get all of the necessary info for
the
AllUsersWebPart> element for each of the lists? How do I make sure the
webpart is linked to the correct list if I use the <AllUsersWebPart
element?
Thanks,
Mike
|
|
|
| Back to top |
|
 |
Kit Kai
Guest
|
Posted:
Wed Jan 12, 2005 1:05 pm Post subject:
Re: Templates, ONET.XML and WebPart frames and titles |
|
|
Well, I know how to do it using the list definition way. I'm quite sure if
you want to use frontpage to do it, it could be done... I think you just
need to switch to xslt view and u can modify... Not sure... I dun like front
page... :)
"Mike Hacker" <mphacker@newsgroup.nospam> wrote in message
news:2E1F32BC-9B4F-4788-87AF-C34D14243F5C@microsoft.com...
| Quote: | yes, the add new ... whatever link at the bottom. Also wonder how you
can
set any of the other web part properties for the list.
-Mike
"Kit Kai" wrote:
Are you talking about the link at the bottom of the webpart?
"Mike Hacker" <mphacker@newsgroup.nospam> wrote in message
news:275A07AE-FB71-4E73-B0FC-2B0C333A91CB@microsoft.com...
I am working on a template for a SharePoint Area. I have everything
working
except for a few minor details.
I have an announcements, contacts and events list created. I then
use
the
view> element under the <modules><module><file> section in the
onet.xml
file to display these lists.
How can I set the toolbar type to none (I don't want to see the "Add a
new... link")? Do I need to use the <AllUsersWebPart> element
instead of
the <view> element? If so, how do I get all of the necessary info
for
the
AllUsersWebPart> element for each of the lists? How do I make sure
the
webpart is linked to the correct list if I use the <AllUsersWebPart
element?
Thanks,
Mike
|
|
|
| Back to top |
|
 |
Mike Hacker
Guest
|
Posted:
Wed Jan 12, 2005 8:15 pm Post subject:
Re: Templates, ONET.XML and WebPart frames and titles |
|
|
Yes, by area I do mean the section in SharePoint called an area. And I do
believe this is the right place to post since creating a template based on
the onet.xml file occurs in both WSS and Portal. And as you stated in one
other post, the Portal newsgroup is frequented by more admins and the wss
group usually attracts the developers, which is who I need assitance from.
"Mike Walsh" wrote:
| Quote: | If by "SharePoint Area" you mean the functionality called specifically
"Area", please note that this is purely SharePoint Portal Server 2003
functionality and does not appear in any WSS implementation (standalone; SBS
2003; Project Server 2003)
Please therefore post questions on Area to the SPS newsgroup at
microsoft.public.sharepoint.portalserver
as it is not covered in this newsgroup.
If you were using "Area" in a generic sense, just ignore the above.
Mike Walsh, Helsinki, Finland
WSS FAQ at http://wss.collutions.com
Please post questions to the newsgroup only.
"Mike Hacker" <mphacker@newsgroup.nospam> wrote in message
news:275A07AE-FB71-4E73-B0FC-2B0C333A91CB@microsoft.com...
I am working on a template for a SharePoint Area. I have everything
working
except for a few minor details.
I have an announcements, contacts and events list created. I then use
the
view> element under the <modules><module><file> section in the onet.xml
file to display these lists.
How can I set the toolbar type to none (I don't want to see the "Add a
new... link")? Do I need to use the <AllUsersWebPart> element instead of
the <view> element? If so, how do I get all of the necessary info for
the
AllUsersWebPart> element for each of the lists? How do I make sure the
webpart is linked to the correct list if I use the <AllUsersWebPart
element?
Thanks,
Mike
|
|
|
| Back to top |
|
 |
Mike Hacker
Guest
|
Posted:
Wed Jan 12, 2005 8:19 pm Post subject:
Re: Templates, ONET.XML and WebPart frames and titles |
|
|
It is not possible to create an area template using FrontPage. You must do
it using the XML configuration files (onet.xml, schema.xml, etc...).
I just want to be able to set the properties for a list view that is shown
on the page. The options are to either use a <view> element or a
<AllUsersWebPart> element. I am guessing that the <view> element will
probably not do what I need, but I do not know how to generate the
defenition needed for the <AllUsersWebPart> element which relates to a list's
webpart.
"Kit Kai" wrote:
| Quote: | Well, I know how to do it using the list definition way. I'm quite sure if
you want to use frontpage to do it, it could be done... I think you just
need to switch to xslt view and u can modify... Not sure... I dun like front
page... :)
"Mike Hacker" <mphacker@newsgroup.nospam> wrote in message
news:2E1F32BC-9B4F-4788-87AF-C34D14243F5C@microsoft.com...
yes, the add new ... whatever link at the bottom. Also wonder how you
can
set any of the other web part properties for the list.
-Mike
"Kit Kai" wrote:
Are you talking about the link at the bottom of the webpart?
"Mike Hacker" <mphacker@newsgroup.nospam> wrote in message
news:275A07AE-FB71-4E73-B0FC-2B0C333A91CB@microsoft.com...
I am working on a template for a SharePoint Area. I have everything
working
except for a few minor details.
I have an announcements, contacts and events list created. I then
use
the
view> element under the <modules><module><file> section in the
onet.xml
file to display these lists.
How can I set the toolbar type to none (I don't want to see the "Add a
new... link")? Do I need to use the <AllUsersWebPart> element
instead of
the <view> element? If so, how do I get all of the necessary info
for
the
AllUsersWebPart> element for each of the lists? How do I make sure
the
webpart is linked to the correct list if I use the <AllUsersWebPart
element?
Thanks,
Mike
|
|
|
| Back to top |
|
 |
Mike Walsh
Guest
|
Posted:
Thu Jan 13, 2005 1:08 am Post subject:
Re: Templates, ONET.XML and WebPart frames and titles |
|
|
Sorry but this newsgroup does not deal with things that are only in
SharePoint Portal Server 2003 (such as My Sites; Areas; the Outlook webpart
etc. ). Nor does it deal with the installation of SPS 2003.
It also doesn't deal with webparts that come only with SBS 2003 (such as one
for Fax) and installations of SBS 2003 and also doesn't deal with the
webparts that come with Project Server 2003 (and installations ...).
What it does deal with is
a) installations of standalone WSS
b) all features of WSS that are *common* to all implementations (standalone;
WSS in SPS 2003; WSS in SBS 2003 and WSS in Project Server 2003
In other words this is the wrong newsgroup for a posting on Areas as these
occur only in one product (SPS 2003) and that product has its own
newsgroups.
Please therefore post Areas (etc. - see partial list above) questions to
microsoft.public.sharepoint.portalserver
or, if you think one of their many sub newsgroups is a better choice, to
that
But not here.
Most people visting this newsgroup don't have Areas and can't answer
questions about areas. Almost all people in the SPS newsgroups (i.e. all
except those using SPS 2001) *do* have Areas.
Mike Walsh, Helsinki, Finland
"Mike Hacker" <mphacker@newsgroup.nospam> wrote in message
news:4F0A808A-BFE8-46C9-9FAB-1057135FDC98@microsoft.com...
| Quote: | Yes, by area I do mean the section in SharePoint called an area. And I
do
believe this is the right place to post since creating a template based on
the onet.xml file occurs in both WSS and Portal. And as you stated in
one
other post, the Portal newsgroup is frequented by more admins and the wss
group usually attracts the developers, which is who I need assitance from.
"Mike Walsh" wrote:
If by "SharePoint Area" you mean the functionality called specifically
"Area", please note that this is purely SharePoint Portal Server 2003
functionality and does not appear in any WSS implementation (standalone;
SBS
2003; Project Server 2003)
Please therefore post questions on Area to the SPS newsgroup at
microsoft.public.sharepoint.portalserver
as it is not covered in this newsgroup.
If you were using "Area" in a generic sense, just ignore the above.
Mike Walsh, Helsinki, Finland
WSS FAQ at http://wss.collutions.com
Please post questions to the newsgroup only.
"Mike Hacker" <mphacker@newsgroup.nospam> wrote in message
news:275A07AE-FB71-4E73-B0FC-2B0C333A91CB@microsoft.com...
I am working on a template for a SharePoint Area. I have everything
working
except for a few minor details.
I have an announcements, contacts and events list created. I then use
the
view> element under the <modules><module><file> section in the
onet.xml
file to display these lists.
How can I set the toolbar type to none (I don't want to see the "Add a
new... link")? Do I need to use the <AllUsersWebPart> element instead
of
the <view> element? If so, how do I get all of the necessary info
for
the
AllUsersWebPart> element for each of the lists? How do I make sure
the
webpart is linked to the correct list if I use the <AllUsersWebPart
element?
Thanks,
Mike
|
|
|
| Back to top |
|
 |
Mike Hacker
Guest
|
Posted:
Thu Jan 13, 2005 1:55 am Post subject:
Re: Templates, ONET.XML and WebPart frames and titles |
|
|
Mike... Is you only purpose out here is to give people a hard time and
absolutly no solutions? I asked a question realted to sharepoint templates,
and not installation issues or other webparts.
As I explained earlier... this does not realte just to SharePoint areas but
ANY template based on the onet.xml file and other related files. Someone
that has experience using CAML and the onet.xml file may have the ability to
answer this question. WSS DOES use onet.xml based templates. More people
are likely to create templates or web parts for WSS sites than for SharePoint
areas, so that is why I posted here. I don't need basic admin information,
how to setup security or deal with alerts, which is what the portal newsgroup
focuses on. I need developer assistance, which seems to be more prevelant
in the WSS newsgroup.
Do you even really understand the internals of Sharepoint / WSS such as
templates, custom code and such? If not, then you have really no idea what
is or isn't appropriate for the newsgroup.
If you do not have a answer to my issue then please don't reply because you
are just wasting space and time.
"Mike Walsh" wrote:
| Quote: | Sorry but this newsgroup does not deal with things that are only in
SharePoint Portal Server 2003 (such as My Sites; Areas; the Outlook webpart
etc. ). Nor does it deal with the installation of SPS 2003.
It also doesn't deal with webparts that come only with SBS 2003 (such as one
for Fax) and installations of SBS 2003 and also doesn't deal with the
webparts that come with Project Server 2003 (and installations ...).
What it does deal with is
a) installations of standalone WSS
b) all features of WSS that are *common* to all implementations (standalone;
WSS in SPS 2003; WSS in SBS 2003 and WSS in Project Server 2003
In other words this is the wrong newsgroup for a posting on Areas as these
occur only in one product (SPS 2003) and that product has its own
newsgroups.
Please therefore post Areas (etc. - see partial list above) questions to
microsoft.public.sharepoint.portalserver
or, if you think one of their many sub newsgroups is a better choice, to
that
But not here.
Most people visting this newsgroup don't have Areas and can't answer
questions about areas. Almost all people in the SPS newsgroups (i.e. all
except those using SPS 2001) *do* have Areas.
Mike Walsh, Helsinki, Finland
"Mike Hacker" <mphacker@newsgroup.nospam> wrote in message
news:4F0A808A-BFE8-46C9-9FAB-1057135FDC98@microsoft.com...
Yes, by area I do mean the section in SharePoint called an area. And I
do
believe this is the right place to post since creating a template based on
the onet.xml file occurs in both WSS and Portal. And as you stated in
one
other post, the Portal newsgroup is frequented by more admins and the wss
group usually attracts the developers, which is who I need assitance from.
"Mike Walsh" wrote:
If by "SharePoint Area" you mean the functionality called specifically
"Area", please note that this is purely SharePoint Portal Server 2003
functionality and does not appear in any WSS implementation (standalone;
SBS
2003; Project Server 2003)
Please therefore post questions on Area to the SPS newsgroup at
microsoft.public.sharepoint.portalserver
as it is not covered in this newsgroup.
If you were using "Area" in a generic sense, just ignore the above.
Mike Walsh, Helsinki, Finland
WSS FAQ at http://wss.collutions.com
Please post questions to the newsgroup only.
"Mike Hacker" <mphacker@newsgroup.nospam> wrote in message
news:275A07AE-FB71-4E73-B0FC-2B0C333A91CB@microsoft.com...
I am working on a template for a SharePoint Area. I have everything
working
except for a few minor details.
I have an announcements, contacts and events list created. I then use
the
view> element under the <modules><module><file> section in the
onet.xml
file to display these lists.
How can I set the toolbar type to none (I don't want to see the "Add a
new... link")? Do I need to use the <AllUsersWebPart> element instead
of
the <view> element? If so, how do I get all of the necessary info
for
the
AllUsersWebPart> element for each of the lists? How do I make sure
the
webpart is linked to the correct list if I use the <AllUsersWebPart
element?
Thanks,
Mike
|
|
|
| Back to top |
|
 |
Mike Walsh
Guest
|
Posted:
Thu Jan 13, 2005 12:01 pm Post subject:
Re: Templates, ONET.XML and WebPart frames and titles |
|
|
I quote again your very first line in your very first message.
"I am working on a template for a SharePoint Area"
I repeat that SharePoint Area problems are not covered here because they are
only in SPS 2003.
If you want to ask about templates that are in parts of WSS that are common
to all products then go ahead here.
But by your first sentence you clearly indicated that you are concerned
about templates in a part of SPS 2003 that is in no other implemention than
the SPS 2003 one.
There are SPS 2003 newsgroups. If people don't ask template questions there,
there won't be any template questions there. The main newsgroup there is per
se not only for Admin questions (both this newsgroup and the main SPS
newsgroup are both called "Administration" by Microsoft on their web page
with links to them).
I post messages like this in order than we concentrate on those common WSS
problems and thus do not have most readers of this newsgroup turning off
because too many threads are about some feature they don't even have.
It seems that every six months or so someone turns up who doesn't understand
this. Mostly they turn to abuse - yours so far is mild in comparison. So
thank you for that.
Mike Walsh, Helsinki, Finland
"Mike Hacker" <mphacker@newsgroup.nospam> wrote in message
news:E66AE365-F4A7-45B6-BAB6-E532DA8B4735@microsoft.com...
| Quote: | Mike... Is you only purpose out here is to give people a hard time and
absolutly no solutions? I asked a question realted to sharepoint
templates,
and not installation issues or other webparts.
As I explained earlier... this does not realte just to SharePoint areas
but
ANY template based on the onet.xml file and other related files. Someone
that has experience using CAML and the onet.xml file may have the ability
to
answer this question. WSS DOES use onet.xml based templates. More
people
are likely to create templates or web parts for WSS sites than for
SharePoint
areas, so that is why I posted here. I don't need basic admin
information,
how to setup security or deal with alerts, which is what the portal
newsgroup
focuses on. I need developer assistance, which seems to be more
prevelant
in the WSS newsgroup.
Do you even really understand the internals of Sharepoint / WSS such as
templates, custom code and such? If not, then you have really no idea
what
is or isn't appropriate for the newsgroup.
If you do not have a answer to my issue then please don't reply because
you
are just wasting space and time.
"Mike Walsh" wrote:
Sorry but this newsgroup does not deal with things that are only in
SharePoint Portal Server 2003 (such as My Sites; Areas; the Outlook
webpart
etc. ). Nor does it deal with the installation of SPS 2003.
It also doesn't deal with webparts that come only with SBS 2003 (such as
one
for Fax) and installations of SBS 2003 and also doesn't deal with the
webparts that come with Project Server 2003 (and installations ...).
What it does deal with is
a) installations of standalone WSS
b) all features of WSS that are *common* to all implementations
(standalone;
WSS in SPS 2003; WSS in SBS 2003 and WSS in Project Server 2003
In other words this is the wrong newsgroup for a posting on Areas as
these
occur only in one product (SPS 2003) and that product has its own
newsgroups.
Please therefore post Areas (etc. - see partial list above) questions to
microsoft.public.sharepoint.portalserver
or, if you think one of their many sub newsgroups is a better choice, to
that
But not here.
Most people visting this newsgroup don't have Areas and can't answer
questions about areas. Almost all people in the SPS newsgroups (i.e. all
except those using SPS 2001) *do* have Areas.
Mike Walsh, Helsinki, Finland
"Mike Hacker" <mphacker@newsgroup.nospam> wrote in message
news:4F0A808A-BFE8-46C9-9FAB-1057135FDC98@microsoft.com...
Yes, by area I do mean the section in SharePoint called an area. And
I
do
believe this is the right place to post since creating a template
based on
the onet.xml file occurs in both WSS and Portal. And as you stated
in
one
other post, the Portal newsgroup is frequented by more admins and the
wss
group usually attracts the developers, which is who I need assitance
from.
"Mike Walsh" wrote:
If by "SharePoint Area" you mean the functionality called
specifically
"Area", please note that this is purely SharePoint Portal Server 2003
functionality and does not appear in any WSS implementation
(standalone;
SBS
2003; Project Server 2003)
Please therefore post questions on Area to the SPS newsgroup at
microsoft.public.sharepoint.portalserver
as it is not covered in this newsgroup.
If you were using "Area" in a generic sense, just ignore the above.
Mike Walsh, Helsinki, Finland
WSS FAQ at http://wss.collutions.com
Please post questions to the newsgroup only.
"Mike Hacker" <mphacker@newsgroup.nospam> wrote in message
news:275A07AE-FB71-4E73-B0FC-2B0C333A91CB@microsoft.com...
I am working on a template for a SharePoint Area. I have
everything
working
except for a few minor details.
I have an announcements, contacts and events list created. I then
use
the
view> element under the <modules><module><file> section in the
onet.xml
file to display these lists.
How can I set the toolbar type to none (I don't want to see the
"Add a
new... link")? Do I need to use the <AllUsersWebPart> element
instead
of
the <view> element? If so, how do I get all of the necessary
info
for
the
AllUsersWebPart> element for each of the lists? How do I make
sure
the
webpart is linked to the correct list if I use the
AllUsersWebPart
element?
Thanks,
Mike
|
|
|
| Back to top |
|
 |
Mike Hacker
Guest
|
Posted:
Thu Jan 13, 2005 3:31 pm Post subject:
RE: Templates, ONET.XML and WebPart frames and titles |
|
|
Sorry, but I don't see any attachment. I still might be able to explain
which one. Each web part shown on the page has an "add a ...." link at the
bottom of the part. This can be turned off by setting the toolbar to none.
If the toolbar setting is set to summary, then the "add a ...." link shows
up.
I am just trying to achieve the same results as setting the toolbar to none.
In the onet.xml file I can use the <view> element to display a web part
view of a list, but I see no options for changing the toolbar to none so that
the "add a ...." link does not show up under the part.
I am guessing I have to use the <AllUsersWebPart> element to accomplish this
since you can specify all of the web part settings. The problem is I do
not know how to get the full assembly and wepart information for a list view
or once I have that info, how to bind it to a specific list.
As mentioned earlier this applies to both WSS site definition or an Area
definition. So it really doesn't matter if this is being attempted in WSS or
SPS.
Thank you for your assistance.
Mike
"Wei-Dong XU [MSFT]" wrote:
| Quote: | Hi Mike,
I attach one screen capture of one SPS area page with contact, doclib,
events. Could you be so kind to tell me which "Add a ...link" item you are
going to hide. I will research that for you then.
Look forward to your reply!
Best Regards,
Wei-Dong XU (WD.XU)
Microsoft Product Support Services
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights |
|
|
| Back to top |
|
 |
Mike Hacker
Guest
|
Posted:
Thu Jan 13, 2005 8:59 pm Post subject:
RE: Templates, ONET.XML and WebPart frames and titles |
|
|
Here is the section in the onet.xml for displaying the webparts / lists on
the page:
<Modules>
<Module Name="Default" Url="" Path="">
<File Url="default.aspx" Type="Ghostable">
<View List="104" BaseViewID="0" WebPartZoneID="MiddleLeftZone"
WebPartOrder="1" />
<View List="101" BaseViewID="0" WebPartZoneID="MiddleLeftZone"
WebPartOrder="2" />
<View List="106" BaseViewID="0" WebPartZoneID="MiddleLeftZone"
WebPartOrder="3"/>
<View List="105" BaseViewID="0" WebPartZoneID="MiddleRightZone"
WebPartOrder="0"/>
<AllUsersWebPart WebPartZoneID="TopZone"
WebPartOrder="0"><![CDATA[<WebPart
xmlns="http://schemas.microsoft.com/WebPart/v2"><Assembly>Microsoft.SharePoint.Portal,
Version=11.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c</Assembly><TypeName>Microsoft.SharePoint.Portal.WebControls.CategoryDetail</TypeName><Title>Area
Detail Part</Title><Description>Area Detail
Part</Description><PartOrder>0</PartOrder><FrameType>None</FrameType><AllowMinimize>true</AllowMinimize><AllowRemove>true</AllowRemove><IsVisible>true</IsVisible></WebPart>]]></AllUsersWebPart>
<AllUsersWebPart WebPartZoneID="MiddleLeftZone"
WebPartOrder="0"><![CDATA[<WebPart
xmlns="http://schemas.microsoft.com/WebPart/v2"><Assembly>Microsoft.SharePoint.Portal,
Version=11.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c</Assembly><TypeName>Microsoft.SharePoint.Portal.WebControls.ListingSummary</TypeName><Title>Grouped
Listings</Title><Description>Shows listings in the
portal.</Description><PartOrder>1</PartOrder><FrameType>None</FrameType><AllowMinimize>true</AllowMinimize><AllowRemove>true</AllowRemove><IsVisible>true</IsVisible><DisplayTemplate
xmlns="urn:schemas-microsoft-com:sharepoint:ListingSummary">TopicsItems</DisplayTemplate><GroupBy
xmlns="urn:schemas-microsoft-com:sharepoint:ListingSummary">Group</GroupBy><SortOrder
xmlns="urn:schemas-microsoft-com:sharepoint:ListingSummary">Order</SortOrder><SortDirection
xmlns="urn:schemas-microsoft-com:sharepoint:ListingSummary">Ascending</SortDirection></WebPart>]]></AllUsersWebPart>
</File>
<File Url="admin.aspx" Type="Ghostable">
<View List="104" BaseViewID="0" WebPartZoneID="MiddleLeftZone"
WebPartOrder="1" />
<View List="101" BaseViewID="0" WebPartZoneID="MiddleLeftZone"
WebPartOrder="2" />
<View List="106" BaseViewID="0" WebPartZoneID="MiddleLeftZone"
WebPartOrder="3"/>
<View List="105" BaseViewID="0" WebPartZoneID="MiddleRightZone"
WebPartOrder="0"/>
<AllUsersWebPart WebPartZoneID="TopZone"
WebPartOrder="0"><![CDATA[<WebPart
xmlns="http://schemas.microsoft.com/WebPart/v2"><Assembly>Microsoft.SharePoint.Portal,
Version=11.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c</Assembly><TypeName>Microsoft.SharePoint.Portal.WebControls.CategoryDetail</TypeName><Title>Area
Detail Part</Title><Description>Area Detail
Part</Description><PartOrder>0</PartOrder><FrameType>None</FrameType><AllowMinimize>true</AllowMinimize><AllowRemove>true</AllowRemove><IsVisible>true</IsVisible></WebPart>]]></AllUsersWebPart>
<AllUsersWebPart WebPartZoneID="MiddleLeftZone"
WebPartOrder="0"><![CDATA[<WebPart
xmlns="http://schemas.microsoft.com/WebPart/v2"><Assembly>Microsoft.SharePoint.Portal,
Version=11.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c</Assembly><TypeName>Microsoft.SharePoint.Portal.WebControls.ListingSummary</TypeName><Title>Grouped
Listings</Title><Description>Shows listings in the
portal.</Description><PartOrder>1</PartOrder><FrameType>None</FrameType><AllowMinimize>true</AllowMinimize><AllowRemove>true</AllowRemove><IsVisible>true</IsVisible><DisplayTemplate
xmlns="urn:schemas-microsoft-com:sharepoint:ListingSummary">TopicsItems</DisplayTemplate><GroupBy
xmlns="urn:schemas-microsoft-com:sharepoint:ListingSummary">Group</GroupBy><SortOrder
xmlns="urn:schemas-microsoft-com:sharepoint:ListingSummary">Order</SortOrder><SortDirection
xmlns="urn:schemas-microsoft-com:sharepoint:ListingSummary">Ascending</SortDirection></WebPart>]]></AllUsersWebPart>
</File>
</Module>
<Module Name="WebPartPopulation" List="113" Url="_catalogs/wp"
Path="lists\wplib\dwp" RootWebOnly="TRUE">
<File Url="MSContentEditor.dwp" Type="GhostableInLibrary" />
<File Url="MSImage.dwp" Type="GhostableInLibrary" />
<File Url="MSPageViewer.dwp" Type="GhostableInLibrary" />
</Module>
</Modules>
The <view> element only works with the first list of that type it finds in
the site / area and also doesn't allow any properties of the web part to be
set. I think I just need to know how to use an <AllUsersWebPart> element
instead of the <view> element for displaying lists.
"Wei-Dong XU [MSFT]" wrote:
| Quote: | Hi Mike,
I attach one screen capture of one SPS area page with contact, doclib,
events. Could you be so kind to tell me which "Add a ...link" item you are
going to hide. I will research that for you then.
Look forward to your reply!
Best Regards,
Wei-Dong XU (WD.XU)
Microsoft Product Support Services
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights |
|
|
| Back to top |
|
 |
Wei-Dong XU [MSFT]
Guest
|
Posted:
Fri Jan 14, 2005 1:07 pm Post subject:
RE: Templates, ONET.XML and WebPart frames and titles |
|
|
Hi Mike,
The AllUsersWebPart element is used at the Module element to add the web
part into the area template. From my research, this element can only accept
the properties of WebPart Class. The ToolBar Type property which you are
going to set to "none" belongs to SPView class. So from AllUsersWebPart,
there is no way for us to set this.
Moreover, for example we use the doclib web part, when Sharepoint renders
the web part at the default setting (no customize from web page or
frontpage), it will obtain the defaultview from SPView.DefaultView and then
send the rendered content to the client browser. The web part will check to
see whether the request page from client is the AllItems.aspx. If not, it
will use the "Summary" toolbar type (). In AllItems aspx page, it will use
the standard toolbar type. As I know, this is by design and we can't change
this. So no matter the <view> element or the <AllUsersWebPart> all can't
help us to change the default behavior. This is to say, your customization
at this is not supported.
Please feel free to let me know if you have any question.
Best Regards,
Wei-Dong XU (WD.XU)
Microsoft Product Support Services
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights. |
|
| Back to top |
|
 |
Kit Kai
Guest
|
Posted:
Fri Jan 14, 2005 2:20 pm Post subject:
Re: Templates, ONET.XML and WebPart frames and titles |
|
|
Hi, sorry for the late reply.
May I know your list name?
Basically, you need to edit the schema.xml for the list link.
Give me more details, like are you dragging and dropping webpart, or are u
using existing webpart view created by default. If you are, I need to know
the ID of that webpart in the onet.xml.
If you are adventurous, you can just do a search for Add New Item (can't
remember the link text) and remove and test which is it. Basically, if you
see <View BaseViewID=X Name=XXX URL=XXX..... that view is not a webpart
view, but a detailed view :)
Hope this helps.
"Mike Hacker" <mphacker@newsgroup.nospam> wrote in message
news:4C6D3538-F647-4697-A701-42F79BC5070F@microsoft.com...
| Quote: | It is not possible to create an area template using FrontPage. You must
do
it using the XML configuration files (onet.xml, schema.xml, etc...).
I just want to be able to set the properties for a list view that is shown
on the page. The options are to either use a <view> element or a
AllUsersWebPart> element. I am guessing that the <view> element will
probably not do what I need, but I do not know how to generate the
defenition needed for the <AllUsersWebPart> element which relates to a
list's
webpart.
"Kit Kai" wrote:
Well, I know how to do it using the list definition way. I'm quite sure
if
you want to use frontpage to do it, it could be done... I think you just
need to switch to xslt view and u can modify... Not sure... I dun like
front
page... :)
"Mike Hacker" <mphacker@newsgroup.nospam> wrote in message
news:2E1F32BC-9B4F-4788-87AF-C34D14243F5C@microsoft.com...
yes, the add new ... whatever link at the bottom. Also wonder how
you
can
set any of the other web part properties for the list.
-Mike
"Kit Kai" wrote:
Are you talking about the link at the bottom of the webpart?
"Mike Hacker" <mphacker@newsgroup.nospam> wrote in message
news:275A07AE-FB71-4E73-B0FC-2B0C333A91CB@microsoft.com...
I am working on a template for a SharePoint Area. I have
everything
working
except for a few minor details.
I have an announcements, contacts and events list created. I
then
use
the
view> element under the <modules><module><file> section in the
onet.xml
file to display these lists.
How can I set the toolbar type to none (I don't want to see the
"Add a
new... link")? Do I need to use the <AllUsersWebPart> element
instead of
the <view> element? If so, how do I get all of the necessary
info
for
the
AllUsersWebPart> element for each of the lists? How do I make
sure
the
webpart is linked to the correct list if I use the
AllUsersWebPart
element?
Thanks,
Mike
|
|
|
| Back to top |
|
 |
Mike Hacker
Guest
|
Posted:
Fri Jan 14, 2005 8:25 pm Post subject:
RE: Templates, ONET.XML and WebPart frames and titles |
|
|
Thank you for researching this. I was afraid that this would be the answer.
Thanks again.
"Wei-Dong XU [MSFT]" wrote:
| Quote: | Hi Mike,
The AllUsersWebPart element is used at the Module element to add the web
part into the area template. From my research, this element can only accept
the properties of WebPart Class. The ToolBar Type property which you are
going to set to "none" belongs to SPView class. So from AllUsersWebPart,
there is no way for us to set this.
Moreover, for example we use the doclib web part, when Sharepoint renders
the web part at the default setting (no customize from web page or
frontpage), it will obtain the defaultview from SPView.DefaultView and then
send the rendered content to the client browser. The web part will check to
see whether the request page from client is the AllItems.aspx. If not, it
will use the "Summary" toolbar type (). In AllItems aspx page, it will use
the standard toolbar type. As I know, this is by design and we can't change
this. So no matter the <view> element or the <AllUsersWebPart> all can't
help us to change the default behavior. This is to say, your customization
at this is not supported.
Please feel free to let me know if you have any question.
Best Regards,
Wei-Dong XU (WD.XU)
Microsoft Product Support Services
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights |
|
|
| Back to top |
|
 |
|
|
|
|