TYPO3 Core

I see no easy way to implement this. We could add readonly db mounts, but that would require too many changes in different places.

I see no use for this (compared to required effort). As discussed in the list, you don't even need read-only db mounts, but with proper permissions, you can just add a global db mount and tell the users to use that for linking, that's your link mount. We've done that and it's been secretary-safe ;)

Of course you can do that, but it is just not really nice for the standartd noop user, that will click on the link button, and everything appears twice. I know many people that are not able to handle such a needless (to their point of view) dublication...

Hi,
I am not sure if it would be more logical if everything didn't appear twice... Imagine the following: A user has a certain DB mount and normally only sees his part of the pagetree. He then wants to insert a link to a page he wrote and sees the whole pagetree, maybe not even knowing where his subtree is located. I think in this example, he shouldn't be allowed to see more than his part of the pagetree, as it could confuse the user, too.
Maybe "Link DB Mounts" would be a solution... What do you think? DB mounts only taken into account for adding links.
Greets, Sebastian

Another cool way to handle this would be the "link" popup to not show us the "page tree" but instead the frontend (in a subframe, for example). The user then navigates through the well known site, and as soon as he finds the one to which he wants to link to he clicks on "link to this page" and the link is created. With the adminPanel and the "preview" she could even link to pages requiring login, etc.

This could even handle "external" links: just surf to the link and say "link to this".

What do you think? :)

Hi Ernesto,
I think this would be very nice, indeed. Maybe not as a default, but as a TypoScript option.
Currently I have no time to implement this, if somebody is interested, feel invited :-)
Greets, Sebastian

Ciao Ernesto!

What do you think? :)

I think this sounds like overkill! ;-) For sure this is too much work for the Gremlins project, but maybe someone else will pick it up later...?

Hi,

as I reported that, I will try to program an extension for this, because this sound like a good solution for it. I do not have enough time in march, but hey there's april after march... I'll see what I can do...

This is possible now with user TS config: options.pageTree.altElementBrowserMountPoints = 34,123

Thanks for Susanne Moog for reporting.

See rev. 2630 by Kasper, since 4.2.0-alpha2. Later (rev. 3981 by Stan, since 4.2.2) also added to RTE browse-Links.