Where to find the footer CDN to use?

Hi @joseph.olstad i have the same question about this value.

Possibly from here?

Governance details: https://design.canada.ca/common-design-patterns/site-footer.html
CODE template references: https://wet-boew.github.io/GCWeb/sites/footers/footers-en.html

Those two links didn't have any CDN values?

Canada.ca doesn't supply a CDN for the footer, the only one I know about is StatsCan, but their footer links are slightly modified and do not align with Canada.ca. The footer CDN option has been around for a while now, I believe it was implemented when WxT was on D8.

ok, hmm, confusing, maybe I was asking the wrong question, there was some new functionality mentioned here:

#3335298: Update GCWeb footer structure with new global footer design →

For some reason I thought it was related to a cdn that brought this in?

Isn't this to replace the big Menu at the top? IF so, which cdn if any to use?

maybe there's a content import script that needs to run for new menu links? Is this intended to be menus from our Drupal CMS? Or brought in from elsewhere?

The new footer menu links are brought in via migration (gcweb_menu_link, gcweb_menu_link_translation). Only the main menu has a CDN option for Canada.ca. The new footer menus and blocks are brought in via drupal/wxt_bootstrap, and new migration config from wxt_ext_migration module.

@smulvih2 , ok , I'm going through the migrations

I foudn this one:

/admin/structure/migrate/manage/gcweb/migrations/gcweb_menu_link/execute

rolled it back, re-imported, gave the same old links.

I am still searching for the new links.

deleted our twig for this so the links show up and disappear when I rollback and re-import the above migration. The only one that I see that looks correct is the gcweb_menu_link migration...?

@joseph, since the migration scripts are actually config, you will need to import the new scripts or what I did was uninstall the wxt_ext_migration module, then enable it again to get the new scripts. This will throw error on install due to config already existing (not using enforced key), so just drush cdel the migration configs it complains about and you should have the new links ready to import.

I have added the enforced key to all migration scripts, so in the future the error on install for wxt_ext_migration will not occur.

ok makes sense, so it's basically working for vanilla installs but since there's no hook updates we just need to uninstall and re-install wxt_ext_migrations and delete the migration configs it complains about.

Yes exactly. Another option is to import the migration configs via drush or Config Sync Import UI, just need the two update scripts (gcweb_menu_link, gcweb_menu_link_translation).