Hi,

 

My WinXP IE browser (and system) hangs when I attempt a 'Replace All' using the latest version of CuteSoft's Find and Replace feature to replace all instances of a particular HTML tag with a different text string with an IE browser. If I use Firefox instead, I get the familiar and much more user friendly:

 

 

The actual sequence that hangs is a replace of all '<li>' instances with '<li><h4>'. Other global replaces that I've tried didn't exhibit this problem and worked fine. Also, I can replace a single instance of '<li>' with '<li><h4>' at a time, but when I click the replace all button, the script hangs.

When I stop the script under Firefox, I find that the editor has replaced the first '<li>' tag with:

 

'<li><h4><h4><h4><h4><h4><h4><h4><h4><h4><h4><h4><h4>...<h4>' [ad infinitum..]

 

I've been unable to reproduce this problem on the CuteSoft demo page, but can reproduce it every time with my own latest build, but I still tend to think this is a CuteSoft bug rather than an integration problem. Still, it's puzzling that it works just fine under the latest CuteSoft demo. Anyone else seen this issue?

 

Adam, any ideas?

 

Thanks,

Kazzlo

Kazzlo,

 

Are you able to reproduce this issue in the following example?

 

 

If not, please download the control again:

 

 

Keep me posted

 

Hi Adam,

 

We re-downloaded the latest Cutesoft code and rebuilt. Strangely, I see a different behavior now. Now, I get the following when I set "Find what" to <li> and "Replace with" to <li><h4> under the editor when in HTML mode using Firefox 2.0:

 

 

 

 

And when I try a Replace rather than a Replace All, it replaces <li> with <li><h4> as I would expect, but it then changes the same string to <li><h4><h4> if I click Replace again without clicking Find Next. And then <li><h4><h4><h4>, etc..

 

This is a better behavior than the endless loop script hang situation. It also matches how your demo page now works.

 

I'm dependent upon a Ukrainian development team for build updates, etc. (and they're asleep now) so don't know the answer to the following question.. Did you change the code on the download page even though it still has a Date Added date of 08-07-2008?

 

I ask because when I tried a find/replace on your demo page two days ago (like that described above), it worked fine and executed all of the replaces only once. However, now when I try the replace all, it returns the same pop-up that I see locally, i.e. "Please use replace function."

 

Thanks,

Bill

Bill,

 

We did changed the control after 08-07-2008.

 

If our demo works for you, please download the control again.

When upgrading, please update the dll and client files as well.

 

Keep me posted

Hi Adam,

 

I'm confused.

 

When I tried your demo on the first day I reported this bug, the demo code was able to do a replace all of '<li>' with '<li><h4>' without a problem. However, when I tried it yesterday, the demo gave me the "Please use replace function" pop-up. And today when I try the same replace all sequence, it works like it did several days ago, i.e. without error (no pop-up).

 

Did you update the code yet again yesterday or today?

 

As an aside, I would strongly encourage you to update the date on the download page any time you change any part of the code. It's very confusing and misleading to those of us trying to figure out when/if to update. There for a while, you were publishing a change list with each code update, and that would be tremendously helpful as well.

 

Regards,

Bill

Bill,

 

We have not updated this dialog in a very long time.

 

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

Okay, thanks Adam.

 

One thing I just discovered while doing some testing against your demo at http://cutesoft.net/example/general.aspx..

 

A replace all of HTML tags such as find: <td> and replace with: <td><h4> works fine with IE (I'm using IE6), but returns the pop-up message described earlier under Firefox (I'm using 2.0).

 

Hope this helps..

 

Regards,

Bill

Hi Adam,

 

Any resolution on this issue?

Will there be a fix in the upcoming release?

 

Thanks,

Bill