-
-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Specific media destination folder setup does not work #4975
Comments
After some more trial and lot's of error i'm one step closer to the solution: Only downside now: uploading a picture via LWC sets the attribute to: "../media/Spielgerät_Fotos/MyTestPic.jpg" Is there any chance to get rid of the ".." ? |
I was going to suggest to "upload a file from LWC and check the path created", so as to upgrade your existing dataset.
I think it's on purpose. Any downside about this ? I think the logic is to always keep a relative path from the QGIS project. |
well, putting it that way it really kind of makes sense - the thing is, i would need it without the leading "../" in order to work with the pictures in other (non LWC) projects (QField Cloud in particular). If nothing helps, i'll try it with a PostGres trigger which cleans the leading "../" - would be the least favourable solution, but at least it would be something :) |
What is the bug? (in English)
I follow precicely the instructions to setup a "central" media folder which should be shared by different projects. Folder structure on the server is:
/var/www/cutomerA/lizmap/install/customerA
---ProjectA/ProjectA.qgs
---ProjectB/ProjectB.qgs
---media/Fotos_Spielgerät/69_1.jpg
Permissions are correctly set for www-data.
In ProjectA, the layer "Playground" has a column "Picture_1" and an example attribute is: "Fotos_Spielgerät/69_1.jpg"
In the layer settings, i set the attribute form widget to "Attachment", default path to ../media/ and "Store Path as Relative to Project Path"
In the QGIS attribute form it won't show a picture (folder structure is obviously the same as on server), as well as on Lizmap.
Am i missing something or is this a bug?
Steps to reproduce the issue
Versions, safeguards, check summary etc
Versions :
List of Lizmap Web Client modules :
* Version Lizmap Web Client 3.8 needed
List of safeguards :
* Mode : normal
* Allow parent folder : no
* Prevent other drive : yes
* Prevent PG service : yes
* Prevent PG Auth DB : yes
* Force PG user&pass : yes
* Prevent ECW : yes
Check Lizmap plugin
Operating system
Ubuntu 22.04
Browsers
Firefox
Browsers version
Firefox 115
Relevant log output
No response
The text was updated successfully, but these errors were encountered: