waldronlab / waldronlab/BugSigDB
Study page 42278997 does not display study information or controls (Edit, History, Delete, and Add a new Experiment buttons)
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 9
- Forks
- 9
- Avg merge
- 1h 56m
- Merged PRs (30d)
- 4
Description
Hi @tosfos,
I would like to report an issue with the study page for Study 42278997.
Page URL
Description
The study page for Study 42278997 is not displaying the normal BugSigDB study-page content.
Normally, after creating a study, the study page displays the Study Information section, including the citation details, as well as the Edit, History, Delete, and Add a new Experiment buttons.
However, on Study 42278997, only the study title and the Categories section are displayed. The Categories section shows:
- Pages using DynamicPageList4 parser function
- Pages using DynamicPageList4
The normal Study Information section and the study controls are missing.
Steps to Reproduce
- Go to https://bugsigdb.org/42278997
- View the study page.
- Observe that the study title is displayed.
- Observe that the normal Study Information section and study controls are missing.
Expected Behavior
The study page should display the normal BugSigDB study layout, including:
- Study Information
- Citation information (PMID, DOI, authors, journal, year, etc.)
- Background
- Edit, History, and Delete buttons
- Add a new Experiment button
Actual Behavior
The study title is displayed, but the main study content is missing.
Instead, the page displays only the Categories section containing:
- Pages using DynamicPageList4 parser function
- Pages using DynamicPageList4
The page then proceeds to the footer.
Screenshots
Two screenshots are attached:
- A normal BugSigDB study page showing the expected Study Information and study controls.
- Study 42278997 showing the missing study content.
Environment
- Browser: Google Chrome
- Device: Desktop
- Operating System: Windows 11
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by opening the reported study page at https://bugsigdb.org/42278997 and compare it with a normal BugSigDB study page, focusing on how the Study Information and study controls are rendered. Trace the page entry point for study 42278997 and determine why only the title and Categories section appear; done means the expected study information and controls display normally.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100