Problem with pageTransitions with criteria "visited" *and* time-settings about marugoto

[yaslena]

This a duplicate of #116

[martindusinberre]

@Helena-LiT It's not quite a duplicate because the radioButtonExercise transition, which was also part of #116 , is fixed.

[nemtish]

should be fixed with 4ab23d1

[martindusinberre]

Thanks so much, @nemtish we'll test it tomorrow. Best, Martin

[yaslena]

@Helena-LiT It's not quite a duplicate because the radioButtonExercise transition, which was also part of #116 , is fixed.

@martindusinberre The changes that presumably caused all these bugs were made at the same time and in the same instance (the trailer bug is not newer than the other transition bugs), so these two issues should be linked when people are looking for the cause of the problem. Adding a duplicate marker is just one way in GitHub to link two related issues, which makes sense when all of #120 is contained in #116.

[yaslena]

I would like to add some of my observations on the transition bug (autotransition + page criteria: visited) based on the Madness (Managing Lunacy storyline):

• presence of autotransition on a page (in page.json) causes the game to disregard any "page criteria" : "visted" objects (in pageTransition.json) displaying pageTransitions (button text) that should not be available
• presence of autotransition on a page (in page.json) causes the game to disregard any "page criteria" : "visted" objects (in pageTransition.json) automatically triggering pageTransitions that should not be available
• presence of autotransition on a page does not cause the game to disregard other page criteria like "exerciseCriteria": "correctInput"
• autotransition can currently only trigger Transition1 but will never automatically trigger Transition2, Transition3 and so on even when transition criteria for these other page transitions are met.

[martindusinberre]

Setting aside these other transition issues for a moment: the original bug, which appears with a combination of "visited"/"notVisited" criteria in pageTransition.json files and the timer/autoTransitionOnTimerExpiration being "true" in page.json files is still there (on the test system, not on the live system).
Whereas previously (as described above) two buttonTexts appeared where they shouldn't, the problem tonight was different: the buttonTexts worked fine (i.e. only one appeared), but the timer counted me down from 12 minutes, even though it was set to 300 in the page.json file. See the two screenshots (top screenshot taken when there were 10 minutes left on the timer).

[yaslena]

I don't have the same problem with the timer in the trailer. I have tested this page in firefox and edge browsers and I always get the correct 5min displayed. Maybe it's a browser problem (chrome?) or the problem is already solved.

[yaslena]

I would like to add some of my observations on the transition bug (autotransition + page criteria: visited) based on the Madness (Managing Lunacy storyline):

* presence of **autotransition** on a page (in page.json) causes the game to **disregard** any **"page criteria" : "visted"** objects (in pageTransition.json) **displaying** pageTransitions (button text) that should not be available

* presence of **autotransition** on a page (in page.json) causes the game to **disregard** any **"page criteria" : "visted"** objects (in pageTransition.json) automatically **triggering** pageTransitions that should not be available

* presence of **autotransition** on a page **does not** cause the game to disregard other page criteria like **"exerciseCriteria": "correctInput"**

* **autotransition** can currently **only trigger Transition1** but will never automatically trigger Transition2, Transition3 and so on even when transition criteria for these other page transitions are met.

I think all of the above was already solved.

[martindusinberre]

I don't have the same problem with the timer in the trailer. I have tested this page in firefox and edge browsers and I always get the correct 5min displayed. Maybe it's a browser problem (chrome?) or the problem is already solved.

OK, many thanks for pointing this out: has just worked for me fine in Firefox, too. What I experienced may be connected to #126 (I was testing many games consecutively) so for the time being, I'll close this assuming that this particular issue (combination of criteria + timer) is fixed.