Servoy 2022.03.3_LTS

We are pleased to announce the availability of Servoy 2022.03.3_LTS (release number 3745)

This release includes the update of Apache Commons Text lib to 1.10 because of CVE-2022-42889

See 2022.03.3_lts_fixes for the list of fixes for this release since 2022.03.1 (where this release is build on top of)

This version is available through the download site

or through the update site URL: http://download.servoy.com/developer/lts
If you want to use the LTS release enable the above LTS update site and disable the ‘latest’ update site so you only update to LTS updates.

if you want to stick to the 2021 LTS (2022.3.3 LTS) then disabled the lts and latest updates sites, and add this site: https://download.servoy.com/developer/lts_2021/
Updates on that LTS will be published there.

The LTS of 2020 (2020.03.3_LTS) is not supported anymore from now on, no more updates will be on that release.
You are strongly recommended to move over to one of the supported branches (2021 LTS, 2022 LTS or 2022 Latest)

For solutions that are already in production it is a good idea to stick to this version if you don’t need to newer features right now.

jcompagner:
it also has a few more changes you can see here: issues. Especially in the http client plugin

Hi Johan,

the link to the resolved issues, points to 2022.9 fixes.
Also you mention changes in http client plugin. I do see this as part of the 2022.9 fixes, not for 2022.3.3

Can you please correct this and also confirm these http plugin changes are not part of 2022.3.3 (or otherwise extend the release notes)

Thank you!

mboegem:
the link to the resolved issues, points to 2022.9 fixes.

that was a wrong copy/paste and just pointed to the wrong issue page. (the correct one was also there already a bit later in the post)

I’ve installed 2022.03.3_LTS as a standalone on my Mac OSX 10.15.7 / MySQL, to do some testing prior to upgrading from 2021.03.3_LTS

When I launch the IDE I get all the console messages while npm runs, then a large number of errors about ‘dateinput’
What’s the appropriate action?

Error: src/designer/designform_component.component.ts:122:67 - error NG8001: ‘dateinput’ is not a known element:

  1. If ‘dateinput’ is an Angular component, then verify that it is part of this module.
  2. To allow any element add ‘NO_ERRORS_SCHEMA’ to the ‘@NgModule.schemas’ of this component.

122 <ng-template #dateinput let-callback=“callback” let-state=“state”><dateinput [servoyAttributes]=“state.model.servoyAttributes” [background]=“state.model.background” [backgroundPicker]=“state.model.backgroundPicker” [border]=“state.model.border” [cssPosition]=“state.model.cssPosition” [cutoffNextYear]=“state.model.cutoffNextYear” [dataProviderID]=“state.model.dataProviderID” (dataProviderIDChange)=“callback.datachange(state,‘dataProviderID’,$event, true)” [displayFormat]=“state.model.displayFormat” [entryTemplate]=“state.model.entryTemplate” [foreground]=“state.model.foreground” [foregroundPicker]=“state.model.foregroundPicker” [inputFormat]=“state.model.inputFormat” [location]=“state.model.location” [placeholderText]=“state.model.placeholderText” [readOnly]=“state.model.readOnly” =“state.model.size” [tabSeq]=“state.model.tabSeq” [toolTipText]=“state.model.toolTipText” [onDataChange]=“callback.getHandler(state,‘onDataChange’)” [onFocusGained]=“callback.getHandler(state,‘onFocusGained’)” [onFocusLost]=“callback.getHandler(state,‘onFocusLost’)” [servoyApi]=“callback.getServoyApi(state)” [name]=“state.name” #cmp>



Error: src/designer/designform_component.component.ts:122:79 - error NG8002: Can't bind to 'servoyAttributes' since it isn't a known property of 'dateinput'.

122 <ng-template #dateinput let-callback="callback" let-state="state"><dateinput [servoyAttributes]="state.model.servoyAttributes" [background]="state.model.background" [backgroundPicker]="state.model.backgroundPicker" [border]="state.model.border" [cssPosition]="state.model.cssPosition" [cutoffNextYear]="state.model.cutoffNextYear" [dataProviderID]="state.model.dataProviderID" (dataProviderIDChange)="callback.datachange(state,'dataProviderID',$event, true)" [displayFormat]="state.model.displayFormat" [entryTemplate]="state.model.entryTemplate" [foreground]="state.model.foreground" [foregroundPicker]="state.model.foregroundPicker" [inputFormat]="state.model.inputFormat" [location]="state.model.location" [placeholderText]="state.model.placeholderText" [readOnly]="state.model.readOnly" ="state.model.size" [tabSeq]="state.model.tabSeq" [toolTipText]="state.model.toolTipText" [onDataChange]="callback.getHandler(state,'onDataChange')" [onFocusGained]="callback.getHandler(state,'onFocusGained')" [onFocusLost]="callback.getHandler(state,'onFocusLost')" [servoyApi]="callback.getServoyApi(state)" [name]="state.name" #cmp></dateinput></ng-template>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[/quote]

that is most of the time already a result of something else.

To see what that is, make sure the TI NGClient console is cleared, and then do a copy ngclient sources → copy and clean and let it fully build.

and give the complete console. to see where the error really starts.

i don’t fully understand what “dateinput” tag is, by default i don’t think servoy ships such a thing,. do you have custom components? did you port those already to TiNG?

Hi Johan, Thanks for the quick response, full console output attached following a restart. Should we expect the npm output each time the IDE launches? It takes a couple of minutes to complete.

then do a copy ngclient sources → copy and clean and let it fully build.

not sure how to do that.

We were planning to stick with NG client for now, not using the Ti client yet

I will check for custom components

Servoy console 2022-12-13.txt (74.5 KB)

this has to be custom components (because i dont think any components is called dateinpout in the once i see being installed)

if you stick to ng1 then you just have to set the preferences to to use the ng1 designer and start ng1 in stead of ng2.

problem is it will do that npm at launch until it can build fully correctly once, which i think because of custom components doesnt happen at this time
So yes then it will constantly try this

Found and removed the conflicting custom component, thanks for the handy tips. Console now looks clean.