Hi Paul, The errors weren't terribly meanignful and I didn't want to flood the list. But I think the reason for the error(s) is to be expected given the changes I've made thus far were only cosmetic.
* The code below was added to the master page's head section, so in its current form it's not going to be visible in the browser anyway. * The text control doesn't map to anything. So even if it was visible, any inputted text would likely go into the ether or cause further errors. I don't mind mapping to a site column if there is no other way but I still don't really know how to do that. I was hoping that I could use the AdditionalPageHead delegate control and somehow inject the contents of my field into the page's head during creation/authoring. Is this even possible? Wouldn't I still need a placeholder for this content to live within the page? My biggest concern is still securing this. From: [email protected] [mailto:[email protected]] On Behalf Of Paul Turner Sent: Tuesday, 17 March 2009 9:07 AM To: [email protected] Subject: RE: Per page custom HEAD content Can you post the stack trace? Regards Paul Turner Senior Solution Specialist M: 0412 748 168 P: 08 8238 0912 F: 08 8234 5966 A: 66 Henley Beach Road, Mile End SA 5031 E: [email protected]<mailto:[email protected]> W: www.sdm.com.au<https://adlex01/exchweb/bin/redir.asp?URL=http://www.sdmcom.au/> ________________________________ From: [email protected] [[email protected]] On Behalf Of Paul Noone [[email protected]] Sent: Monday, 16 March 2009 1:41 PM To: [email protected] Subject: RE: Per page custom HEAD content Looks like there's a couple of ways this may be achieved without breaking anything or using any custom code. The poor sample below returns a System.Web.HttpException but indicates what I'm trying to do. Any advice on getting this to work as intended? Custom Master <%-- Adding a potentially dangerous place for people to add scripts, CSS or metadata --%> <asp:ContentPlaceHolder id="myPlaceHolderCustomHead" runat="server"> <SharePoint:SPSecurityTrimmedControl PermissionsString="ManageWeb, EnumeratePermissions" runat="server"> <PublishingWebControls:EditModePanel runat="server" id="myEditModePanel"> <SharePointWebControls:textField ID="myCustomHeadBlock" runat="server" /> </PublishingWebControls:EditModePanel> </SharePoint:SPSecurityTrimmedControl> </asp:ContentPlaceHolder> From: [email protected] [mailto:[email protected]] On Behalf Of Paul Noone Sent: Monday, 16 March 2009 12:31 PM To: [email protected] Subject: RE: Per page custom HEAD content Scratch that. Found what I'm after here I believe. http://sharepointkb.wordpress.com/2008/08/01/the-power-of-placeholders/ From: [email protected] [mailto:[email protected]] On Behalf Of Paul Noone Sent: Monday, 16 March 2009 12:30 PM To: [email protected] Subject: RE: Per page custom HEAD content Yes, I did notice that. :) But it's not _really_ what I'm after and I'd like it security trimmed. Ideally I'm after a solution that doesn't use page columns but just presents a text field in Edit view to people with the right permission level. I'm also not sure what might happen to existing content within the PlaceHolderAdditionalPageHead in a Layout Page if I hijack this at the page level. What I really need is a custom placeholder that I can apply to my layout pages for Page content types. Just no real idea how to achieve that. Regards, Paul Online Developer, ICT CEO Sydney From: [email protected] [mailto:[email protected]] On Behalf Of Daniel Brown Sent: Monday, 16 March 2009 11:43 AM To: [email protected] Subject: RE: Per page custom HEAD content Hi Paul, The page down the bottom has a link to a WSP/feature in which you can test and deploy with no code :) Cheers, Daniel From: [email protected] [mailto:[email protected]] On Behalf Of Paul Noone Sent: Monday, 16 March 2009 10:51 AM To: [email protected] Subject: RE: Per page custom HEAD content You can. But I was hoping to find a solution that didn't involve code...or even an existing feature I could just hack up. :) Will take a look at the delegate option. Thanks, Paul From: [email protected] [mailto:[email protected]] On Behalf Of Paul Turner Sent: Monday, 16 March 2009 9:10 AM To: [email protected] Subject: RE: Per page custom HEAD content You can do this with delegates. http://www.mtelligent.com/journal/2008/1/11/using-the-delegate-control-to-add-meta-tags-to-sharepoint-pa.html Regards Paul Turner Senior Solution Specialist M: 0412 748 168 P: 08 8238 0912 F: 08 8234 5966 A: 66 Henley Beach Road, Mile End SA 5031 E: [email protected]<mailto:[email protected]> W: www.sdm.com.au<https://adlex01/exchweb/bin/redir.asp?URL=http://www.sdmcom.au/> ________________________________ From: [email protected] [[email protected]] On Behalf Of Paul Noone [[email protected]] Sent: Friday, 13 March 2009 2:59 PM To: [email protected] Subject: Per page custom HEAD content I'm looking for a method to allow additional scripts, meta tags or CSS to be added to a page's head via the UI. Either through PageSettings.aspx or CreatePage.aspx/EditForm.aspx. I know that scripts and CSS can be added via a CEWP but this is very inelegant and tends to affect validation. Has anyone toyed with adding a custom placeholder to a master page's HEAD section and mapping it to a custom column for the Page content type? Something akin to the PlaceHolderAdditionalPageHead but editable from the UI. Any ideas on how to approach this? Kind regards, Paul ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists ________________________________ Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists -------------------------------------------------------------------------------- Support procedure: http://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists
