ToolTip 2.0 now makes it easier to implement by only needing you to identify the name of the link as you see it on the page.
How do you add a title tag to a webpart page that doesn’t have one? Simply use Javascript (no jQuery necessary) in a Content Editor Web Part (CEWP):
As I continue to put EndUserSharePoint back together after the server fiasco last month, I have tracked down all the resources that were made available to previous EUSP SharePoint Newsletter Subscribers. Below is a list of the thirty, free downloadable resources that are available to subscribers.
I think that they will be popular as a deployment model for applications that use the SharePoint.Client namespace with javascript and Silverlight. I can certainly hide the ribbon with javascript on the client – but I shouldn’t have to. I remain concerned that there is no good answer to #2 with regards to client side code. It would be nice if SharePoint allowed some sort of trusted caller infrastructure that allowed elevation to site owner. This should be possible at least with Silverlight
So, a requirement popped up to allow the business to store “Contact Us” information in SharePoint and use workflows to manually send emails to the people who submitted the contact information. Very easy.. nothing spectacular. They also wanted the ability to send pre-formatted email templates as responses. Also fairly easy to do creating an SPD workflow for each template, right? Well.. what do you do so that you don’t have to open up SPD every time the user wants to add or modify a template? I came up with the following solution. You could take what I did here and build upon it to make it much more elaborate. I’m sure you could format the emails more professionally. You could auto populate more fields like the subject and signature.
I could not get the admin to enable Anonymous Read Access, as believed to be the problem with not being able to access authenticated feeds. I discovered a work around, using SharePoint Designer.
During the last 12 months Twynham has moved beyond using SharePoint as an intranet and extranet to developing Internet facing websites in SharePoint.
During the last 12 months Twynham has moved beyond using SharePoint as an intranet and extranet to developing Internet facing websites in SharePoint.
During the last 12 months Twynham has moved beyond using SharePoint as an intranet and extranet to developing Internet facing websites in SharePoint.
During the last 12 months Twynham has moved beyond using SharePoint as an intranet and extranet to developing Internet facing websites in SharePoint.
