While this really doesn't have anything to do with SharePoint, both times I've been asked this question, it was in the context of somebody developing and testing a SharePoint list form.
The answer is that the form fields are yellow due to the Google Toolbar Autofill feature.
Tuesday, July 22, 2008
Monday, July 21, 2008
SharePoint EventID: 8tvn and 8nhi
Are you all of a sudden seeing zillions of messages in the event log with either event id 8tvn or 8nhi? The associated text reads something like:
Unable to retrieve parent node for item at: /SomeSite/SomeSubSite/Pages/Default.aspx of type: Area. This may be expected if changes have been made as the System Account, or if this is a POST request, request type: GET
or
Unable to retrieve parent node for item at: /SomeSite/Pages/SomePage.aspx of type: Page. This may be expected if changes have been made as the System Account, or if this is a POST request, request type: GET
Check and see if you've got more than 50 sites or pages underneath "SomeSite". If so, then you're probably bumping up against the default limit of 50 supported by the MOSS navigation infrastructure and you're getting errors when page/site number 51 and above is accessed. (At least that's what happening on the site I'm working on.)
To make the error go away, you probably need to bump up the value of "DynamicChildLimit" in the relevant NavSiteMapProviderdefinition in web.config. (Set it to zero if you don't want any limit.)
Alternatively, you can define additional NavSiteMapProviders (overriding the default value of "DynamicChildLimit") and reference them in your master page (or whatever is appropriate to your site).
Here are a couple of links to more information on MOSS navigation:
http://blogs.msdn.com/ecm/archive/2007/02/10/moss-navigation-deep-dive-part-1.aspx
http://www.sharepointblogs.com/spsherm/archive/2007/10/22/portalsitemapprovider-properties-includepages-dynamicchildlimit.aspx
Unable to retrieve parent node for item at: /SomeSite/SomeSubSite/Pages/Default.aspx of type: Area. This may be expected if changes have been made as the System Account, or if this is a POST request, request type: GET
or
Unable to retrieve parent node for item at: /SomeSite/Pages/SomePage.aspx of type: Page. This may be expected if changes have been made as the System Account, or if this is a POST request, request type: GET
Check and see if you've got more than 50 sites or pages underneath "SomeSite". If so, then you're probably bumping up against the default limit of 50 supported by the MOSS navigation infrastructure and you're getting errors when page/site number 51 and above is accessed. (At least that's what happening on the site I'm working on.)
To make the error go away, you probably need to bump up the value of "DynamicChildLimit" in the relevant NavSiteMapProviderdefinition in web.config. (Set it to zero if you don't want any limit.)
Alternatively, you can define additional NavSiteMapProviders (overriding the default value of "DynamicChildLimit") and reference them in your master page (or whatever is appropriate to your site).
Here are a couple of links to more information on MOSS navigation:
http://blogs.msdn.com/ecm/archive/2007/02/10/moss-navigation-deep-dive-part-1.aspx
http://www.sharepointblogs.com/spsherm/archive/2007/10/22/portalsitemapprovider-properties-includepages-dynamicchildlimit.aspx
Wednesday, July 2, 2008
CSS Reference Chart for SharePoint 2007 Update
Heather Solomon has updated her very handy SharePoint CSS reference chart.
This reference, along with SharePoint Skinner, was a life saver a few months back when I was working on a SharePoint rebranding project.
This reference, along with SharePoint Skinner, was a life saver a few months back when I was working on a SharePoint rebranding project.
Indexing PDF Documents on SharePoint
Everything you need to know about installing the PDF iFilter on WSS and MOSS.
http://www.moss2007.be/blogs/vandest/archive/2007/09/19/sharepoint-2007-and-pdf-indexing.aspx
One little hint from the "once bitten, twice shy" department: if after installing this iFilter someone claims that a particular PDF document is still NOT being indexed, double-check to make sure that the document in question doesn't just simply contain a image scan with no text.
http://www.moss2007.be/blogs/vandest/archive/2007/09/19/sharepoint-2007-and-pdf-indexing.aspx
One little hint from the "once bitten, twice shy" department: if after installing this iFilter someone claims that a particular PDF document is still NOT being indexed, double-check to make sure that the document in question doesn't just simply contain a image scan with no text.
Tuesday, July 1, 2008
SharePoint Publishing: Enabling Page Settings and Schedule
Scenario: you have a SharePoint publishing site and the Page dropdown on the Page Editing Toolbar has a menuitem that says "Page Settings", not "Page Settings and Schedule". This is bad because you want to be able to schedule when a page will first appear and end.
How do you (re-)enable the "Page Settings and Schedule" choice?
Click the "Settings/Document Library Settings" menuitem for the Pages document library (http://SomeSite/Pages/Forms/AllItems.aspx ).
1) In "versioning settings", ensure that content approval is turned on.
2) In "manage item scheduling", ensure that "enable scheduling of items in this list" is checked.
That should do it.
Update: after writing the above post, I found another post addressing the same issue. You can find it here.
How do you (re-)enable the "Page Settings and Schedule" choice?
Click the "Settings/Document Library Settings" menuitem for the Pages document library (http://SomeSite
1) In "versioning settings", ensure that content approval is turned on.
2) In "manage item scheduling", ensure that "enable scheduling of items in this list" is checked.
That should do it.
Update: after writing the above post, I found another post addressing the same issue. You can find it here.
Subscribe to:
Posts (Atom)