Hajk 3.10 Release Candidate 1

[jacobwod]

A fantastic release, full of new amazing features, is ready to be tested. Grab it at the release page and report your findings in this thread!

[WCarlsson]

Looks amazing with all the newly implemented features!

Regarding the attribute table for wms layers there is a comment in the code that further work is needed for this to work with QGIS Server so the problem seems to already be known be we are interested in wheter this will be fixed in RC or if its in a later stage?

We have also experienced some bugs with the layercomparer where the button to end the comparison is not visualised.
If the user switches layers to compare the pop up notice is replicated and if they end the comparison after switching layers to compare multiple background layers can end up as active at the same time.

[jacobwod]

Thanks for the feedback!

There is currently no activity regarding the attribute table view. Feel free to tell more about the problems you run into.

Regarding LayerComparer: can you please tell which steps are needed to reproduce the "multiple snackbars problem"? I'm trying to reproduce (so I can fix it) but fail.

[WCarlsson]

Regarding attribute table view: See LayerItem.js

Layercomparer:
I feel like I used it in a normal way when encountering the problem.

1. Compare two layers in layercomparer in a map. A snackbar appears.
2. Switch one layer you are comparing to another layer in the layercomparer. For every time a layer is changed a new snackbar appears.

[jacobwod]

Regarding attribute table view: See LayerItem.js

Unfortunately I only see a red underline, not what causes it. The line itself is correct JS so it's hard to tell what's wrong here without further info.

[jacobwod]

Layercomparer: I feel like I used it in a normal way when encountering the problem.

1. Compare two layers in layercomparer in a map. A snackbar appears.
2. Switch one layer you are comparing to another layer in the layercomparer. For every time a layer is changed a new snackbar appears.

Ahh, now I see. Will take a look later this week! :)

[WCarlsson]

Yes sorry a bit unclear from me, I was thinking of the comment that begins "TODO" were it seems like you encountered and identified the problem with QGIS Server and that it requires some more work.
I've tried with https://hajk.orebro.se/api/v1/proxy/qgisserver/maps/Test/Redigering_test2?SERVICE=WFS&service=WFS&version=1.0.0&request=DescribeFeatureType&typeName=TEST3&outputFormat=application%2Fjson and it defaults to gml

[jacobwod]

Closed LayerComparer bugs in 35765bc 👍

[lina-sbk-gbg]

I missed to publish my findings here. See issue #1104 #1105 och #1106

[jacobwod]

Excellent, thanks! 👍

[lina-sbk-gbg]

And a new one in #1107

[bitmapbulgaria]

Hi, guys! Awesome work, really!
Just want to make a point, that in deployment instruction is forgotten to be mentioned, that the folder /App_data should also be copied in root folder, where the files for the compiled backend and client are. In the compiled dist/api/services/config.service.js, on 49 is the reference to App_data

const pathToFile = _path.default.join(process.cwd(), "App_Data", ${map}.json);

Sorry, I'm a noob yet, but this path is needed, for the backend to work.
P.S. I am behind a ssl secured Nginx, so I had to setup forward proxy to my backend, for my configuration to work. Excuse me, if this is not relevant, best regards!

[jacobwod]

Hi! Thanks for the feedback!

Are you referring to the installation instructions? They are specifically designed for the prepared releases (the ones that you can download from the Release page, such as this one for 3.10).

If you download the NodeJS-edition and unzip you will find the App_Data directory directly inside the root folder. So basically

cd hajk-[version-number]
node index.js

will get you going as the App_Data exists in hajk-[version-number].

But perhaps you refer to some other method such as launching in development mode?

[bitmapbulgaria]

Hi, Jacob! I'm running the NodeJS variant (new-backend,new-admin and new-client variants) on Ubuntu 22.04. My point was for the following instruction about compile and moving the distro package of the backend in some www folder, where it will start: https://github.com/hajkmap/Hajk/tree/master/new-backend#deploy [image: image.png] In this "Deploy" section it would be a good idea to mention moving the App_data folder to the new location, where the backend /distro files have been moved for production (for example ( /var/www/html/ ), because this folder is outside. If we move /dist/* to /var/www/html/ , but App_data is not moved, the backend will crash. :) I hope this will help some new users that are not familiar with the server. Have a nice day, I hope I explained it well. Ivan

…

On Wed, 31 Aug 2022 at 11:48, Jacob Wodzyński ***@***.***> wrote: Hi! Thanks for the feedback! Are you referring to the installation instructions <https://github.com/hajkmap/Hajk/wiki/Installation-guide-%28for-pre-packaged-releases%29>? They are specifically designed for the prepared releases (the ones that you can download from the Release page, such as this one for 3.10 <https://github.com/hajkmap/Hajk/releases/tag/v3.10.0>). If you download the NodeJS-edition and unzip you will find the App_Data directory directly inside the root folder. So basically cd hajk-[version-number] node index.js will get you going as the App_Data exists in hajk-[version-number]. But perhaps you refer to some other method such as launching in development mode? — Reply to this email directly, view it on GitHub <#1092 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANYXEXLMHH4CMAKVWXPWLATV34L5ZANCNFSM5W4354XA> . You are receiving this because you commented.Message ID: ***@***.***>

[jacobwod]

Ah! Now I see which part of the documentation you mean. I'll fix that, thanks! 👍