Ah, thanks for the fast reply.
I think I'll go for the DMS trunk.

-will

On 22.10.2008, at 08:42, Jan Haderka wrote:

On Wed, 2008-10-22 at 08:21 +0200, Will Scheidegger wrote:
Can anyone confirm this:
When you create a link in the FCK editor which points to a document in
the dms you now endup with something like this:

/dms//path/to/document...

instead of

/dms/path/to/document...

see http://jira.magnolia.info/browse/MGNLDMS-138


Even changing the link afterwards in the HTML code did not solve the
problem because the link seems to be "fixed" each time the FCK editor
is saved.
-> Do you see the same happening with your 3.6.3 installation?
-> Does anyone have a quick fix for it? I mean: QUICK! Just got a call
from a customer who is having a training for his users shortly... :-(

work around suggested in the issue (alternatively you can build snapshot
of DMS from trunk, AFAIK there were no other changes since 1.2.6)

Another option is to revert fix for
http://jira.magnolia.info/browse/MGNLDMS-126 - remove trailing slash
from value
of /config/server/URI2RepositoryMapping/mappings/dms/URIPrefix

HTH,
Jan


Thanks!

-will

----------------------------------------------------------------
for list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
----------------------------------------------------------------
--
Best regards,

Jan Haderka
Magnolia International Ltd.

----------------------------------------------------------------------
[EMAIL PROTECTED] http://www.magnolia- cms.com
Magnolia®  - Simple Open Source Content Management
----------------------------------------------------------------------


----------------------------------------------------------------
for list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
----------------------------------------------------------------


----------------------------------------------------------------
for list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
----------------------------------------------------------------

Reply via email to