[UX] Add better description text for file directory setting

We should improve the description text for the Public file system path setting. Here's what we have now:

A local file system path where public files will be stored. This directory must exist and be writable by Backdrop. This directory must be relative to the Backdrop installation directory and be accessible over the web.

Original issue follows.

---

Hello Developers,

I upgraded to Backdrop 1.6.0 yesterday. Everything works but unfortunately the pictures can not be found in the blog post in the text.

My file system is located in the FTP account under /files.

In the backend of the Backdrop CMS I have the directory files. This is also recognized. Unfortunately, the image from /files/files/styles in the frontend does not load.

The Google Chrome Inspector shows me that the image can not be found. But the picture still exists.

You can see this under the URL http://wpzweinull.ch/cms/backdrop/backdropcms-1-6-0-update-online-mit-bugfixes-neuen-features times. Probably something is wrong with me, only what exactly?

Thanks for the help in advance.

[Graham-72]

@AlexL777 I think you may be having the same problem that I have had because of installing Backdrop in a subdirectory. If so, have a look at my solution at #2220 (comment)

[olafgrabienski]

When you inspect the image source of the mentioned site, you see the following as image path:

/files/files/styles/backdropcms-1-6-0-statusbericht-im-backend-updates-werden-angezeigt.jpg.

@AlexL777 I guess the URL is missing the subdirectories 'cms/backdrop'. To check that, add them for instance via Chrome Develeper Tools, resulting in the following path:

/cms/backdrop/files/files/styles/backdropcms-1-6-0-statusbericht-im-backend-updates-werden-angezeigt.jpg

The reason for the issue may depend on how you added the image to your post. Can you give some information to this question?

Hi Guys,

Thank you for your quick help and the solutions as well as hints. Unfortunately, I spent half the day, but unfortunately there was no success. Since I had only 15 articles in the backdrop blog on this domain, I decided to delete the blog.

I have installed backdrop at https://alexanderliebrecht.de and added the images in the ckeditor has worked. It is probably only at the subdirectory, where I had installed.

If I enter in the options of the file system in the backend cms/backdrop/files - then a directory cms/backdrop is created in the directory /files in the FTP account. This is such a mess and the system does not recognize the uploaded images.

I will do nothing more and now have a new backdrop CMS blog in the root directory. This should work.

[Graham-72]

@AlexL777 I am sorry to hear that you were unable to solve the subdirectory problem. If I understand you correctly the problem may be what you have entered as the file system, namely 'cms/backdrop/files'.

It is my experience when working with backdrop installed in a subdirectory that you do not enter the subdirectory at this setting, just leave it as 'files' and Backdrop will automatically use the files folder within the subdirectory.

Anyway, I'm glad to hear that your new installation has avoided this problem.

[jenlampton]

It sounds like this whole problem is coming from the fact that we don't provide adequate help text for this setting. Here's what we have now:

A local file system path where public files will be stored. This directory must exist and be writable by Backdrop. This directory must be relative to the Backdrop installation directory and be accessible over the web.

The first sentence (A local file system path where public files will be stored.) adds nothing. We could move some of that language into the field label, so Public file system path would become Where public files will be stored.

Since we validate the file system path after it's entered, I'm not sure we need the second sentence (This directory must exist and be writable by Backdrop.) either.

That leaves only the final sentence (This directory must be relative to the Backdrop installation directory and be accessible over the web.).

Can we come up with some clearer language around what that means? Or add examples?

Adding milestone candidate tag for the next bug-fix release.