Printable View
I can restrict pages to logged in users. However, any files or images on those pages can still be accessed directlyby non-logged in users.
The "Public" option in the file manager doesn't seem to have any affect (what is it for?).
I have seen some complex solutions using mod_rewrite that don't seem to work anymore for 4.4. I would prefer a solution simple enough to survive upgrades.
Any suggestions?
Thanks,
Allen
Only those files in folders that are set to "public" can be reached from the outside.Quote:
Originally Posted by alien878
For other files you can use the Download(s) content element, which you can restrict to certain member groups (either directly in the element or indirectly via the page).
Actually, files in folders not marked public are still accessible with a direct link. Ex:Quote:
Originally Posted by Spooky
https://www.webpage.de/files/protected/file.gif
Where the files/protected directory does not have "Public" checked in the file manager. I think this only applies to the file manager.
I was looking for some way to make our group's history pages (with pictures) private/members only to comply with new EU/German privacy laws. I think I will just have to take them down now. Kind of hard to take down 20 years of documented history though...
No, that should not be possible. Only folders that are marked as "Public" are accessible in the front end - because only those get a symlink to the actual files directory.Quote:
Originally Posted by alien878
Okay.... Maybe I've set something up incorrectly. Admittedly, this site has been using contao for several years and I am not 100% sure all of the upgrades set up the files directory correctly.
In the web directory, there is a symlink to ../files.
This directory is the "root" of the backend's "File Manager".
In the File Manager, I have created a directory "protected" with Public unchecked. This appears in the files directory.
I can still access files in this "non-public" file directory with a direct link. Ex.
https://www.webpage.de/files/protected/file.gif
According to https://docs.contao.org/books/cookbo...tructure.html:
"files/ contains public files such as images, CSS, JavaScript, etc. It is available from the web/ folder through a symbolic link.", so it seems correct.
May be Contao is unable to delete the symlink (may be a permission issue?). Delete the symlink manually.
I created the files link manually based on the documentation. The contao:install-web-dir deletes it and breaks every image on the webpage.
So you are saying there shouldn't be a link to "files" in the web dir? I need one, but maybe that is because something went wrong when I upgraded from contao 3 to 4.
You should not do that. Where did you read that?Quote:
Originally Posted by alien878
What do you mean by that?Quote:
Originally Posted by alien878
Thanks spooky for answering my questions so quickly.
https://docs.contao.org/books/cookbo...structure.htmlQuote:
Originally Posted by Spooky
Scroll down to /files.
Whenever I run composer to add an extension, the files symlink is removed. I assumed it was at the contao:install-web-dir which is run even when adding an extension. Also, in the backend maintenance, the rebuild symlinks will delete it.Quote:
Originally Posted by Spooky
Eather way, my main issue is that after upgrading my sites from contao 3 to 4, all web page images include the "files" in the url (ex. img src="files/images/image.jpg"). If I delete the files symlink, they are all broken. I take it from what you are saying, the image url in the webpage should not include the files (ex. img src="images/image.jpg" ).
It seems something isn't quite right since the contao upgrade. Maybe I am missing a setting somewhere?
Cheers,
Allen
It does not say that you should create those symlinks ;). It merely says, that the files in files/ are made available through symlinks. Those symlinks are generated by Contao - for folders that you have set to "public".Quote:
Originally Posted by alien878
Did you set the folder "images" to be public?Quote:
Originally Posted by alien878
Yeah, but the wording is a bit vague :). After I upgraded 3 to 4, all images were broken. Investigating, I discovered all pages were rendered with images including the "files" (ex. img src="files/images/image.jpg"). Adding the files symlink fixed the images.Quote:
Originally Posted by Spooky
If there is a better way to fix this, let me know. I would rather not have to edit every single image (100s) to fix this. If I remember correctly, I can't even change the images as the file chooser was also partially broken without the files symlink.
It was already set to public after the upgrade. All directories in files were set to public. I have tried turning it on/off, but the real problem seems to be that contao is rendering pages with the "files" in the image source names.Quote:
Originally Posted by Spooky
FYI: My upgrade fun was documented here (final post describes what I did in the end): https://community.contao.org/en/show...h-workarounds)
You need to make sure that Contao is able to generate these symlinks.Quote:
Originally Posted by alien878
Try the following:
- Delete the folder web/files/
- Execute composer install
- Check whether the the web/files/ folder is generated again and that it contains a symlink from web/files/images/ to ../files/images/
No, that's normal.Quote:
Originally Posted by alien878
Ah, I see. web/files is a directory that contains the links.
I deleted the files symlink, ran the "Re-create the symlinks" in the backend maintenance and a symlink for "images" appeared. My other two public folders didn't appear, but I just added the symlink by hand. Re-running the backend maintenance doesn't delete the ones I added.
Not sure what happened with my webpage upgrade, but at least it appears I have things fixed. Thanks!
BTW: Back to my original goal--I created a members only page with images from non-public folders. It sometimes works:
- Adding an image to in-line text doesn't work
- Using "Add an Image" to a text element does work
- An image gallery does not work
I can live without it though.
Cheers,
Allen
You need to understand that files that are not in public folders can never be reached from the outside directly. It only works for the thumbnails, i.e. resized versions of those pictures - since the resized versions are stored in a publicly accessible folder.