Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[timepoint_list] Visit / approval stage display is broken #8439

Closed
CamilleBeau opened this issue Mar 13, 2023 · 7 comments
Closed

[timepoint_list] Visit / approval stage display is broken #8439

CamilleBeau opened this issue Mar 13, 2023 · 7 comments
Labels
Bug PR or issue introducing/requiring bug fixes (not mutually exclusive with the Feature label)

Comments

@CamilleBeau
Copy link
Contributor

Describe the bug
If you modify the visit or approval stage from the timepoint list once, the stage display in the table to the right does not change. In any subsequent modifications without reloading the page, the display shows whatever the stage previously was. If the page is refreshed, the stage shows the correct status again.
Screen Shot 2023-03-13 at 1 34 57 PM
Screen Shot 2023-03-13 at 1 35 37 PM
Screen Shot 2023-03-13 at 1 36 08 PM

To Reproduce
Steps to reproduce the behavior (attach screenshots if applicable):

  1. Go to a visit that is passed
  2. Click on "In Progress" stage in the lefthand sidebar without refreshing the page.
  3. Notice that the stage in the display table to the right has not changed.
  4. Without refreshing, click back to a different stage. Notice that now the display changes to "In Progress" even though a different stage was selected.
  5. Refresh the page, and notice that the stage in the display table is now the correct one.

What did you expect to happen?
The display stage to be modified to match what is selected in the sidebar, and what is in the database.

@CamilleBeau CamilleBeau added the Bug PR or issue introducing/requiring bug fixes (not mutually exclusive with the Feature label) label Mar 13, 2023
@christinerogers
Copy link
Contributor

christinerogers commented Jun 12, 2023

I see this issue as simply that the page isn't dynamic. if you save a change, you have to refresh to see it take effect. I think this is a bigger question for making more pages/modules dynamic, probably too big for a summer student unless @driusan already has a plan in mind that can be quickly implemented.
thoughts @CamilleBeau ?

cc @racostas to be confirmed in a Loris meeting - maybe a good gsoc ticket if it's important and the solution is straightforward

@driusan
Copy link
Collaborator

driusan commented Jun 12, 2023

Yes, the problem is that the page isn't dynamic. The update to the database happens after the page is rendered IIRC.

A summer student could probably do something so that the actions on the page result in a 303 Redirect to return to the page which would effectively be the same as the user re-loading the page without completely overhauling the module.

@CamilleBeau
Copy link
Contributor Author

@christinerogers @driusan Yes, it's true that if you refresh it the correct value is shown. However, after selecting a new value, the whole page reloads and updates to the previously selected value. E.g. if it starts out as "Pass" and I select "In progress", it will reload as "Pass", and then if I select "Failure", it will reload as "In progress".

So it seems to be dynamic since the page refreshes and the variable is modified, but it is not modified to the correct value.

@christinerogers christinerogers added the GSOC Google Summer of Code related label May 13, 2024
@christinerogers
Copy link
Contributor

Hi @racostas and/or @CamilleBeau -- Could either of you please confirm:
Since this issue was resolved by CCNA#7223, could it likely be quickly resolved in LORIS by the same fix ?

Rolando --- if not, please 'remove' the GSOC tag I've just added. thanks

and generally, folks -- is it worth getting this bug fix in to the 26 release ?

@CamilleBeau
Copy link
Contributor Author

@skarya22 Can you confirm if your fix is relevant to the 26 code?

@skarya22
Copy link
Contributor

@christinerogers There are these two PRs that were merged into LORIS main.
#9040
#9072

I believe that the issue duplicated and this instance of it was resolved but not closed

@christinerogers christinerogers removed the GSOC Google Summer of Code related label May 14, 2024
@christinerogers
Copy link
Contributor

already resolve, perfect. thank you all.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug PR or issue introducing/requiring bug fixes (not mutually exclusive with the Feature label)
Projects
None yet
Development

No branches or pull requests

4 participants