[Bug]: 5.0.0-beta.2: False positive COG parent folder usage

[arno974]

What is the bug?

Since a recent update of the Lizmap plugin, the project validity checker (safeguards) incorrectly flags COG raster layers as using parent folders.

COG layers are added to the QGIS project via the Protocol HTTP(S) source type (using /vsicurl/). Their datasource is a remote URL (e.g. https://my-lizmap-instance.com/cog/my-raster.cog.tif), not a local file path. However, the safeguard check appears to treat them as file-based layers and compares their path against the project directory, resulting in a false positive warning about parent folder usage. They should not be subject to the "parent folder" safeguard at all.

Steps to reproduce the issue

1. Add a COG raster layer to a QGIS project using Layer > Add Layer > Add Raster Layer > Protocol: HTTP(S), cloud, etc.
   • Example URL: https://demo.lizmap.com/example/cog/my-raster.cog.tif
2. Open the Lizmap plugin and run the project validity check
3. The checker reports a warning about the layer being in a parent folder, even though it is a remote HTTP resource

Versions, safeguards, checks summary etc

Versions :

• Lizmap Web Client : 3.9.7 - commit 800219e95 3liz/lizmap-web-client@800219e95
• Lizmap plugin : 5.0.0-beta.2
• QGIS Desktop : 3.34.6
• Lizmap.com : Yes
• QGIS Server : 3.40.15
• Py-QGIS-Server : 1.9.6
• QGIS Server plugin atlasprint : 3.4.3
• QGIS Server plugin cadastre : 2.2.5
• QGIS Server plugin lizmap_server : 2.14.1
• QGIS Server plugin wfsOutputExtension : 1.8.3

List of Lizmap Web Client modules :

* webdav : 1.2.1 * saas : 1.8.1 * saml : 2.6.0 * samladmin : 2.6.0

List of safeguards :

* Mode : normal
* Allow parent folder : no
* Prevent other drive : no
* Prevent PG service : no
* Prevent PG Auth DB : yes
* Force PG user&pass : yes
* Prevent ECW : yes

Check Lizmap plugin

• I have done the step just before in the Lizmap QGIS desktop plugin before opening this ticket. Otherwise, my ticket is not considered valid and might get closed.