Thursday, August 23, 2007 12:20 AM
I hope this isn't a silly question, but I haven't been able to find the answer anywhere. When we create a new page in SharePoint and add content to the page, how do we spell check the content? According to the Help, the spell check button is not included on the inline editing toolbar (the one that shows up when you click Edit Content on a page). How do we switch to the Rich Text Editor that includes the spell check button?
For example, I have a publishing site and I select Create Page and select an out-of-the-box Article Page for the page layout. When I click on Edit Content, I do not see any way to use the Rich Text Editor, just the inline toolbar mentioned above. If I create a new page and use a page layout with web parts, I can add a Content Editor Web Part to a web part zone. When I edit that page, I can use the Rich Text Editor in the Content Editor Web Part. Seems convoluted.Can I spell check an article or welcome page without adding a Content Editor web part?Thanks -- Kristin
Wednesday, August 29, 2007 7:24 AM
You can use spelling option from the page editing toobar in tool options when you edit the page.
Thursday, August 30, 2007 12:00 AM
Thanks Mayur! That is what I was looking for. However, some of my users cannot spell check on their subsites. They get the message: "Spelling did not complete properly. If this problem persists, notify your system administrator." They have either owner or contributor access to their site. Those of us with full control at the top level site can spell check. Has anyone else had this issue? Is there a certain level of access required to access the dictionary for spell check?
Thanks -- Kristin
Thursday, August 30, 2007 2:11 PM
Try to repair your office
Monday, September 24, 2007 4:47 PM
I believe that you require at least "Visitor" permissions on the site to be able to do a spell check.
Tuesday, September 25, 2007 11:27 AM
That may well be a security issue, but I would have expected a more explicity "denied" error myself.
Often, these kinds of vague errors are logged with more diagnostic information in the log here:
If you do determine and fix the root cause, please let us all know!