biocompute-objects / biocompute-objects/portal_userdb

Next Button Won't Click or Allow to Save

Open
#500 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
1
Forks
1
Avg merge
10m
Merged PRs (30d)
1

Description

**Describe the bug**
I will open a Draft BCO that has already been created. I was editing the version number. Once I edited it the Next button glows blue, but it won't allow me to click on it. If I can't click on Next then I can't save the BCO.

**To Reproduce**
Steps to reproduce the behavior:
1. Go to https://biocomputeobject.org/builder?https://biocomputeobject.org/ARGOS_000012/DRAFT or even biosampleMeta-HIVE does it too
2. Click on the draft itself
3. Update the BCO version
4. Try to click on the blue button to go next

**Expected behavior**
I expected the BCO to go to the next page so that I could press 'Save BCO Draft' and therefore my changes were saved.

**Screenshots**
If applicable, add screenshots to help explain your problem.

**Desktop (please complete the following information):**
- OS: on my Mac 15.3.2 (24D81) also known as Sequia?
- Browser Chrome
- Version Version 134.0.6998.89 (Official Build) (x86_64) for chrome

**Smartphone (please complete the following information):**
- Device: [e.g. iPhone6]
- OS: [e.g. iOS8.1]
- Browser [e.g. stock browser, safari]
- Version [e.g. 22]

**Additional context**
It only does it for a couple of DRAFT BCOs not all of them. I only have had issues a couple times.

WORKAROUND:
The work around is to just manually update it in Raw JSON or the Tree JSON and then save it and it works. Super weird

Contributor guide

Open the contributing guide

Research direction

Start at the builder page linked in the reproduction steps and reproduce the failure by editing the version of an existing draft BCO, including the affected drafts if available. Compare the normal form flow with the Raw JSON and Tree JSON workarounds; done means the Next button advances reliably after a version edit and the draft can be saved.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.