lizmap-web-client: Edit layer : can't access to the edit form (loading progress bar)
What is the bug?
I try to edit a layer stored in PostGis. But when I select the layer in the Edition menu nothing happens but a loading progress bar. The form seems to be ok in Qgis and the cfg configuration file has no error.
Steps to reproduce the issue
- Go to Lizmap Web Client
- Click on ‘Edition’
- Select layer to edit
- See error
Expected behavior
Screenshots and logs
In Google Chrome Inspector I have the following error :
Failed to load resource: the server responded with a status of 500 (Internal Jelix Error)
http://IP/websig/lizmap/www/index.php/lizmap/edition/modifyFeature?repository=demo&project=Test_Projet_QGIS_218&layerId=epci_1720200107114840283&featureId=13
In Lizmap web client logs I have:
2020-01-07 11:56:37 192.168.17.31 warning 2020-01-07 11:56:37 [2] SQLite3::query(): Unable to prepare statement: 1, no such table: lizmap_search /var/www/websig/lib/jelix/plugins/db/sqlite3/sqlite3.dbconnection.php 112
2020-01-07 11:56:53 192.168.17.31 error 2020-01-07 11:56:53 [403] Erreur dans la requête (ERROR: column d.adsrc does not exist
LINE 2: a.atthasdef, d.adsrc
^(SELECT t.typname, a.attname, a.attnotnull, a.attnum, a.attlen, a.atttypmod,
a.atthasdef, d.adsrc
FROM pg_type t, pg_attribute a LEFT JOIN pg_attrdef d ON (d.adrelid=a.attrelid AND d.adnum=a.attnum)
WHERE
a.attnum > 0 AND a.attrelid = 18299 AND a.atttypid = t.oid
ORDER BY a.attnum)) /var/www/websig/lib/jelix/plugins/db/pgsql/pgsql.dbconnection.php 174
Environment
- Lizmap version: use of image ‘jancelin/docker-lizmap:3.2.1’
- QGIS Server version: use of image ‘jancelin/qgis-server:2.18LTR’
- QGIS Project version: tested with both 3.4 and 2.18
- OS (Windows, Linux, MacOS, Android…): Ubuntu Server 18
- Browser (Firefox, Chrome…): Chrome
- Lizmap admin information (users, logs…) stored into Sqlite (default)? PostgreSQL? MySQL? no changes, admin infos are stored in SQlite.
Any help would be very appreciated, thanks !
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 17 (3 by maintainers)
@ocelot73 It’s a QGIS server + Postgresql 12 issue. It was fixed in QGIS server https://github.com/qgis/QGIS/pull/32684 Now it has to be fixed in Lizmap