There are some references on how to install intellisense for jQuery in VS2008SP1, is it also possible for SharePoint Designer ?
Highly unlikely in my opinion, I don't think SPD is - nor it's meant to be - a very extensible application.
SharePoint Designer was never intended to be used for custom code of any sort, even though you can obviously inject client side code into a page using it.
So I would suspect that Microsoft have deliberately not invested time and effort in developing that side of the product.
I have an initial workflow in Sharepoint Designer that triggers whenever an item is created and also whenever an item has changed in the 'Employee' list . Within second workflow I am updating the 'Employee' list and the workflow above is triggered. Is there any way I can check in the intial workflow if the item has been updated by a user or if it was updated by a workflow. In the case if the item was updated by a workflow I would not want to trgigger it. Many Thanks,
I've followed the 'SPSource_Starter_Guide_WSPBuilder.docx' tutorial and everything was correct. But I've a question : once you've extracted the aspx pages + schema.xml, which tool can be used to edit a AllItems.aspx page in designer mode ? This is not possible using SharePoint Designer or VisualStudio because the masterpage cannot be found once the pages are extracted from the site. Any solution for this ? I've also posted this question to http://spsource.codeplex.com/Thread/EditThreadDetail.aspx?ThreadId=85934 (Sorry for crossposting...)
calling the SharePoint Web Services. It also describes the problem and the solution using SOAPAction. I'm looking for more the 'when' as opposed to the 'how'. ...Is there any rule that says when SOAPAction is REQUIRED in the setRequestHeader? In my jQuery library (SPServices), I've been including the SOAPAction for every Web Service call. It turns out that is what is preventing anonymous access to the Web Services to work. When I remove SOAPAction entirely and I AM logged in, some calls fail with the following error: errorstring: The security
Can I create a unique item in a SharePoint list to prevent duplication of entries, without deploying any app to the server? Also if it can be done through SharePoint Designer, how it can be done?? Thanks.
When I am trying to edit a SharePoint 2010 site (clicking ribbon - Site Actions -> Edit Site in SharePoint Designer), it load SharePoint Designer 2010 application and gives me the following error: "You do not have permission to open this Web site in SharePoint Designer" This error I am getting on my Workstation (Win XP - IE8). I am logging on to my SP2010 site using the Administrator account. Did anyone face this similar problem?
. For instance… If I add a user into the Designer site permission group I can create pages – excellent, just as I would expect. If I create a new site permissions level - let’s call it ‘customer-designer’ - by copying the Designer site permission level and then assign this ‘customer-designer’ level to a new site permission group. I then add my user into the new group and… I cannot create pages, even... in the pages library. Could someone try this for me – to see if it’s a problem on my machine or some weird behavior from Sharepoint?
I've changed the master page on a publish site collection. When I browsed back to the start site to check the new master page the browser just returned a 404 error, telling me that the page could not be found. But when I open the site collection with the SharePoint Designer very thing seems to be ok and in its place. All pages are as expected in the page library. Within the Designer I could even open the pages for editing. So does anyone has an idea why the browser cannot find and open the pages? UPDTAE To clarify my problem I should say, that also switching back to the default master
Is it ok to strip a masterpage for all SharePoint scripts and styles? We have custom CSS and all of our scripts are JQuery. Even CQWP will have custom rendering. The reason we want to do this is so end users will get a lighter version of the page. Since it's a publishing page all end users will be anonymous. We will include all scripts, styles and ribbon for logged in users, so the custom layout have to work for logged in users as well.