Craig Somers
Top achievements
Rank 1
Rank 1
Craig Somers
asked on 09 Nov 2009, 10:37 AM
I upgraded RadEditorMoss from the trial to the full version (5.5.1). I then noticed the information on changing the scope of the features so that you didn't have to enable the features for each site in a site collection. I followed the instructions, and this worked fine as well. Unfortunately, I discovered that I no longer had the ability to embed video into blogs and wiki's with ERTE, so I realised I needed to implement the "Web" scope after all, so users could choose whether to have the embed functionality of ERTE, or the features offered by RadEditor. I followed the instructions again, this time substituting "Site" for "Web", but no matter what I do, RadEditor is always the default editor for lists, even if the feature isn't activated on the wiki or blog or list site in question.
I have disabled all instances of the features, retracted, and removed the solution (which reverts the lists back to the MOSS editor), performed numerous IISRESET, and re-installed and deployed the .wsp with stasadm, but still it shows up as the default editor after re-installation, even though it hasn't been activated.
Any idea what's going on and how to solve this issue?
(if there was a way to access the ERTE functionality from a button on the RadEditor toolbar, that would work for me...)
I have disabled all instances of the features, retracted, and removed the solution (which reverts the lists back to the MOSS editor), performed numerous IISRESET, and re-installed and deployed the .wsp with stasadm, but still it shows up as the default editor after re-installation, even though it hasn't been activated.
Any idea what's going on and how to solve this issue?
(if there was a way to access the ERTE functionality from a button on the RadEditor toolbar, that would work for me...)
1 Answer, 1 is accepted
0
Hello Craig,
What you need to do is enable the "Site" scope again and then disable the features. After you disable the features in site scope you can implement back the "web" scope.
Regards,
Stanimir
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
What you need to do is enable the "Site" scope again and then disable the features. After you disable the features in site scope you can implement back the "web" scope.
Regards,
Stanimir
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.