You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using a option set provider with autocomplete widget, which uses refresh = True inside a collection on page level (is collection), the user can not switch between the tabs / sets and is stuck at the last created one, if a new one is created or the first one when answering the questions.
This only occurs on option set providers inside a collection with refresh = True. For example with rdmo-plugins-gnd.
Expected behaviour / Erwartetes Verhalten
The user can switch between tabs / sets.
Steps to reproduce / Schritte zum Reproduzieren
Create a catalog which includes a question with an option set provider which uses refresh = True on a page which is a collection
On the page with is collection flag click on + Set and give it a name, for example test1
Fill out the question(s)
Add another set by clicking on + Set and give it a name, for example test2
Fill out the question(s)
Click on the fist tab / set (test1) -> Switches back to the previously created one (test2)
Page with is collection enabled and a question using an option set provider with refresh = True as autocomplete widget type: The user can not switch to "test1" after creating "test2" and is stuck on the last created one.
Or if already filled out:
Go to the page which is a collection with the option set provider and autocomplete
Try to switch between the sets -> Switches back to the first one (test1)
Page with is collection enabled and a question using an option set provider with refresh = True as autocomplete widget type: After the user browsed to the page, the user can not switch from "test1" to "test2".
Note: In the example screenshots the rdmo-plugins-wikidata plugin was used, which does not use refresh = True by default. It was modified for testing purposes by setting the refresh flag to True. A better example is the rdmo-plugins-gnd plugin.
Context / Kontext
Linux
RDMO version 2.2.0, also tested with 2.1.3
References / Verweise
The text was updated successfully, but these errors were encountered:
Hi @hafu , thanks for reporting. The last commit should fix the bug. If you have time, you can install the wheel from the GitHub action once it is completed.
Description / Beschreibung
When using a option set provider with autocomplete widget, which uses
refresh = True
inside a collection on page level (is collection), the user can not switch between the tabs / sets and is stuck at the last created one, if a new one is created or the first one when answering the questions.This only occurs on option set providers inside a collection with
refresh = True
. For example with rdmo-plugins-gnd.Expected behaviour / Erwartetes Verhalten
The user can switch between tabs / sets.
Steps to reproduce / Schritte zum Reproduzieren
refresh = True
on a page which is a collectionPage with is collection enabled and a question using an option set provider with
refresh = True
as autocomplete widget type: The user can not switch to "test1" after creating "test2" and is stuck on the last created one.Or if already filled out:
Page with is collection enabled and a question using an option set provider with
refresh = True
as autocomplete widget type: After the user browsed to the page, the user can not switch from "test1" to "test2".Note: In the example screenshots the rdmo-plugins-wikidata plugin was used, which does not use
refresh = True
by default. It was modified for testing purposes by setting therefresh
flag toTrue
. A better example is the rdmo-plugins-gnd plugin.Context / Kontext
References / Verweise
The text was updated successfully, but these errors were encountered: