Bart Adriaanse
Top achievements
Rank 1
Rank 1
Bart Adriaanse
asked on 25 Feb 2008, 07:57 PM
I purchased the 4_5_0 RadEditor_MOSS web part today, installed it on two servers in exactly the same way.
One of them works fine but on the other one the default content editors (wiki, discussions etc) are not replaced with RadEdit, i get only raw html when i edit an item. I can add the RadEditor web part to a web parts page myself so it has been deployed and actived on the site i am testing...
The only difference i see in the two setups it that on the machine wich is working OK i had RadEditor Lite deployed (and retracted) before i installed the full version.
I suppose i could try and put the light version on the other machine as well then again install the full product (.wsp file) but this is a production server so i hope there is a better solution to the problem ?
EDIT: thanks to another post in the forum, i find out i need te retract and redeploy, now it works, so one needs to deploy the editor twice to get the full version to work !?
One of them works fine but on the other one the default content editors (wiki, discussions etc) are not replaced with RadEdit, i get only raw html when i edit an item. I can add the RadEditor web part to a web parts page myself so it has been deployed and actived on the site i am testing...
The only difference i see in the two setups it that on the machine wich is working OK i had RadEditor Lite deployed (and retracted) before i installed the full version.
I suppose i could try and put the light version on the other machine as well then again install the full product (.wsp file) but this is a production server so i hope there is a better solution to the problem ?
EDIT: thanks to another post in the forum, i find out i need te retract and redeploy, now it works, so one needs to deploy the editor twice to get the full version to work !?
7 Answers, 1 is accepted
0
Hi,
After you retract/deploy the RadEditor solution, you need to activate (or re-activate) the editor features on at least one site and recycle the SharePoint web application. This will ensure that the RadEditorList.ascx file is copied and loaded properly by MOSS.
Best wishes,
Lini
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
After you retract/deploy the RadEditor solution, you need to activate (or re-activate) the editor features on at least one site and recycle the SharePoint web application. This will ensure that the RadEditorList.ascx file is copied and loaded properly by MOSS.
Best wishes,
Lini
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Bart Adriaanse
Top achievements
Rank 1
Rank 1
answered on 27 Feb 2008, 03:28 PM
Hmm, i noticed this is like a standard reply for posts like these, but this does not seem to be the problem in my case, the RadEditorList.ascx file had been copied succesfully from the start...
As you can see in my edit of the original post, the problem was solved by deploying the feature TWICE, and the RadEditorList.ascx seems to have little to do with it.
Now how about my next problem, i have not found a solution for yet....
As you can see in my edit of the original post, the problem was solved by deploying the feature TWICE, and the RadEditorList.ascx seems to have little to do with it.
Now how about my next problem, i have not found a solution for yet....
0
Hi,
The image manager problem is a known issue with version 4.50 of the RadEditor when your site collection is not at the root of a SharePoint web application. We have fixed it in the current RadEditor for MOSS internal build. The build will be released officially at the end of this week. If you want to receive a fix earlier, please open a formal support ticket and mention this thread as reference.
Greetings,
Lini
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
The image manager problem is a known issue with version 4.50 of the RadEditor when your site collection is not at the root of a SharePoint web application. We have fixed it in the current RadEditor for MOSS internal build. The build will be released officially at the end of this week. If you want to receive a fix earlier, please open a formal support ticket and mention this thread as reference.
Greetings,
Lini
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Bart Adriaanse
Top achievements
Rank 1
Rank 1
answered on 18 Mar 2008, 02:31 PM
I just downloaded the 4_5_1 RadEditor_MOSS update to fix the problem with the image manager discussed in several threads here.
Now the same problem occurs after removing the 4.5.0 RadEditor according to the instructions and then deploying the 4.5.1 update. I have retracted and deployed, removed and reinstalled the update several times now but i cannot get it to work.
So, the RadEditor Web part works fine, but the default editors are not changed, there must be some way to check the default editor configuration manually ?
If i cannot get it to work today i will post a support ticket tomorrow, this is blocking my entire project for the second time now !
Now the same problem occurs after removing the 4.5.0 RadEditor according to the instructions and then deploying the 4.5.1 update. I have retracted and deployed, removed and reinstalled the update several times now but i cannot get it to work.
So, the RadEditor Web part works fine, but the default editors are not changed, there must be some way to check the default editor configuration manually ?
If i cannot get it to work today i will post a support ticket tomorrow, this is blocking my entire project for the second time now !
0
Bart Adriaanse
Top achievements
Rank 1
Rank 1
answered on 18 Mar 2008, 03:41 PM
Following up on my own post:
After retracting/redeploying & totally removing & reinstalling at least five times now the default editors suddenly starts working. (i did a iisreset and cleaned my browser cache each time)
Now the content in radeditor webparts (which is supposed to be upgraded) is broken, and some of the pages cannot be opened at all, not even using Sharepoint designer, not funny !
I guess i need to go back to the 4.5.0 version, remove all the Radeditors from my content pages and then go through the update again, grrrrr.....
After retracting/redeploying & totally removing & reinstalling at least five times now the default editors suddenly starts working. (i did a iisreset and cleaned my browser cache each time)
Now the content in radeditor webparts (which is supposed to be upgraded) is broken, and some of the pages cannot be opened at all, not even using Sharepoint designer, not funny !
I guess i need to go back to the 4.5.0 version, remove all the Radeditors from my content pages and then go through the update again, grrrrr.....
0
Hello,
Have you followed the upgrade instructions on this page http://www.telerik.com/help/radeditormoss/Upgrade%20to%20a%20newer%20version%20of%20RadEditor%20for%20MOSS.html?
The errors suggest that the assemblyBinding elements, mentioned in the above help topic, are not in your Web.config file - they are required when upgrading from a differen version of the editor.
Kind regards,
Lini
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Have you followed the upgrade instructions on this page http://www.telerik.com/help/radeditormoss/Upgrade%20to%20a%20newer%20version%20of%20RadEditor%20for%20MOSS.html?
The errors suggest that the assemblyBinding elements, mentioned in the above help topic, are not in your Web.config file - they are required when upgrading from a differen version of the editor.
Kind regards,
Lini
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Bart Adriaanse
Top achievements
Rank 1
Rank 1
answered on 21 Mar 2008, 08:43 PM
Thanks i guessed i missed these instructions, sorry.
I took the other way out, went back to 4.5.0 then removed the telerik web parts on my sites web part pages (there were only a few, it's a new site) After that just removing 4.5.0 and deploying 4.5.1 went just fine without breaking any pages of the site.
I took the other way out, went back to 4.5.0 then removed the telerik web parts on my sites web part pages (there were only a few, it's a new site) After that just removing 4.5.0 and deploying 4.5.1 went just fine without breaking any pages of the site.