Need help with setting Editor Link Browser values!

[Pangdene]

Hi,

seem to be having a problem setting this using an include list.

I have SM installed in public_html/cms with the starting folder for the use being public_html/cms/mycontent

I want to restrict the user to only being able to link to site files in the public_html folder, so I've put public_html in the include list.
I've also restricted linkable files to .html & .php

To test this, I login as the user, edit the snippet, select some text and click the link icon, the Edit/Insert Link dialgoue comes up okay.
On the GeneralProperties tab, the first field is the Link URL - I then click on the 'folder list' icon to the right which I presume brings up a list of linkable files in the folder defined in the Editor Link Browser settings, i.e. public_html.

But, all I get is an empty dialogue box - no files to select.

Is this because the folder defined in Editor Link Browser is above the starting directory for the user in the folder hierarchy - or shouldn't this make any difference?

Help!

Thanks
P

[admin]

Hello,

Yes, I think if you change their starting folder to /public_html/ it will work.  Best way to test is to try the change and then see if it works.

The Starting Folder is used as the "starting point" for the file navigator, so if you specify a path "below" the place you want them to go, then they will have no way to navigate higher.

I hope that makes sense.

[Pangdene]

Hi Henri,

well that didn't work - if I set the starting folder to public_html, then the user can't select a folder from the drop down list.
I think this is because public_html is above the cms folder where SM is installed?

I changed the starting folder to public_html/cms and the user could then select their folder - my content.

Then I did get a list of files to link to, but they were in the public_html/cms folder - so you're correct in that you can't use a folder above the starting folder!

In real life, I'd be installing SM into public_html/cms but the files that the user can link to will be in public_html - the website root.
How can I get around this?

Thanks
P

[admin]

Hmm.. the real-life scenario is pretty much exactly how the software was designed to work, so I'm not too sure if there's a way around it.

Is there a reason why you are wanting to put the files into a folder under the CMS folder?  Maybe what you can do is set their starting folder as /public_html/, but then create a List Group that only includes the specific folders you want them to be able to see. 

With the list groups, you can specify an "include" list of folders.. one set for when they browse for files to edit, another when browsing for images, and another for links.

I think that should work for you. This way, they can only see the specific folders you specify so they will not be able to navigate anywhere else.

[Pangdene]

Hi Henri,

thanks for the suggestion - I will try this out!

Sorry for all the questions right now - but I'm giving SM a good test as I have a bunch of clients ready for it!

Regards
P

[admin]

No problem at all.  Let me know how things go. 

[Pangdene]

will do - thanks!

Just a thought - I'm trying this out using a subdomain - cms.mydomain.co.uk, so the root for the subdomain is public_html/cms - could this be causing a problem?

Regards
P

[admin]

It shouldn't be a problem, although it might mess things up when you add links and images, since the "starting URL" is used for that purpose.   

(ie: Relative links are used by default, and then when previewing or editing, it uses the Starting URL as the "base path" from where to find the relative links.)

I hope that makes sense.