I am using Cute Editor for .NET inside an web application that will be used for managing website content.

 

In development, the team has added content using Page Properties>Base location to be our server.  In the HTML view, we then set image paths to be /uploads and other web page links to be something like 'FRP/', or "PCH/' (because the CMS will be managing multiple websites).

 

The question I have is when we deploy this CMS to our clients server, is there an easy way to deploy all the content without manually going in and retyping the Base Location for each as well as going into HTML view and and stripping out the original base location from the image and href paths that is saved originally.  OR is there a better way to handle this all together.  I tried playing with the basehref and removeservertagsfrom url properties on the control and it really screwed up links and even hard coded links that were on the website 'skin'...not even in the content code.  Very bizarre behaviour.

 

Schly

Schly,

 

Can you tell me which version are you using?

 
Please make sure you are using the version 4.5.0.1:

 

Keep me posted.

 

 

Is there any way to tell other than the download file I have...it says CuteEditor_for_NET4.0

4.0.0.4

Please download the version 4.5.0.1 from:

 

  

i downloaded the newest version and added to test project...looking at it though, I don't see how this will solve my problem.  Maybe I didn't clearly explain and I apologize.

 

The CMS where the editor is placed manages content for many websites.  Those websites (that don't have the editor) are separate web applications with their own virtual directory right now but will soon be deployed to external client server.  Right now all images uploaded through the CMS have a directory of http://localhost/CMS/uploads/whatever.  Also when adding links to the content through CMS, if users add a relative link, on save of the code, the html source plugs in the CMS directory and not the other websites directory...so we tried adding the absolute directory to our internal server.  What we are trying to avoid is constant editing of the content.  Because of deployment and support issues back and forth, it would be nice to make sure the relative path is correct no matter where the user is editing or viewing.

 

I will continue playing with new version in test project, but am not feeling tool hopeful.

Please set the editor.UseRelativeLinks, editor.RemoveServerNamesFromUrl and editor.DisableAutoFormatting to true.

editor.UseRelativeLinks = true;
editor.RemoveServerNamesFromUrl = true;
editor.DisableAutoFormatting = true;

 

Demo is here:

 

 

That should resolve your problems.

 

keep me posted.

 

 

i was trying to delete the orig cuteeditor.dll and cuteeditor.lic file in my original project so i could replace with new version...the license file deleted, but the dll didn't.  So I got a 'latest' on the VSS source code to grab the original license that is associated with this project and i get this error

 

"The License for Editor is not valid."

Don't panic; this is an easy fix.

This message usually results from one of the following scenarios:

1. The 30-day free evaluation period has expired.

Solution:

• Purchase CuteEditor and we will send your own license file to unlock your copy of CuteEditor.
• Download the evaluation version from the CuteSoft site again and continue your evaluation.

 

 

2. You have your own license file. But you are using evaluation license file for some reasons.

Solution:

• Please find the license file we sent to you and upload it to your server. If you can't find the license file, email us and specify the email address used for purchasing in your email.

 

 

3. You have placed the order but haven't received the license file for some reason.

Solution:

• Email us and specify the email address used for purchasing in your email.

 

 

4. The actual domain name (or the IP address) has changed.

Solution:

• Email us and specify the email address used for purchasing in your email.

Got this fixed.  Thank you.

 

Since I downloaded a new version, can I use two different versions at the same time as long as they are different ASP.NET web application projects?