[MGNLDMS-84] Ability to link to a document within the FCK Editor Created: 17/Jan/07  Updated: 03/Jul/14  Resolved: 08/Nov/07

Status: Closed
Project: Document Management System (closed)
Component/s: None
Affects Version/s: 1.1
Fix Version/s: 1.2-m3

Type: New Feature Priority: Major
Reporter: Magnolia International Assignee: Philipp Bärfuss
Resolution: Fixed Votes: 10
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: HTML File browser.html     HTML File browser.html    
Issue Links:
dependency
depends upon MAGNOLIA-1807 FCKEditor: support links to other wor... Closed
duplicate
duplicates MGNLDMS-1 DMS feature improvement Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

split from MGNLDMS-1



 Comments   
Comment by Barney Boisvert [ 03/Oct/07 ]

Not being able to easily embed links to files in "normal" content is quite an issue. At least for the non-power-user, the solution is to upload a copy of the document within the 'link' dialog, so you no longer have a centralized version of the document. The "right" solution, of course, is to browse to the doc in AdminCentral, edit it, and copy the URL from there into the 'insert link' dialog in the editor, but that's not how the technically non-adept see it.

Extending the 'browse server' dialog would be as simple as adding a radio button for toggling between the website and dms repositories (by updating the inner IFRAME's src attribute), and then if dms, prepending "/dms/" to the generated URL.

Am I missing something? I'm far from experienced with Magnolia having just picked it up within the past week or so, but it seems both a glaring omission and a relatively simple fix.

Comment by Barney Boisvert [ 03/Oct/07 ]

This file can be injected into the

mgnl-resources\fckeditor\custom\editor\filemanager\browser\default\

folder of 'magnolia-editor-fckeditor-3.1-m3.jar ' to deliver the functionality I desired. It's ugly as sin and hasn't been tested in any edge-case scenarios or any other versions of Magnolia, but it solves the core issue at hand.

Comment by Barney Boisvert [ 05/Oct/07 ]

An updated version of browser.html. It can be installed in the same way, but it's smart enough to pick the DMS repository automatically, as well as appending a filename to the path, which seems to be "sometimes" required. It uses a rather crude hack in that it assumes the topmost folder in the DMS hierarchy is the extension to use for the filename. Far from ideal, but whatever. I could reorganize my hierarchy more easily than I could figure out how to extract the data correctly.

Comment by Philipp Bracher [ 05/Oct/07 ]

It is unfortunately not that simple. We store the uuid (so that you can move/rename the nodes). This makes it a bit tricky, but some changes in the core are preparing the solution

Comment by Philipp Bracher [ 31/Oct/07 ]

A more generic solution is targeted with MAGNOLIA-1807

Comment by Philipp Bracher [ 07/Nov/07 ]

works in magnolia 3.5

Comment by Magnolia International [ 08/Nov/07 ]

Fixed with MAGNOLIA-1807.

Generated at Mon Feb 12 00:48:16 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.