ok, the insert-anchor-dialog is nice, but the following behaviour is a problem;

cuteeditor used on admin.aspx to change content;
a) insert anchor #top
b) save
c) change sth, switch between normal/html view; -> explorer changes link to http://myweb/admin.aspx#top
d) save, which then cuts the link to admin.aspx#top; this is nice, but nevertheless wrong when writing the content to another page, the link should point to #top, not to admin.aspx#top ..

this bug/problem was already reported on 2005-06-16 in this forum, but his post has not been answered yet;
maybe there's a switch to tell cuteeditor, not only to strip the folderpath, but also the documentname of the page he is used on (here admin.aspx) ??? or could it be built?

thx

Can you produce the same problem in the following link?

 

 

Keep me posted.

 

 

sorry, wrong dll; mine was 4.0.0.7 or sth. like that, didn't notice upgrade to 4.5;

problem seems to have disappeared;

 

thank you!

sorry, but a variation of the problem seems to be there again;

1) open the example Relative-or-Absolute-URLs.aspx
2) now insert a link to some file, downloads/test.jpg for example;

3) post -> the link points to /downloads/test.jpg

4) switch to htmlview, switch back to normal view;

5) post again -> the link points to http://cutesoft.net/example/downloads/test.jpg

this is a problem for me, the reasons r 2:

a) my application architecture

 my folderstructure:
 /app
    show.aspx (writes the content to the user)  
    /images
    /downloads 
    /maintenance
       /cutesoft
       /downloads (is a virtual entry pointing to ../downloads)
       /images (is a virtual entry pointing to ../images)
u see, the editor is placed in another folder than the aspx which puts the content to the website; to overcome the problems, all linked data (images, downloads) is placed in two folders which are referenced by virtual entries in the maintenance app, so /downloads/test.jpg is valid for the maintenance app and for the website itself;

if sb saves his stuff in normalview after switching the links point into the maintenace folder, which may be valid as links but leads to problem as normal visitors have no right to access data in the maintenance folder;

b) when using anchors in the page the output of cute editor is simply wrong;
for example, my link points to #top; save it and open um switch to html, back and save; and now the link points to http://cms/maintenance/#top which is simply wrong;

and .. no, the workaround to set the link to show.aspx#top does not work, because show.aspx gets many more parameters (displayed menus and so on) and i don't think my user would be very happy if they had to know my app-architecture just to edit their content :-))


p.s.:
if u switch back to html and save, the link is corrected in the samples downloaded with cuteeditor; but this doesn't work online

That's the IE behaviour. Internet Explorer converts all URLs in hyperlinks (anchor tags) and images (img tags) to absolute URLs with the hostname name.

Cute Editor found a solution to this issue.

1. If you type <img height=100 src="/uploads/Cindy_Crawford.jpg" width=124 border=0>, after you click the submit button, the content generated from the editor is "<img height=100 src="/uploads/Cindy_Crawford.jpg" "

2. If you type <img height=100 src="../uploads/Cindy_Crawford.jpg" width=124 border=0>, after you click the submit button, the content generated from the editor is "<img height=100 src="../uploads/Cindy_Crawford.jpg" "

3. If you type <IMG height=100 src="/uploads/Cindy_Crawford.jpg" width=124 border=0> after you click the submit button, the content generated from the editor is <IMG height=100 src="/uploads/Cindy_Crawford.jpg" width=124 border=0>"

I understand you may still have problems.

 

Can you put your site online and send the URL to us?

 

 

Hi guys, great product and all the rest.  The best HTML editor for asp.net that I've seen. 

I have to say that I've come across the same issue with anchor links which go to the same page, as previous users. 

I'm slightly different from other users though, in that I'm not using the out-of-the-box link button for creating anchor links - I've created my own button which allows for a custom dialog which creates links from other applications into the html. 

Basically this button pops up a custom dialog which people select a value from i.e. an existing anchor link on the same page.  Then, I have a function which gets this value and outputs it into the code.  This seems to be where my problem lies:

my code looks like this:

where strLink is a value thats passed in from the custom dialog from before.  Now if I check out the value of strLink before running this line, it gives a value of:

<a href="#nameofanchor">texthere</a>

but when I run the ExecCommand command, it adds the editor page to before the hyperlink e.g:

Any ideas?  I'd be really appreciative of any help I could get with why ExecCommand screws up my anchor tag.  Or perhaps even pointers on documentation for how the ExecCommand/PasteHTML thing works..

 

Thanks for the nice comments about CuteEditor.

 

Please try the PasteHTML(html) JavaScript API:

 

 

Keep me posted

 

 

 

 

hi Adam, thanks for getting back to me so quickly.

I tried the PasteHTML function as you showed in your previous post, but it gave me the same results that I had when using the ExecCommand function. 

Do you have any other things that I could try? 

Is it a bug in IE, that it always outputs the current editor page in the beginning before the hash?

Thanks for spending time on this.

 

theo,

 

>> it a bug in IE, that it always outputs the current editor page in the beginning before the hash?

There is  an bug in IE. But Cute Editor already took care of it.

 

 

 

When I use Cute Editor.NET 5.3 inside of a third-party TAB control (Tabular control), the anchor bug is still there. The TAB control is Javascript based. I want to contact the vendor of Tabular control to report the problem. But I'm afraid that they might say it is Cute Editor's problem. Could you tell me what case (any html tags or style) can prevent Cute Editor from fixing the anchor bug?

 

Thanks.

 

 

 

ytang,

Adam,

 

I can reproduce the problem in your link finally. It happens when I use Absolute Urls setting (Editor1.UseRelativeLinks = false and Editor1.RemoveServerNamesFromUrl = false) and the page has 2 or more querystring items.

The following are the steps to reproduce the problems:

 

1. Click the link which has 2 querystring items:

 

2. Click the radio button "Use Absolute Urls".

 

3. Switch to "HTML" view, and insert an anchor link: <a href="#top">top</a>

 

4. Switch to "Normal" view then switch back to "HTML" view, you will find the anchor link has been changed as following:

<a href="http://cutesoft.net/example/Relative-or-Absolute-URLs.aspx?param1=1&amp;param2=2#top">top</a>

 

 

The anchor link works fine when the page doesn't have any querystring item or only has one. My page needs many querystring items, and I must use Absolute Urls setting. Any idea to solve the problem?

 

 

 

 

 

My users are pulling there hair out with Anchors. The div's, where the cursor gets placed and reformatting to xhtml on submission seem to each have something to do with this...Will provide test scenario as I get it...

Latest version

 

OK It's Firefox that has the issues with anchors. IE works fine. With Firefox my content get's blown away.

 

Take this content I submitted in the editor with IE 7 browser and cut out of html view::

 

 

 

 

 

http://cutesoft.net/example/general.aspx

 

Download:

 

 

Sorry - still broken
I just used fresh update of mac osx and firefox 2 and used your sample editor

 

create ten lines of text

enter cursor at line 5
create an anchor using the anchor tool

name it an OK
select HTML view
all content below anchor is deleted

 

when I type in an anchor as in <a name="test"/> it works and I can switch views

 

This is my biggest client grievance at the moment, well for a long time now.

Can you reproduce?

Anchors definitely do not work in version 6, latest build, and I have thus far received no response.

Version 6 does seem to help with content getting blown away using mac firefox and safari BUT the anchor name and id attributes get messed up. Reprodcued in your demo site where I make 6 anchors with unique names and then submit and they all get changed to the same name

In my app I tried creating anchors in PC and Mac Firefox 2 running version 6 and here is what I found

In this case I made anchors to 6 spots in my content and on submission the anchors <a name="hosting" id="hosting"></a>,<a name="system" id="system"></a>, [and a few more] and <a name="support" id="support"></a>  ALL got written as the last anchor - such that when I opened back up the content in the editor I saw 6 anchors like this <a name="support" id="support"></a>

 

Please try this example:

 

 

It works fine here.