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

VACMS 19273 - menu exception manila and add to menus download #2303

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

eselkin
Copy link
Contributor

@eselkin eselkin commented Oct 4, 2024

Summary

  • Adds manila-va-clinic to menu download, but because manila-va-clinic has no parent, exception is created to allow menus to be created for it.
  • Sitewide team (we own facility pages)

Related issue(s)

Testing done

  • Manual testing by numerous people for existence of menus, breadcrumbs accessibility, and get updates box correctness

Screenshots

Manila VAMC main page Screenshot 2024-10-07 at 1 28 21 PM
Manila VAMC main page - showing breadcrumb to current page content Screenshot 2024-10-07 at 1 28 47 PM
Manila VAMC main page - showing link to About us nested page Screenshot 2024-10-07 at 1 29 05 PM
Manila VAMC About Us page - with breadcrumb back to Manila VAMC (not system) Screenshot 2024-10-07 at 1 29 26 PM
Manila VAMC main page - Get Updates content Screenshot 2024-10-07 at 1 31 16 PM

What areas of the site does it impact?

Manila VAMC page

Acceptance criteria

  • Manila menu appears on the left sidenav of Manila VA Clinic pages based on Section
  • Preview works on Manila pages
  • Manila pages build successfully

Quality Assurance & Testing

  • I fixed|updated|added unit tests and integration tests for each feature (if applicable).
  • No sensitive information (i.e. PII/credentials/internal URLs/etc.) is captured in logging, hardcoded, or specs
  • Linting warnings have been addressed
  • Documentation has been updated (link to documentation *if necessary)
  • Screenshot of the developed feature is added
  • Accessibility testing has been performed

Error Handling

  • Browser console contains no warnings or errors.
  • Events are being sent to the appropriate logging solution
  • Feature/bug has a monitor built into Datadog or Grafana (if applicable)

Authentication

  • Did you login to a local build and verify all authenticated routes work as expected with a test user

Requested Feedback

Because of the status of tugboats rebuilding every night and resetting, you'll have to test locally from a tugboat with Manila VAMC (not the system) published, and the Manila About Us page published and make sure the parent in the menu is pointing to the About Manila VAMC <nolink> menu section.

To publish VAMC
Go to:
/node/1059/edit
Changes Save as to published and add some text in textbox and click save

To publish About us page and make sure it's in the correct location go to
/manila-va-clinic/about-us
then edit
then under menu settings on the right, choose:
Parent link to be:
Screenshot 2024-10-07 at 10 19 38 PM
and keep the Alias URL the same.
Change save as to: published
add some text in the text box and save

Point your content build to the tugboat to build with:
yarn build --use-cached-assets --pull-drupal --drupal-address=https://tugboatmainaddress
and wait the 900000000 minutes

@va-vfs-bot va-vfs-bot temporarily deployed to master/main/SPIKE-VACMS-19272-exception-Manila October 4, 2024 21:35 Inactive
@eselkin eselkin changed the title SPICE VACMS 19272 exception manila VACMS 19273 - menu exception manila and add to menus download Oct 7, 2024
@eselkin eselkin marked this pull request as ready for review October 7, 2024 20:38
@eselkin eselkin requested review from a team as code owners October 7, 2024 20:38
if (!regionPageUrlPath) {
if (
!regionPageUrlPath &&
page.entityUrl.breadcrumb[1]?.text !== 'Manila VA Clinic'
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Manila VAMC has no parent system published so the path is empty but it still points somewhere (to itself as the Clinic/System)

@randimays
Copy link
Contributor

@eselkin Working on setting up a Tugboat to test.

you'll have to test locally from a tugboat with Manila VAMC (not the system) published

Does this mean I need to publish the Manila VAMC (VAMC Facility)?

Screenshot 2024-10-08 at 10 41 59 AM

@eselkin
Copy link
Contributor Author

eselkin commented Oct 8, 2024

Yes. Publish the facility. Not the VAMC System with the same name.

@jilladams
Copy link
Contributor

(To match what will happen in Prod, the System should be Published > Archived)

@randimays
Copy link
Contributor

@jilladams

(To match what will happen in Prod, the System should be Published > Archived)

Does this mean the VAMC System should be published, then archived?

@randimays
Copy link
Contributor

@eselkin I don't have the option to select the correct menu in the About page per your instructions:
Screenshot 2024-10-08 at 3 00 34 PM

Screenshot 2024-10-08 at 2 58 56 PM

@jilladams
Copy link
Contributor

@randimays yes: in Prod we are going to Publish and then Archive the Manila VAMC System. It would be best to do that for testing, to make sure that no behavior is negatively impacted by that change, when it happens.

@eselkin
Copy link
Contributor Author

eselkin commented Oct 8, 2024

@randimays Sorry, didn't see the message. So, you can make a <nolink> menu item under Manila VA Clinic or spin up a new tugboat and that should have the right menu structure.

To make a nolink menu item,
go to:
/admin/structure/menu/manage/manila-va-clinic
Click "+ Add link" button at the top
In the title box add something like: About Manila VA Clinic
In the link box add: <nolink>
Make sure Enabled is still checked
In the Parent link section on the right Select
Screenshot 2024-10-08 at 4 12 30 PM
Then go back into the about us page and change the parent link to whatever you called the new nolink menu item under -- Manila VA Clinic

@eselkin
Copy link
Contributor Author

eselkin commented Oct 8, 2024

So the Manila VA System page needs to be published -> archived once only. It's just so that it gets picked up for the Blue box about social links for the VAMC facility page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants