A brand new node for working with Handlebars templates – build HTML and text snippets based on templates dynamically and use JSON column and variable input to fill placeholders
Based on the numerous feedback from our community and our own experience with recent KNIME releases, we’ll continue to support KNIME 4.7 for the time being. No matter which KNIME version you are using, please always make sure to set an update site URL which resembles your KNIME version:
KNIME 4.7:https://download.nodepit.com/4.7
KNIME 5.1:https://download.nodepit.com/5.1
KNIME 5.2:https://download.nodepit.com/5.2
KNIME 5.3:https://download.nodepit.com/5.3
Questions?
Enjoy the new functionality, see you around, and for questions feel free to get in touch here or mail@palladian.ws
Hello,
I got the following strange dependency error and I cannot update my KNIME AP 3.1.0 installation (on Windows 10) with version 3.1 of Palladian nodes:
Cannot complete the install because one or more required items could not be found.
Software being installed: Palladian for KNIME 3.1.0.202409011740 (ws.palladian.nodes.feature.feature.group 3.1.0.202409011740)
Missing requirement: Palladian for KNIME 3.1.0.202409011740 (ws.palladian.nodes 3.1.0.202409011740) requires 'osgi.bundle; org.knime.workbench.repository [4.7.0,5.3.0)' but it could not be found
Cannot satisfy dependency:
From: Palladian for KNIME 3.1.0.202409011740 (ws.palladian.nodes.feature.feature.group 3.1.0.202409011740)
To: org.eclipse.equinox.p2.iu; ws.palladian.nodes [3.1.0.202409011740,3.1.0.202409011740]
Looking at the error, it seems the allowed osgi version range of org.knime.workbench.repository bundle excludes the 5.3.0 version and up.
By the way, my KNIME 5.3.1 installation appears to have installed the 5.3.0 version of that bundle: when I look at the installation configuration I see the following:
This looks like you’re not using the 5.3-specific update site, but an older one which was probably set up before upgrading your KNIME installation. Can you check this?
This seems to be a common issue, so we’ll have an auto-update mechanism in an upcoming version which automatically updates the URLs! Thank you for your support with that @danielesser