-
Notifications
You must be signed in to change notification settings - Fork 69
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
CLP: View screen should match Edit screen in Drupal #18954
Comments
@mmiddaugh I wanted to just let you know I made a ticket for this but I'm not sure if it needs to be prioritized or not. But at least you know it exists now. CC: @FranECross |
@laflannery Thanks so much! I'll move it to Next Refinement so that it'll be ready in case we do decide to prioritize. |
Seems like the culprit here is a custom module that would hide unused widgets on View back before that was a core widget functionality (leave "Show if empty" unchecked) |
My work on the PR is basically done. Enabled and disabled sections are now functioning as expected. I have also rearranged/renamed/reformatted a few fields so the View and Edit screens match better. Remaining work is writing up QA steps etc. |
@FranECross @mmiddaugh @laflannery - I would like to request a modification to one of the ACs:
I have a solution working that partially resolves this. It won't show sections of the page that have never been enabled. However, if an editor enables a section and then later disables it without manually clearing out the content, that content will still show on Node View. This is not ideal state, but I'd argue it's still functional. Resolving this would require a much larger effort and would balloon the size of this ticket. We'd need to tag in an engineer and discuss tradeoffs of various possible solutions. I suggest that we ship my solution which improves 80% of the scenarios. Here's a comparison from my QA of the current state in Prod vs the state in my tugboat: ✅ = Ideal state
Edit and here are the issues I stubbed for the remaining quirks |
@davidmpickett Thanks for providing the amazing table showing prod/future prod. I'm in favor of shipping with the 80% improvement, but defer to Michelle and Laura for final call. |
Agree! The table is amazing and shipping an 80% improvement is a great win. |
End of sprint update
|
Verified on prod https://prod.cms.va.gov/initiatives/va-health-connect |
Status
[2024-09-06] [Dave] Pulled in to sprint as a Site Building ticket
[2024-08-15] [Fran] Prioritization not decided yet, but moving to Next Refinement so it will be ready in case this bubbles up.
Background
In Drupal for the Campaign Landing page content type, the edit screen has multiple sections that can be enabled to build the page. However, very few of these sections actually show on the View screen in Drupal when they are enabled. There is no issue on the FE - everything is working as expected on the FE - this is just a Drupal View issue.
This did however recently lead to quite a bit of confusion when Justin from VHA was trying to add the Downloadable resources section to a page for SECVA. He, as well as the Helpdesk all thought this section was not working because they couldn't see it being added in Drupal. Slack thread for reference
Description
In order to avoid future confusion, we should ensure that all enabled sections on a CLP are also shown on the View screen in Drupal.
Example (This is a tugboat link so it may break but I also have screenshots)
Drupal Edit screen, I have enabled ALL sections, so this is everything that should be showing on the View screen
Drupal Node view: Only Hero Banner, Why this matters, What can you do, and connect with us show in the accordion style. Then Reusable Q&A show below
Acceptance Criteria
Issues out of scope
The text was updated successfully, but these errors were encountered: