Sierra Archive Obs request

[rustynwac]

Sierra was asking if we can add a link in the observations navigation to link to pre-AFP observations. Adding sub-nav items there is not possilbe. Ultimately we'd like to load them into the AFP. For now (and maybe awhile) we need an alternative solution.

Pointing to this URL: https://archive.sierraavalanchecenter.org/observations-archive

[busbyk]

@andyanderso How is the observation archive stored/built in your archive WordPress site? My concern is that users will navigate to https://archive.sierraavalanchecenter.org/observations-archive, not notice the difference between that site and the new one and start clicking around on old pages, experiencing potentially broken widgets like the forecast widget and outdated information.

Ideally, we could move the observations archive over to AvyWeb.

If it's custom HTML we could use GenericEmbedBlocks potentially. If it's custom .php then we might be able to make that work too. If it's integrated into WordPress with db calls then that's harder.

Even if we could just render that page in an iframe without the header that would be better.

I can help explore this but I don't have access to the WordPress site.

[andyanderso]

Thanks @busbyk - The old site is a Drupal 7 site. I think the best solution is to get the all the old obs and media into the afp platform, but it seems like that will take time.

For now we could easily have all the links point to the avy-web site or we could pull all the decoration and just iframe in the archived obs pages.

I already hid all the menus and stuff and created a page in our avy-web:
https://www.sierraavalanchecenter.org/observations-archive

I just need to allow for iframing now.

I am happy to give you access to the old site and database if you think you could help migrate stuff :)

[busbyk]

@andyanderso

I already hid all the menus and stuff and created a page in our avy-web: https://www.sierraavalanchecenter.org/observations-archive

I just need to allow for iframing now.

That's perfect. Hiding the header and navigation and iframing that page like you've done seems like the best immediate solution.

The reason that page isn't loading in the iframe is because of the Content-Security-Policy header on archive.sierraavalanchecenter.org. We'll need to update that. We'll also need to remove the X-Frame-Options header that Drupal 7 sets by default, since that can block iframes too.

Do you have access to the .htaccess file (an Apache config file) on the archive site?

If yes, you could add:

<IfModule mod_headers.c>
  Header set Content-Security-Policy "frame-ancestors 'self' https://www.sierraavalanchecenter.org https://sierraavalanchecenter.org"
  Header unset X-Frame-Options
</IfModule>

If you already have a <IfModule mod_headers.c> section, just add these two lines to the existing one:

Header set Content-Security-Policy "frame-ancestors 'self' https://www.sierraavalanchecenter.org https://sierraavalanchecenter.org"
Header unset X-Frame-Options

[andyanderso]

Archived server updated. The iframe seems to be working:
https://www.sierraavalanchecenter.org/observations-archive

We can add this to the menu.

[andyanderso]

@busbyk do you need anything else from me to get this in the obs nav menu?

[busbyk]

@andyanderso sweet looks good.

I think you should remove these two buttons though because they navigate within the iframe:

i.e. if I click current observations I get:

If you want those links I suggest using ButtonBlocks for those. I added those and saved as draft:

As I was creating that I realized that we don't have a way to have several buttons in a row (i.e. next to each other) with the way we've set up blocks. Discussing internally but I'll get an issue opened for that.

As far as getting this into the navigation, we can't just add this because the observations tab of the navigation is hardcoded. This was a decision made back during the fixed navigation discussion. But we've talked about updating that to use references to built-in pages so we could change things per center if needed for cases like this. So we're going to move forward with that but we have a few other things in progress so I'll keep you posted on timing.