Bug? Creating Internal Links

Hi there,

I seem to be having problems creating internal links in Revo RC1.

After establishing from a previous thread that I was meant to be dragging and dropping from the site tree I quickly found that this didn’t work with the WYSIWYGs in Beta5 for me, so waited until RC1 to evaluate Revo again.

I’m still having the same problem - with both TinyMCE and CKeditor. If i drop on to any other field the document ID is inserted correctly, but I can’t get it to work with the RTEs.

Any ideas? Is this currently the prefered method for creating internal links from the RTEs? And is it likely to stay this way going forward?

Cheers,

DM

It appears that the drag and drop behavior is working fine in Safari, but acting up in Fx and Chrome; for both Tiny and CKEditor. We’re looking into it; thanks for pointing this out.

In the meantime, you can always just type the internal link out as normal:

[[~123]] for Resource ID 123.

The drag/drop is more of a convienence feature.

Yeah, this seems to be a bug with the way that Firefox/Chrome handle mouseover events in iframes - and I cant actually override it, so it’s just not going to work (unless someone else can solve it).

You’ll just have to manually type in links for now, the old Evo way.

Thanks for the feedback guys.

Personally I don’t think it’s too much of a loss, whilst its ’cool’ its quite a quirky way of inserting an internal link.

Whilst I realise that the goal is to be RTE independant might I suggest that an extra section with the site tree listed is added to the "Browse Server" window in CKEditor and the TinyMCE equivialant that allows you to select a page and return the dynamic URL marker. I’d imagine most of the functionality for this is already built as the tree "widget" is a major part of the manager.

Whilst I’m more than happy to type in references manually I’m sure you’ll agree that this is a real usability weakness for users who aren’t quite so tech savvy. Thoughts?

DM

Quote from: DangerMouse1981 at Mar 25, 2010, 04:49 PM

Thanks for the feedback guys.
Personally I don’t think it’s too much of a loss, whilst its ’cool’ its quite a quirky way of inserting an internal link.

Yeah, the Resources aren’t as neat as when you try and drag and Element (say, like Quip) in. Try that without the RTE on - it shows a popup dialog of properties you can fill in.

Whilst I realise that the goal is to be RTE independant might I suggest that an extra section with the site tree listed is added to the "Browse Server" window in CKEditor and the TinyMCE equivialant that allows you to select a page and return the dynamic URL marker. I’d imagine most of the functionality for this is already built as the tree "widget" is a major part of the manager.
Whilst I’m more than happy to type in references manually I’m sure you’ll agree that this is a real usability weakness for users who aren’t quite so tech savvy. Thoughts?

It’s definitely a desired feature for the RTEs. Just have to either find time to dev it, or hope someone else does.

Wish I could help out - actually tried to figure it out during beta5 assuming that most of the code would be there and I’d just have to hook to the "browse" button method for the RTEs but I couldn’t make head nor tail of the code.

Do you guys keep code documentation? From doc comments or something?

DM

Quote from: DangerMouse1981 at Mar 25, 2010, 08:03 PM

Wish I could help out - actually tried to figure it out during beta5 assuming that most of the code would be there and I’d just have to hook to the "browse" button method for the RTEs but I couldn’t make head nor tail of the code.

Do you guys keep code documentation? From doc comments or something?

On the PHP, yes. However, the JS - especially the RTE JS - no. We’ll probably eventually add JS doc code to it, since now by default the JS is compressed for releases.