Replies: 8 comments 6 replies
-
|
Awesome work, guys! |
Beta Was this translation helpful? Give feedback.
-
|
No, that job is ongoing in the (This release does include some related fixes though, such as #1189.) |
Beta Was this translation helpful? Give feedback.
-
|
Nice work! We've started testing and this is what we've found so far. We’ll let you know if we find anything more. #1239 #1176 |
Beta Was this translation helpful? Give feedback.
-
Just fixed the texts for #1176! Something like this should do? |
Beta Was this translation helpful? Give feedback.
-
|
Yes that's perfect! |
Beta Was this translation helpful? Give feedback.
-
|
I don't know if this is an on-going issue, because it hasn't worked in previous versions either ... or maybe I'm doing it wrong. |
Beta Was this translation helpful? Give feedback.
-
|
The default attribute table just spits out all attributes and their values - working as intended. I don't think we've talked about adding support for highlighted url:s in this release. I would suggest that you create an issue instead. |
Beta Was this translation helpful? Give feedback.
-
|
We’ve now competed our tests. We’ve tested a large part of the new features and bug fixes. These are our remaining findings: #1186 #1196 #1203 |
Beta Was this translation helpful? Give feedback.
-
|
Hi! One more finding/question: We would like to make changes to this button's settings and can't seem to find where we can do that, see button in the picture below. Is it possible to change the settings? It seems like the “Document”-button in the drawer needs a specified "startdokument" to work – if a startdokument isn’t specified we get a loading window if we push the document-button in the drawer, see picture below. Settings we're searching for:
|
Beta Was this translation helpful? Give feedback.
-
|
It was a bug causing the document handler button to show in the toolbar. It shouldn't have been there at all. The bug is fixed now and the result will show in rc2. |
Beta Was this translation helpful? Give feedback.
-
|
#1263 fixed and added to 3.11. Will be visible in rc2. |
Beta Was this translation helpful? Give feedback.
-
|
Fixed a bug where properties from drawn features (from the sketch plugin etc.) were trying to render in the info-click. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @Hallbergs! #1239 #1186 #1196 #1203 |
Beta Was this translation helpful? Give feedback.
-
|
Hi! Sorry, i just saw that i've missed to respond to those. I think they should be added as new issues. Regarding the last question, maybe @OlofSvahnVbg knows the answer? |
Beta Was this translation helpful? Give feedback.
-
Release candidate timeline
Alright, here's the latest RC! Please help out trying this out.
We usually run 3 weeks RC cycles, which would mean that you have until around Christmas holiday to report your findings!
/The Dev team, by @jacobwod
236 commits and changes in 164 files since the 3.10 release – here's Hajk 3.11! This release was brought to you by @Hallbergs and @jacobwod . Please see the list of commits for all contributors.
This release brings improvements across all across the solution, with a lot of efforts being put into Print, Sketch, the Search results list, LayerSwitcher and Infoclick/MapClickViewer, to name a few.
There are of course upgrades to the latest dependencies that ensure that your Hajk setup is up-to-date when it comes to the latest security patches. 🔒
Continue reading for a details list of changes! 🚀
Discussion and bug reports
Please use https://github.com/hajkmap/Hajk/discussions/ to report your findings from this release candidate.
Changelog
Breaking changes
None.
(Almost) breaking changes
NodeJS Backend only: The NodeJS edition is now built using the current LTS version, namely Node 18. It brings a lot of new features and optimisations (such as native
Fetchthat enables this nice layer verification in Backend). In order to use this new features, you must run the Backend on Node 18.This is not a truly breaking change though: Hajk will still run on lower Node versions (tested on v14) – but you will not be able to use the new feature from #1227.
Major new features
Improved group layer support for Infoclick/FeatureInfo/MapClickViewer
See #768.
Secondary display fields in search results view (#1167)
Admins can now configure more informative search results lists by utilising the possibly to show more information for each result. The secondary label (or labels) will be shown below the main label, with a smaller font size:
Print: option to add a margin to the printout (#1174)
User can optionally add a margin to the PDF that will be created. There is another option to make the margin large enough for it to hold the norther arrow, title and logo too:
Sketch: possible to change draw order (z-index) of the drawn features (#1176)
Previously Sketch features were placed on map in an order that corresponded to the draw order (most recently drawn features were placed on top).
This is still the default behaviour but this addition allows the user to control the z-index afterwards. This nice UI makes it possible to send features to front/back directly, or to move them one step at a time:
Allow users to change layer draw order (#1086)
A third tab, called
Active layerscan now be enabled in LayerSwitcher. This tab makes it possible for the user to rearrange the draw order (a.k.a. z-index) of the layers shown in map. It adds some other goodies too.Still a new feature that will be polished in future releases, but already a usable addition to our UI.
MapClickViewer gains support for hard-coded values when no good attribute exists (#1126)
Some layers need to be clickable but they may lack informative attribute values for features. This was problematic before, as we needed at least one parameter to create a nice label in MapClickViewer.
With the release of 3.11, admins can hard-code a text string as an attribute value in Admin UI by surrounding the string with double quotations marks:
Admin UI:
Client UI:
MarkDown and HTML are now allowed in Announcements (#1161)
We can now create more lively notifications using text formatting and even emojis!
Support for additional, non-latin alphabets in Print, Admin (#1181)
Thanks to the spread of Hajk outside of Sweden, we've discover – and fixed! – a bug related to displaying non-latin characters in some parts of the application. E.g. the PDFs created by Print can now include Cyrillic letters:
DocumentHandler window can now be resized and moved around (#1239)
Previously the DocumentHandler window was limited to being locked to the left side of the screen. With this addition, admins can opt-in to make the window behave just as any Hajk plugin.
Web analytics expanded to also support Matomo (#1143)
Since #1065 we've had support for Plausible. In this release, we also add support for Matomo.
Experimental: list of most recently used plugins (#1171)
This experimental feature adds a button to the bottom of the screen and makes it possible to easily toggle between most recently used plugins:
New features and bug fixes
#883, #915, #1031, #1080, #1093, #1100, #1101, #1108, #1111, #1113, #1114, #1115, #1128, #1129, #1130, #1131, #1132, #1137, #1144, #1145, #1148, #1150, #1155, #1158, #1159, #1160, #1179, #1182, #1186, #1187, #1191, #1193, #1195, #1196, #1200, #1203, #1204, #1206, #1213, #1214, #1215, #1216, #1223, #1224, #1225, #1227, #1231, #1233, #1234, #1245, #1248
Downloads
There are multiple ways to get the latest Hajk up and running, including Docker container.
Pre-compiled releases
As usual, we have prepared three different versions of the pre-compiled solution (scroll down for download links):
Docker container
The container is available on Docker Hub: https://hub.docker.com/r/hallbergs/hajk
Installation
Refer to our installation guide.
What's Changed
target) render in Drawer on small screens #1193. by @jacobwod in Control buttons render in Drawer on small screens, closes #1193. #1194New Contributors
Full Changelog: v3.10.0...v3.11.0-rc.1
This discussion was created from the release Hajk 3.11 Release Candidate 1.
Beta Was this translation helpful? Give feedback.
All reactions