WYSIWYG - cutting/pasting changes absolute links to relative ones?
This is apparently a new issue that one of our editors recently discovered. In the editor we use the 'link' button on some text and make an internal link to any page. That works fine - creates an absolute link to the page I selected. Highlight the link, ctrl+c to cut, then ctrl+v to paste. All pasted links automatically insert .. in front of the absolute link, which creates a bunch of invalid links. Submitting/publishing doesn't catch the broken links either.
Any ideas?
We're using 6.4.5 - r14079.
Discussions are closed to public comments.
If you need help with Cascade CMS please
start a new discussion.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by jen9580 on 26 Oct, 2010 06:56 PM
Hi there,
I was curious if anybody has had a chance to look at this yet. We're stumped over here.
Support Staff 2 Posted by Tim on 26 Oct, 2010 07:25 PM
Hi Jen,
Can you provide me with some specific examples along with detailed steps of how the link looks each step of the way? I just want to make sure I understand what you are saying because I'm not totally clear at this point. When providing steps, be sure to mention (at each step) which part of the editor you are in (ex: view mode, preview mode, edit mode, edit mode - html source).
Thanks!
3 Posted by jen9580 on 27 Oct, 2010 02:48 PM
Hi Tim,
Upon further investigation we're noticing that this issue only shows up in Firefox so far. We've also checked Chrome and Safari and those are fine.
Here's how we're doing it:
1) edit a page with an internal link
2) highlight/copy the internal link
3) paste the internal link
4) view HTML source
The pasted links have .. appended at the beginning of the path.
Support Staff 4 Posted by Tim on 28 Oct, 2010 07:12 PM
Jen,
Thanks for that info. I was able to reproduce this intermittently as were my developers. It seems to be an issue w/TinyMCE and Firefox and will likely require us to debug TinyMCE. As soon as we have the chance to do so, we'll update this post with more information.
Support Staff 5 Posted by Tim on 05 Nov, 2010 01:36 PM
Hi Jen,
After some more investigating, we were able to find the related bug on the TinyMCE site here. At this point in time, we'll need to wait until this is corrected by TinyMCE. Then, we'll look to upgrade TinyMCE to a more recent version (which hopefully contains the fix) in the application.
Let me know if you have any further questions.
Thanks!
6 Posted by scott.crevier on 15 Nov, 2010 10:19 PM
Tim, we've got this same problem. It seems to have started about 1-2 months ago, though we haven't updated Cascade itself in a while. I'm still running Cascade v6.0.030, and plan an upgrade next month some time.
Support Staff 7 Posted by Tim on 16 Nov, 2010 05:51 PM
Thanks Scott. We'll be keeping an eye on the TinyMCE release notes to see if they correct the problem. Once we feel that a TinyMCE release contains numerous useful fixes, we will work to include a newer version in the application. It requires a lot of testing as we have to verify that none of the TinyMCE code breaks existing functionality in Cascade.
Tim closed this discussion on 16 Nov, 2010 05:51 PM.