When you upload an image, it is uploaded to "CrossEditor Installation Folder/binary" by default. If the WEB server and WAS server are separated, it is uploaded to the 'binary' folder in the WAS server folder.
Even if you reset the image save path with the administrator settings or the ImageSavePath API property, the program searches for the path starting from the default installation folder on the WAS server.
If you want to use another path other than the default path or use a separate image server, or if you want the image server to have a different domain, follow the steps below.
Set up the web service for the server where you want to upload images.
If the path is on the same server, you can use CrossEditor's installation folder to set it up. If the upload server is physically separated, or you cannot access the save path by a URL, you must set up the web service.
Set the path in the source code that inserts CrossEditor
Set the image save path (ImageSavePath) and the actual image upload URL (UploadFileExcutePath) in the page script that inserts CrossEditor.
JSP Version
var CrossEditor = new NamoSE('namoeditor1');
CrossEditor.params.ImageSavePath = "/crosseditor/binary";
CrossEditor.params.UploadFileExecutePath = "http://domain/crosseditor/websource/jsp/ImageUpload.jsp";
CrossEditor.EditorStart();
Set the physical path where the actual images will be saved and the URL path
Remove the commenting in the websource/web language(asp, aspx, php, jsp)/ImagePath file installed in the image server and set the physical path where the actual images are saved and the URL.
If the language is ASP.NET, just remove the underscore from the ImagePath_.aspx filename.
JSP Version
if (imageUPath.equals("/crosseditor/binary")) { //Save path set by ImageSavePath
imagePhysicalPath = "d:\\workspace\\ce\\image"; //Actual physical path
imageUPath = "http://domain/ce/image";
//If the image server domain is different, it must be possible to connect by the actual URL
}
The administrator page, image uploads and a number of plugins use server side technology. As such, if the WEB server and WAS server are separate, it must be possible to access WEB server files from the WAS server.
If the WEB server and WAS server are physically separate, and you cannot set up a mount or shared storage, you must add logic for taking images uploaded on the WAS server and moving them to the WEB server.
CrossEditor does not have any feature for uploading files by FTP.