Evaluation bug in tree appearance widget

[Alexander Henket]

Hi. Based on Orbeon 2018.01 CE:

We have an issue using the "appearance="tree tree-plus-minus"" onder xf:select1 when it is in a dialog. I've added a reproduction form here.

The phenomenon: the dialog will continue to show and work with the tree it has in its instance when it opened the very first time after the form was loaded, regardless of changes in that instance, for as long as you work with the same form.

Any changes in the instance under xf:select1/xf:itemset are not evaluated for display/logic. The xforms-inspector however has exactly what you expect in the instance.

Hope you can issue an update for this tricky issue.

Best regards

Alexander Henket

[Alexander Henket]

I've improved readability of the reproduction form a little. You can now see how the main body updates as the items updates, while the dialog does not

[Alessandro Vernet]

Thank you for the updated example Alexander. Erik will follow-up with you on
this, since he's very familiar with that particular code.

‑Alex

-----
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet
--
Sent from: http://discuss.orbeon.com/

[hen...@nictiz.nl]

My return for a friendly reminder :-) Any news?

[Erik Bruchez]

Alexander,

I apologize for missing this message. We will plan to have a look during the
coming week.

-Erik

[Alexander Henket]

Hi. Any news? We have discovered more and more places where this issue hurts us so we need to make a decision. Revert to 3.9 where the old tree still existed or patch the 2018 release.

[Erik Bruchez]

I am sorry no news yet. But we understand the urgency. We will do our best to
look at this on Wednesday this week.

Regards,

[Erik Bruchez]

Here is an update:

- I reproduce the problem with Orbeon Forms 2018.1.1 CE
- I do NOT reproduce the problem with Orbeon Forms 2018.2.1 CE

There are two choices:

- On our side: figure out which change between these two versions fixes the
problem.
- On your side: try out Orbeon Forms 2018.2.1 CE.

[Alexander Henket]

I've checked on my machine what happens with 2018.2.1. The dialogtester.xhtml page now works as expected, but unfortunately the rest of the application breaks in a different way. I get the generic Orbeon Forms error in view. The log reads:

2019-05-30 17:12:47,794 ERROR PageFlowControllerProcessor  - 

+----------------------------------------------------------------------------------------------------------------------+

|An Error has Occurred                                                                                                 |

|----------------------------------------------------------------------------------------------------------------------|

|XPath syntax error at char 116 in {... .}:                                                                            |

|    Cannot find a matching 1-argument function named {http://orbeon.org/oxf                                           |

|/xml/form-runner}component-param-value()                                                                              |

I've checked our code, and all readable files in the war file, but we do not explicitly call that function. I'm not sure what to do next with this.

[Alexander Henket]

The error above came from our main project page. I ran a couple of other pages. All run at least so the problem is apparently confined into something special on the project form. However: on other forms all fr:accordeon widgets initialize as "open" even though they should have been closed, and I cannot close them.

I've extended the dialog tester to include an accordeon that should demonstrate what I see.

[Alexander Henket]

I've managed to bring the inability to load my project form in Orbeon 2018.2.1 down to fr:error-summary. It may not be the only thing that triggers the page load failure, but at least it triggers the same error. Attached a reproduction page

2019-06-04 09:45:43,887 ERROR PageFlowControllerProcessor  - 

[Alexander Henket]

I've flagged https://github.com/orbeon/orbeon-forms/issues/4079 for the form load problem in Orbeon 2018.2.1