This has just been released this month on msdn.
Great article on developing, deploying and updating Content Types.
Best Practices: Developing Content Types in SharePoint Server 2007 and Windows
SharePoint Services 3.0
http://msdn.microsoft.com/en-us/library/ee330223.aspx
Clayton James
:Unauthorized. You can eliminate this problem by configuring
Kerberos for your SharePoint environment which is also a best practice
recommendation.
http://support.microsoft.com/kb/832769
Clayton James
FlarePoint Pty Ltd |t +61 7 3821 7178 |f + 61 7 3821 7175 |m 0402 463 276 | w
http
Read the *!Important* section on the following MSDN article
http://msdn.microsoft.com/en-us/library/ms479975.aspx
Clayton James
FlarePoint Pty Ltd |t +61 7 3821 7178 |f + 61 7 3821 7175 |m 0402 463 276 | w
http://www.flarepoint.com.au<http://www.flarepoint.com.au/>
From: ozmoss@ozmo
t (or shouldn't) happen if you create the content type through
the UI. When you add a new field to a content type that has been created in the
UI then inheritance should be honoured.
Just thought I would point you to a problem when using Content Types deployed
via Features and declarative XML.
Hi ajay
>From memory you access quick deploy from the page editing toolbar. Ithe page
>editing toolbar may be hidden so you can show it by navgating to the page,
>click site
Actions, click show page editing toolbar.
I remember seeing it greyed out also under Tools.
Clayton James
F
Hi Nathan
I ran into the same problem when I was sending emails to a Group via a SPD
workflow. The fix is described in this article.
http://blogs.msdn.com/spdsupport/archive/2008/06/16/how-to-fix-sharepoint-designer-created-workflow-that-periodically-stops-and-does-not-send-emails.aspx
Clayton
The blob cache will only store what is defined in the web.config and is really
targeting content that doesn't change often. Things like images, css and
javascript works well as these maybe stored in the content database so instead
of the request calling the database every time it requires a .jpg
folder in the 12 hive).
Let me know if this works, as I am not sure how it will handle the provisioning
process of a Feature that is dependent on the underlying site definition that
hasn't yet been created.
Clayton James
From: ozmoss@ozmoss.com [mailto:ozm...@ozmoss.com] On Behalf Of Paul
Excellent...thanks Arron.
I think this is our March.
Some great additions that will make development much easier.
Clayton
From: ozmoss@ozmoss.com [mailto:ozm...@ozmoss.com] On Behalf Of Paul Noone
Sent: Tuesday, 13 January 2009 9:11 AM
To: ozmoss@ozmoss.com
Subject: RE: Community Technology Prev
Hi Aaron
There are many things that need to be in place when creating a Single Sign On
for two ASP.Net 2.0 applications (which includes SharePoint).
- Same Machine Keys
- Need to set the Domain property of the cookie when creating a new
cookie
- Set the Domain proper
Sounds like you are running an trial version of MOSS that has expired.
Go to Central Admin --> Application Management and click the link Check
Services Enabled in this Farm.
You should see an issue here stating you are running an evaluation version and
from memory you can click a link and enter
Hi Paul
I experienced the same thing at a company when they changed their domain
name and therefore couldn't find the user that created the page. I was
unable to enter Page Settings to change page layouts and so forth
Never came across a solution..
CJ
From: ozmoss@ozmoss.com [ma
12 matches
Mail list logo
