Live Support, Chat, Upload Control and Rich Text Editor
Welcome to Support forums Sign in | Join | Help |Client Center
in Search

applying the editor to multiple websites on one server

Last post 02-15-2005, 1:49 PM by dklauk. 17 replies.
Sort Posts: Previous Next
  •  02-07-2005, 4:03 PM 3950

    applying the editor to multiple websites on one server

    I have the server licesne for ASP 3.0 and have multiple client websites on a single webhost. Each website has the same IP address in a shared webspace.

    I have one of the websites working (in a test phase) using the editor.  It accesses/saves content from/to a SQL Server database in an IIS 5 environment.  

    The Cute files are in a folder in the root directory.  I have the asp files to activate the editor to make content changes for just one website.  Now, I want to apply what I have working into the other client websites.

    Do I have to make a CuteMain folder with the other Cute sub-folders within each website folder or can I have just the one CuteMain folder and somehow have the other website folders work from that?

    I really don't want to have to duplicate the Cute-related folders/files for every client website I have.
     
     
  •  02-07-2005, 5:49 PM 3955 in reply to 3950

    Re: applying the editor to multiple websites on one server

     
    In the Site A, SiteB, SiteC, you create a visual directory named CE_fiiles and point the same Cute Editor files folder.

    asp.net Chat http://cutesoft.net/ASP.NET+Chat/default.aspx
    Web Messenger: http://cutesoft.net/Web-Messenger/default.aspx
    asp.net wysiwyg editor: http://cutesoft.net/ASP.NET+WYSIWYG+Editor/default.aspx
    asp wysiwyg html editor: http://cutesoft.net/ASP
    asp.net Image Gallery: http://cutesoft.net/ASP.NET+Image+Gallery/default.aspx
    Live Support: http://cutesoft.net/live-support/default.aspx

  •  02-07-2005, 6:43 PM 3958 in reply to 3955

    Re: applying the editor to multiple websites on one server

     Adam wrote:
     
    In the Site A, SiteB, SiteC, you create a visual directory named CE_fiiles and point the same Cute Editor files folder.
     
    Sorry, but I'm not sure exactly what you mean.  Should I create a regular folder named, CE_files, (with nothing in the folder?)under each site? 

    Also, how do I "point the same Cute Editor files folder?"
  •  02-08-2005, 11:10 AM 3974 in reply to 3958

    Re: applying the editor to multiple websites on one server

     
     
    For example, your cuteeditor files path is c:\inetpub\wwwroot\CuteEditor_files:
     
    1. In site A, you create a virtual directory CE_fiiles and point it to the above location.
     
    in your editor setting, you need to set editor.FilesPath = "/CE_fiiles" 
     
    2. In site B, you create a virtual directory CE_fiiles and point it to the above location.
     
    in your editor setting, you need to set editor.FilesPath = "/CE_fiiles"
      
    3. In site C, you create a virtual directory CE_fiiles and point it to the above location.
     
    in your editor setting, you need to set editor.FilesPath = "/CE_fiiles"

    That will resolve your problem.
     
     
     

    asp.net Chat http://cutesoft.net/ASP.NET+Chat/default.aspx
    Web Messenger: http://cutesoft.net/Web-Messenger/default.aspx
    asp.net wysiwyg editor: http://cutesoft.net/ASP.NET+WYSIWYG+Editor/default.aspx
    asp wysiwyg html editor: http://cutesoft.net/ASP
    asp.net Image Gallery: http://cutesoft.net/ASP.NET+Image+Gallery/default.aspx
    Live Support: http://cutesoft.net/live-support/default.aspx

  •  02-08-2005, 6:04 PM 3994 in reply to 3974

    Re: applying the editor to multiple websites on one server

    1. Ddo you mean, virtual directory and not visual directory?  I don't know what a visual directory is.

     

    2. How do I set up these directories on my shared webhost?  It happens to be LFCHosting.  In this environment, I set up a folder (directory) under my account root directory for each client website.  I am not able to see a "inetpub\wwwroot\..." when I use their File Manager.  I see only my account (client) folders.

    Am I making sense, here, with the webhost setup?

    That's my issue: how do I set up the webhost folders for each client?

     

  •  02-10-2005, 2:27 PM 4040 in reply to 3974

    Re: applying the editor to multiple websites on one server

    My CuteEditor_files folder (with it's sub-folders) on my shared webhost lies under a 'CuteMain' folder.  Should I still point the /CE_files virtual directory to c:\inetpub\wwwroot\CuteEditor_files or should it now be c:\inetpub\wwwroot\CuteMain\CuteEditor_files?  Or, does it make a difference?
     
    Please respond ASAP as I am trying to get a client's site working quickly.
     
    Thanks.
  •  02-10-2005, 2:33 PM 4041 in reply to 4040

    Re: applying the editor to multiple websites on one server

    Should I still point the /CE_files virtual directory to c:\inetpub\wwwroot\CuteEditor_files or should it now be c:\inetpub\wwwroot\CuteMain\CuteEditor_files?  Or, does it make a difference?
     
    No difference. As long as you set up virtual directory in your IIS and point it to the editor files folder.

    asp.net Chat http://cutesoft.net/ASP.NET+Chat/default.aspx
    Web Messenger: http://cutesoft.net/Web-Messenger/default.aspx
    asp.net wysiwyg editor: http://cutesoft.net/ASP.NET+WYSIWYG+Editor/default.aspx
    asp wysiwyg html editor: http://cutesoft.net/ASP
    asp.net Image Gallery: http://cutesoft.net/ASP.NET+Image+Gallery/default.aspx
    Live Support: http://cutesoft.net/live-support/default.aspx

  •  02-10-2005, 5:11 PM 4046 in reply to 4041

    Re: applying the editor to multiple websites on one server

    Thanks for getting back quickly. 

     

    With this setup will each site have its own 'Uploads' area for image files?  Must I define this under /CE_files?

  •  02-10-2005, 6:38 PM 4049 in reply to 4046

    Re: applying the editor to multiple websites on one server

    The setup has nothing to do with the ImageGalleryPath property (default "/uploads").

     

     


    asp.net Chat http://cutesoft.net/ASP.NET+Chat/default.aspx
    Web Messenger: http://cutesoft.net/Web-Messenger/default.aspx
    asp.net wysiwyg editor: http://cutesoft.net/ASP.NET+WYSIWYG+Editor/default.aspx
    asp wysiwyg html editor: http://cutesoft.net/ASP
    asp.net Image Gallery: http://cutesoft.net/ASP.NET+Image+Gallery/default.aspx
    Live Support: http://cutesoft.net/live-support/default.aspx

  •  02-11-2005, 9:03 AM 4053 in reply to 4049

    Re: applying the editor to multiple websites on one server

    Okay, then, will each client site have its own '/uploads' area under the /CE_files virtual directory setup? 
  •  02-11-2005, 12:39 PM 4063 in reply to 4053

    Re: applying the editor to multiple websites on one server

     
    If you want all three websites have the same uploads folder:
     
    For example, your want to store all the image files at c:\inetpub\wwwroot\uploads:
     
    1. In site A, you create a virtual directory uploads and point it to the above location. 
    2. In site B, you create a virtual directory uploads and point it to the above location  
    3. In site C, you create a virtual directory uploads and point it to the above location.
     
    If you leave it default, each web site will have its own uploads folder.
     

    asp.net Chat http://cutesoft.net/ASP.NET+Chat/default.aspx
    Web Messenger: http://cutesoft.net/Web-Messenger/default.aspx
    asp.net wysiwyg editor: http://cutesoft.net/ASP.NET+WYSIWYG+Editor/default.aspx
    asp wysiwyg html editor: http://cutesoft.net/ASP
    asp.net Image Gallery: http://cutesoft.net/ASP.NET+Image+Gallery/default.aspx
    Live Support: http://cutesoft.net/live-support/default.aspx

  •  02-12-2005, 5:27 PM 4075 in reply to 4063

    Re: applying the editor to multiple websites on one server

    The admin at LFCHosting created virtual directories for each site pointing to /CuteSoftEditorMain/CuteEditor_files.


    I put my 'action' asp in one of the site's real folders.  When I put the url in my browser to get to my 'target' asp, I see everything about CuteEditor (the editor.Draw works) except the window frame is missing.  It is defined as editor.StyleSheetPath = "khaki.css"

    I have had this working in the 'non-virtual directory' setup I did, but now the .css does not show under this new scheme.  I have your editor pointing to editor.FilesPath = "/CE_files" in the target asp.

    What am I doing wrong?

     

  •  02-13-2005, 3:39 PM 4081 in reply to 4075

    Re: applying the editor to multiple websites on one server

    (1) Khaki.css got clobberred on the host. 
     
    (2) When I set my desktop shortcut to go to siteA.org/editor-page.asp, it displays nothing (mouse hour-glass active on the browser).  I have editor.FilesPath = "/CE_files"  Looks to me like the virual directory can't be found.

    Help! 
  •  02-14-2005, 10:21 AM 4095 in reply to 4081

    Re: applying the editor to multiple websites on one server

  •  02-15-2005, 8:05 AM 4112 in reply to 4095

    Re: applying the editor to multiple websites on one server

    I can now get to the editor window using the /CE_files virtual directory setup.  As I look back at the recent problems, it appears I was trying to do development when the webserver was being worked on or had problems.  This explains why I wasn't able to see the 'khaki.css' frame as it wound up being an empty file on the webserver.
     
    So, now I have the editor showing in a client website folder.  But, when I go to the 'Images' icon on the menubar, it tells me that I don't have access to that area.  In my asp page, I have ImageGalleryPath = "Uploads" which is the default. 
     
    The Uploads directory is at the same level (in the root) as CuteSoftEditorMain which then contains CuteEditor_Files. Under what conditions will the editor tell the user it doesn't have access to the images area?  Do you think I need to construct the pathing to the Uploads folder so that it knows it is in the root and not in the client website folder?  I thought you said in an earlier response that I should leave the ImageGalleryPath as is.

    BTW, thanks for sticking with me on this multi-website implementation. 
  •  02-15-2005, 9:48 AM 4115 in reply to 4112

    Re: applying the editor to multiple websites on one server

    Directory Structure on my web host:

     

    Here's what I have control over from the web host's File Manager--

     

     

    '/' = my main domain name account root directory with my website folders and files

    'cutesofteditormain/cuteeditor_files' = your module's folders and files under '/'

    'uploads' = the folder where uploaded files are placed per your software from the Insert Image icon.
    'websiteA' = client A's website folders and files including the asp page that points to /CE_files and "Uploads".
    'websiteB' = client B's website folder and files ncluding the asp page that points to /CE_files and "Uploads".
    'websiteC' = client C's website folder and files ncluding the asp page that points to /CE_files and "Uploads".
     
     
    I do not 'see' the virtual directory, CE_files, in my File Manager so I have no control over whether folders or files should be placed within it to accommodate CuteEditor requirements.
     
    Hope this helps.
  •  02-15-2005, 1:18 PM 4117 in reply to 4115

    Re: applying the editor to multiple websites on one server

    The variable that is causing the message that "access to this area is ... forbidden" using Insert Image is: editor.allowupload.  Seems to not allow uploads if the Session (admin access level is <2).

    1. Where is this "admin level" set?
    2. What do I need to do to set it to allow uploads by client websites?

     

     

  •  02-15-2005, 1:49 PM 4118 in reply to 4117

    Re: applying the editor to multiple websites on one server

    In browse_img.asp a check is made for both user access level AND a blank Session(ImageGalleryPath).  I commented-out this code, and indeed, I do not get the "forbidden access..." error message.
     
    So, why would the Session(ImageGalleryPath) = ""?
View as RSS news feed in XML
Powered by ASP.Net
Copyright 2003 - 2017 CuteSoft Components Inc.. All rights reserved.