In the calendar, I wanted to hide the start and end times while wrapping the title to allow two lines of text. A quick Google didn't lead to any answers, so off it was to firebug figuring I could get it done with a little CSS. Sure enough it was pretty easy and the solution I'm using is below.
1) Edit the calendar view in advanced mode with SPD.
2) Find the style section near the very bottom of the page and replace it with:
<style type="text/css">
.ms-bodyareaframe {
padding: 0px;
}
.ms-acal-title {white-space:normal;}
.ms-acal-time{display:none;}
.ms-acal-rootdiv div{white-space:normal;}
</style>
Thursday, February 9, 2012
Wednesday, February 8, 2012
Sharepoint 2010: Workflow is not updating
I have been working on a department calendar for time off requests. The list has a couple workflows to send emails to the approvers and the person who submitted the request. I was updating the workflow in SharePoint designer, saving, and publishing. I changed one of the workflows to "Start automatically when an item is changed". I was still not receiving the test emails when the item was changed. I then noticed when looking at the list in SPD the workflow still showed as manual start. I tried everything I could think of, but couldn't get the list to reflect the changes after I saved and published the workflow. I ended up recreating the workflow from scratch and everything worked. It was annoying but at least it was fixed.....then suddenly a second workflow stopped sending the updates to the server. I would change the email, but would still get the old version. I dug around for a little bit and finally found this fix.
It is taken from: http://blogs.msdn.com/b/sharepointdesigner/archive/2007/03/27/tip-clearing-the-spd-workflow-assembly-cache.aspx
If you are building a workflow activity on WSS for SPD you may have to update your activity DLL regularly (say to fix bugs or alter behaviors). Sometimes when you do this, SPD won't recognize your changes to the activity and instead appear to be using the 'old' DLL. Depending on what you've changed in the activity on the server, SPD may not allow you to use this activity at all. This is due to a mismatch between the server's activity and the SPD client's cached activity. To fix this problem its a good idea to clear your SPD activity cache whenever you update your activities DLL on the server.
To clear the SPD activity cache:
1. Close SPD.
2. Open “My Computer”.
3. Go to %System Drive%\Documents and Settings\%user%\Local Settings\Application Data\Microsoft\WebSiteCache (If you are running Vista, that path is different - look for %System Drive%\Users\%user%\AppData\Local\Microsoft\WebSiteCache).
4. Go to a directory that looks similar to the name of the website you were connecting to. (Alternatively, you can just delete all these directories and everything should work when you boot SPD).
5. Delete the assembly with the name similar to the one you are changing.
6. Boot SPD.
7. You can now work with your updated activity.
It is taken from: http://blogs.msdn.com/b/sharepointdesigner/archive/2007/03/27/tip-clearing-the-spd-workflow-assembly-cache.aspx
If you are building a workflow activity on WSS for SPD you may have to update your activity DLL regularly (say to fix bugs or alter behaviors). Sometimes when you do this, SPD won't recognize your changes to the activity and instead appear to be using the 'old' DLL. Depending on what you've changed in the activity on the server, SPD may not allow you to use this activity at all. This is due to a mismatch between the server's activity and the SPD client's cached activity. To fix this problem its a good idea to clear your SPD activity cache whenever you update your activities DLL on the server.
To clear the SPD activity cache:
1. Close SPD.
2. Open “My Computer”.
3. Go to %System Drive%\Documents and Settings\%user%\Local Settings\Application Data\Microsoft\WebSiteCache (If you are running Vista, that path is different - look for %System Drive%\Users\%user%\AppData\Local\Microsoft\WebSiteCache).
4. Go to a directory that looks similar to the name of the website you were connecting to. (Alternatively, you can just delete all these directories and everything should work when you boot SPD).
5. Delete the assembly with the name similar to the one you are changing.
6. Boot SPD.
7. You can now work with your updated activity.
Thursday, February 2, 2012
Sharepoint: : An unsecured or incorrectly secured fault was received from the other party
This was another fun one I ran into today. The site is a reporting center with both Performance Point and Reporting Services reports. The error started after we moved the site from our development environment to our test environment.
The error reported in the SharePoint logs was:
An unexpected error occurred. Error 17265. Exception details: System.ServiceModel.Security.MessageSecurityException: An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail. ---> System.ServiceModel.FaultException: An error occurred when verifying security for the message.
The problem ended up being that after we rebooted the test web server, the clock was 15 minutes ahead. Resetting the clock fixed this error(yes, changing the time fixed the security exception.....). Just another fun day in the world of SharePoint 2010.
The error reported in the SharePoint logs was:
An unexpected error occurred. Error 17265. Exception details: System.ServiceModel.Security.MessageSecurityException: An unsecured or incorrectly secured fault was received from the other party. See the inner FaultException for the fault code and detail. ---> System.ServiceModel.FaultException: An error occurred when verifying security for the message.
The problem ended up being that after we rebooted the test web server, the clock was 15 minutes ahead. Resetting the clock fixed this error(yes, changing the time fixed the security exception.....). Just another fun day in the world of SharePoint 2010.
Subscribe to:
Posts (Atom)