W3-Jan-17-2025-v1

[w3creatives]

What's included

This PR resolves the following issues:

Priority: High

• Common errors clogging log #731
• Places holiday hours unable to use "Opening time" #748
• Content view: name in Updated column should show most-recent editor #773
• Time on French and English sides of Places showing up incorrectly #785
• Dates on Fre news releases are different order than on Eng #795
• On mobile: left-hand nav menu appears at top of page #798
• Add multi-step and Add chart buttons missing on French side #804
• Department field missing on French side of Places #810
• In the top nav menu on child pages, "Home" is going to the News search page #818
• Files exists in Media file folder after being replaced #819
• Filters on Fre search page are in Eng #827 (Repeated Jan-23-2025)
• On Places search, there's English text #828
• Editing Campground in French leads to "encountered unexpected error" #831 (Repeated Jan-23-2025)
• Jump points on pre-migration Campaign pages not linking #832
• Identifying pages in need of translation #833
• French places not editiable due to missing community value #837
• Newly created campaign translation leads to "unexpected error" (InvalidArgumentException: Invalid translation language) #852
• File delete operation is missing #821
• Update search views translations #787
• On mobile: categories are laid out in 3-column grid #812

Priority: Medium

• Campaign page design issues #675
• Campaign page "show logo at top of page" checkbox doesn't have effect #693
• Some roles cannot create/edit some basic pages due to missing/invalid editorial team #718
• Editing page leads to "encountered unexpected error" (InvalidArgumentException error) #746
• Campaign jump point icons (fontawesome?) not displaying #755
• Editable author information field missing from Fre side #781
• Blog: update fields text to French #841

Priority: Low

• URLs differ from D7 #727
• Admin > Content shows "Media" twice #741
• Document "updated at" doesn't need time component #745
• Expand text field size missing in French #764
• In-page alerts do not appear on LPL2 #800
• Event: bullet text is larger font size #826
• Hover, active, visited link colours #829
• Remove beige/gray background from title field on Topics page #830
• Eliminate duplication of "Search" at top of a search results page #842
• Search for Yukon.ca in Google results in "breadcrumb" appearing in results #845

Priority: Unknown

• Places: cannot edit page (editorial team not on Fre side) #817
• Website Encountered an Error displaying an event #834

Notes

This PR will also update the of Drupal core and some modules.

Dependencies changed (versions and patches), so install new ones.

Theme changes, so need to rebuild the theme.

Quite a few config changes.

Deployment instructions

1. backup DB
2. deploy code
3. install dependencies
4. update DB
5. import configuration
6. rebuild theme
7. Load a update-the-db URL (for Places: cannot edit page (editorial team not on Fre side) #817) and for - [ ] Some roles cannot create/edit some basic pages due to missing/invalid editorial team #718
   • /team_department_update
8. Cache rebuild drush cr

[w3creatives]

Hi @leeomara Could you please look into these 3 files with conflicts?

This file docroot/themes/custom/yukonca_glider/yukonca_glider.theme was updated on urgent request. - #818

[leeomara]

Some of these changes look like duplicates of what already landed in #main as part of #825.

[leeomara]

I need to re-deploy, to apply the changes that landed here since Jan 24.

[leeomara]

I've re-deployed to UAT.

[leeomara]

I think we need to revisit how we are using merge requests and branches. This merge request has been open for 3 weeks, has been deployed to UAT twice, and is still getting changes pushed to it.

Challenges I find with this current approach:

• it's hard to test against a moving target
• it's hard to know what has been deployed where
• it's hard to have confidence that we can merge/ship this branch to prod

I'm open to suggestions/discussion about this.

[w3creatives]

May I ask a couple of questions?

1. Did you last merge the code into UAT from main_w3_staging on Feb 4th, 2025?
2. And the issues are the related to the updates occurring after after your last merge?

FYI, we were initially assuming that main_w3_staging will be merged into main at some point and that was why; we took this approach. But if you want to revisit what was merged into main_w3_staging, then you can review these PRs:

https://github.com/ytgov/yukon-ca/pulls?q=is%3Apr+is%3Aclosed

Alternatively, we can resubmit the PR based on the pending issues if you can provide us date after which we should resubmit the updates.

Open to suggestions.

[leeomara]

UAT has been updated with this, up to 5aecd0d.

[leeomara]

Now that I pushed forward one commit to fix #804, as part of #859, this merge request now has a conflict to fix.