I have replaced the built in content editor web part with RadEditor lite on a couple of SharePoint pages while we look at the feasibility of purchasing the full version.
I would like to hide the Web Part title & border, and make the web part contents editable just by clicking inside (this is how we currently use the content editor web part) - rather than having to click 'edit web part' (which will be hidden).
This is what I currently do with the content editor web part:
1. Add a Web Part Zone to the page
2. Add Content Editor Web Part to zone.
3. Set layoutchange and allowpersonalization to false on the Web Part Zone.
4. Set Chrome style to none on the Content Editor Web Part
Even just setting layoutchange to false (removes the 'add web part' link) on the zone which contains the RadEditor, removes the entire title/web part menu from the RadEditor Web Part when it shouldn't.
I would like to hide the Web Part title & border, and make the web part contents editable just by clicking inside (this is how we currently use the content editor web part) - rather than having to click 'edit web part' (which will be hidden).
This is what I currently do with the content editor web part:
1. Add a Web Part Zone to the page
2. Add Content Editor Web Part to zone.
3. Set layoutchange and allowpersonalization to false on the Web Part Zone.
4. Set Chrome style to none on the Content Editor Web Part
Even just setting layoutchange to false (removes the 'add web part' link) on the zone which contains the RadEditor, removes the entire title/web part menu from the RadEditor Web Part when it shouldn't.
1 Answer, 1 is accepted
0
Hello Adam,
I was not able to reproduce exactly your scenario, since layoutchange attribute was not allowed for WebPartPages:WebPartZone. However I set the LockLayout property to true and I was able to see the functionality that you describe. Unfortunately at this point RadEditor for MOSS does not support this behavior and I can not provide you with an easy way of how to achieve it. I logged your request in our feature requests database and we will research it further and I think that we will be able to implement the behavior of the OOB Content Editor Web Part.
Here you can find the PITS Issue: Public URL
I have replaced the built in content editor web part with RadEditor lite on a couple of SharePoint pages while we look at the feasibility of purchasing the full version. - You should know that the lite version of RadEditor for MOSS is based on the classic ASP.NET version of RadEditor, which we stopped enhancing two years ago. If you want to evaluate the full version of RadEditor for MOSS 5.x, I suggest you download and deploy the trial version of the control. It has full functionality and the only difference with the dev (developer) version is the notifying trial message. You can find the upgrade instructions in the following online help article: Upgrade Instructions from version 4.x to version 5.x
Sincerely yours,
Stanimir
the Telerik team
I was not able to reproduce exactly your scenario, since layoutchange attribute was not allowed for WebPartPages:WebPartZone. However I set the LockLayout property to true and I was able to see the functionality that you describe. Unfortunately at this point RadEditor for MOSS does not support this behavior and I can not provide you with an easy way of how to achieve it. I logged your request in our feature requests database and we will research it further and I think that we will be able to implement the behavior of the OOB Content Editor Web Part.
Here you can find the PITS Issue: Public URL
I have replaced the built in content editor web part with RadEditor lite on a couple of SharePoint pages while we look at the feasibility of purchasing the full version. - You should know that the lite version of RadEditor for MOSS is based on the classic ASP.NET version of RadEditor, which we stopped enhancing two years ago. If you want to evaluate the full version of RadEditor for MOSS 5.x, I suggest you download and deploy the trial version of the control. It has full functionality and the only difference with the dev (developer) version is the notifying trial message. You can find the upgrade instructions in the following online help article: Upgrade Instructions from version 4.x to version 5.x
Sincerely yours,
Stanimir
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items