Support forums » Products » Cute Editor for ASP » Re: We can't reproduce the problems.

How about some support here?!?!?!?!?!?!?

Last post 02-24-2006, 1:14 AM by btran. 19 replies.
Sort Posts: Previous Next

  •  01-11-2006, 11:48 AM 14609

    How about some support here?!?!?!?!?!?!?

    Reply Quote
    I left a message about 5 days ago that there has been no response to.
     
    I am getting very friggin disgruntled at the silence from the support department.
     
    Can  someone help me out? I have been a loyal, happy client since version 3 and now that I need some help, there's none to be had, and this absolutely sucks.
     
    Let's get an answer to the problem please, and get it fixed!!!!!!
     
    The message on the forum is "An Error has occurred in the script on this page - Line: 2 Char: 1 Error: Syntax Error"

  •  01-11-2006, 3:36 PM 14615 in reply to 14609

    Re: How about some support here?!?!?!?!?!?!?

    Reply Quote
    rwhawkes,
     
    Your question (all questions) have not been ignored.

    We are investigating this issue and will get back to you as soon as possible.

     

    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

  •  01-15-2006, 3:24 AM 14732 in reply to 14609

    Re: How about some support here?!?!?!?!?!?!?

    Reply Quote
    I have tried this in several places, and have not been able to recreate the problem. The only thing I can find is the reference to the Gecko_tag_hr.asp and tag_hr.asp in the js files that invoke the asp file. The reference to the files is /Gecko_tag_hr .asp and /tag_hr.asp. I will assume that somehow the location of your editor or one of the settings might be cause the problem. can you send the settings?
     
    RC

  •  01-16-2006, 10:29 PM 14789 in reply to 14732

    Re: How about some support here?!?!?!?!?!?!?

    Reply Quote
    I can recreate -
     
    On your webserver, select the site that cutesoft is running in and then set the custom 404 page to a url. This can be an html or asp page, both will throw errors. If the custom 404 is set to default or file, there won't be errors.

    Unzip the cutesoft for asp 5.0 as usual and syntax errors will pop up on about 1/3 of the buttons. Try hyperlink.

    Interestingly, the error stops if response.end is the first command in the custom 404.asp page.

    Notice that cutesoft will never need to access the 404 if you type the url correctly but the errors still occur.

    Please help!
     

  •  01-24-2006, 3:07 PM 15065 in reply to 14789

    Re: How about some support here?!?!?!?!?!?!?

    Reply Quote
    Any progress on this issue??
     
     

  •  01-24-2006, 3:50 PM 15067 in reply to 14789

    We can't reproduce the problems.

    Reply Quote
    jessiegmc,

    We've tried the steps you mentioned above. For some reasons, we can't reproduce the problems.

     

    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

  •  01-24-2006, 5:20 PM 15072 in reply to 15067

    Re: We can't reproduce the problems.

    Reply Quote
    Maybe this is a server/service pack issue.. What Server version did you test on? I am on 2k.

  •  01-24-2006, 5:22 PM 15073 in reply to 15072

    Re: We can't reproduce the problems.

    Reply Quote
    Window XP and Window 2003.
     
     

    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

  •  01-29-2006, 1:00 AM 15284 in reply to 15073

    Re: We can't reproduce the problems.

    Reply Quote
    Rick the original guy here.
     
    I have spent a couple hours on this problem today and I don't have an answer yet. But here's what I do know.
     
    http://www.bbexpo.com/cute5/default.asp contains all the distribution files and exhibits the problem. Click the link, or add a picture and then double click on it.
     
    Another site I created: http://cute.bbexpo.com/cute5/default.asp contains the exact same files. It does NOT exhibit the problems outlined above.
     
    These sites are using the exact same cute5 files, and a few more things exactly the same, like global.asa, error404 file, setting the 404 error in IIS as outlined in my original message.
     
    These sites are also on the same server, running Windows 2003 SBS with IIS 6.0 etc. fully updated with Windows Update.
     
    Thanks to the community for trying to sort this out. We're not there yet.
     
    ..Rick..

  •  01-29-2006, 1:45 AM 15291 in reply to 15284

    Re: We can't reproduce the problems.

    Reply Quote
    OK Now I can reproduce the problem at will and make it stop at will.
     
    Here's the deal. The above site, http://cute.bbexpo.com/cute5/default.asp works ok if there is no *functional* error  404 page defined in the "Custom Errors" tab. I created a file called error404.htm that contains this code:
     
    <html>
    <head></head>
    <body>
    <h1>Error 404!</h1>
    </body>
    </html>
     
    Not too complicated. As soon as this file is in the website, it makes Cute Editor exhibit those problems. When I take it out, ** clear the cache for IE ** and refresh the page, the error is gone.
     
    I can also duplicate this problem on my test server which is running Window 2000 Advanced Server fully up to date, and IIS 5.0
     
    I hope that everyone can duplicate the problem now.
     
    ..Rick..

  •  02-02-2006, 1:35 AM 15474 in reply to 15291

    Re: We can't reproduce the problems.

    Reply Quote
    Sure is quiet in tech support land.
     
    Got any news on this problem? Have you tried duplicating it with the info I have supplied?

  •  02-02-2006, 2:06 AM 15477 in reply to 15291

    Re: We can't reproduce the problems.

    Reply Quote
    Rick,
     
    We still can't reproduce the problem.
     
    1. We created a static HTML file as our custom errror page.
     
    2. In the IIS, we point the 404 custom error page to the above address.
     
    It still wroks fine here.
     
     
     

    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-03-2006, 12:06 PM 15570 in reply to 15477

    Re: We can't reproduce the problems.

    Reply Quote
    Well what do you propose I do then? This software is a little buggy for prime-time.
     
    Did you look at the URLs I mentioned above and see the exact error message? It's meaningless to me, but it may give you a clue as to where the problem is.
     
    Don't just flush this with the "we cannot recreate it so it's your problem" ... Another guy has the same problem above and I am sure he would like it fixed as well.
     
    I'm happy to work with you on this, and could let you use my server for testing if you think that would help. I think the product is worth it, because in spite of this glitch, it's pretty darn good.

  •  02-03-2006, 12:23 PM 15571 in reply to 15570

    Re: We can't reproduce the problems.

    Reply Quote
    Here is more information on recreating the problem:
     
    IIS custom 404 needs to be set to URL - NOT FILE. This is an option of the custom 404 setting. Choose URL and then type in name of 404 page (\404.asp). Use a simple html page as the 404.asp
     
    After pointing to the correct type of error page, CLEAR IE CACHE and then try to use editor. Like I said, about 1/3 of the buttons throw a syntax error. Try "Insert Hyperlink".
     
    Ditto on what rwhawkes said - I'd be happy to help more or show you my site with errors or whatever. What I know is that I have been trying to get this worked out for a MONTH and I need to find a solution. Maybe going back a version??
     
     

  •  02-04-2006, 2:49 PM 15593 in reply to 15571

    Re: We can't reproduce the problems.

    Reply Quote
    Hey Jessie... Version 4 does not throw this error, but it does not have some of the nice features of version 5. Specifically for my site, in v4, the links are either not there or don't work as well as V5, and for sure the images (should) work better in V5.

  •  02-09-2006, 3:47 PM 15784 in reply to 15593

    Re: We can't reproduce the problems.

    Reply Quote
    I came accross a simple/temporary workaround on this. In IIS, I set the entire site to use my custom 404 URL. In the directory that I have CE and the CE pages, I set it to use the default 404 error. Since I don't need the custom 404 for that directory, it will do. Works fine.. I tried to just do that with the bin and the CuteEditor_Files directories, but syntax errors still there.
     
    Hope this will work for you, Rick!
     
    Jessie

  •  02-10-2006, 10:24 PM 15838 in reply to 15784

    Re: We can't reproduce the problems.

    Reply Quote
    Jessie, you are one smart cookie! That did the trick for me. And so obvious. Nice work!
     
    ..Rick..

  •  02-11-2006, 1:58 PM 15843 in reply to 15838

    Re: We can't reproduce the problems.

    Reply Quote
    Pretty relieved myself. Thanks for bring up the subject in the first place. I am not sure I would have arrived on the 404 connection. Good luck with the rest of this!
     
    Jessie
     

  •  02-24-2006, 12:46 AM 16367 in reply to 15843

    Guess what? We are experiencing this issue as well.

    Reply Quote
    We have a custom 404 setting to an ASPX to redirect the user.  Using fiddler and recording the requested resource in the event log,  we are finding that the Editor sometimes makes requests for a "null" resource, thus triggering the 404 error.
     
    Have you guys been able to reproduce?

  •  02-24-2006, 1:14 AM 16369 in reply to 16367

    Re: Guess what? We are experiencing this issue as well.

    Reply Quote
View as RSS news feed in XML