Overview of Bug
When editing a Content Editor Web Part Rich Text on a publishing page that is based off an page layout that contains User fields / people picker, such as the Contact field, after saving the Rich Text changes the page refreshes and all of the user fields are "messed" up.
Steps to reproduce
· Ensure environment is April CU. (We are not sure at this point if it is a bug introduced in SP2 or April CU since we did both upgrades at the same time. April CU is version 12.0.0.6504
o Central Admin –> Operations –> Servers in farm
· To keep it clean, I created a new Web Application to test this on.
· I also created a new site collection based on the collaboration (Publishing tab) template.
· Add a User / Person field control to the home page
o Open up the new site collection with SharePoint Designer 2007
o Open the DefaultLayout.aspx page layout (which is the one used for the home page). Check out if required. ( _catalogs/masterpage/defaultlayout.aspx )
o From the Toolbox, select SharePoint Controls –> Page fields
o Then drag and drop the Contact control to somewhere on the page layout
o Save and Publish / Approve page layout
· Close SharePoint Designer 2007 and open the site collection home page
· Edit the page and fill in a Contact
· Save the page and check it in.
· Edit the page again and add a Content Editor Web Part to one of the zones.
· Click the Open the Tool part link to get the web part editor panel
· Click the Rich Text Editor button and add some simple text.
· Click Ok to save and close the popup for the rich text editor
· And VOLIA!
Next steps…
We'll be opening a ticket with Microsoft on this to see if they have heard of this (and maybe just maybe have a hotfix for it already). We also applied June CU update and that did NOT fix the issue.
I wanted to get this out there to see if anybody else have had a similar issue and if anybody besides me and 4 different environments can reproduce the issue in their environment.
Thanks!
undercoverlaptop
I’m seeing this same issue on our farm. We are at SP2. Have you found any information about how to fix?
thanks,
Rebecca
We appear to have come across a post June CU bug where enabling sorting and filtering on a DVWP to an SQL table.
The sorts/filters fail, the postback occurs but the both the drop down poplulation and selection are recieved by the SQL server as just
SELECT * FROM tableinstead of
SELECT DISTINCT FROM tableand
SELECT FROM table WHERE...Anyone else seen this?
Hi,
did you ever solve this issue? I have the same problem.
Cheers,
Martin
Martin & Rebecca,
Not yet. We currently have it completely in the works for a hotfix. They haven’t given me a date for when it will be fixed yet but they know it is an bug and are going to fix it.
Eli
Any workarounds/solution for this issue?
Hi!
Did you get a hotfix for this problem? We are experiencing the same problem.
Microsoft has a hotfix to fix this issue and they are currently following up with testing. At this point, the fix breaks something with the people picker in Office (which is why it was fixed/broken in SP2). At this time, I don’t believe that it is going to make the Feburary CU so it probably won’t be released until the April CU. I’ll keep you guys posted on what is happening.
Thanks,
Eli
Installed SP2 in our production environment and users are now noticing this issue. This sucks!!
We were also facing this problem – on a team site. We realized that it disappeared after removing our custom javascript file. So if you use some custom code – features, js, css…it may be caused by this. Check this – create a new site (or web app) and test it there. If it works, it is caused by some custom features.
Marek.