Map prior URLs to new site

brucecrevensten commented 10 years ago

so, /data.php -> /data, etc.

cstephen commented 10 years ago

Looks like this is as simple as adding a bunch of lines like this to the end of Drupal's .htaccess file:

Redirect 301 /data.php /data

I'll start making a map of old URLs -> new URLs.

cstephen commented 10 years ago

Here's a big list of redirects. I've commented out the lines that we can't fill in yet. How do we want to incorporate these redirects? We can either:

Add this list to the existing .htaccess file in the Drupal root directory.
Move the current Drupal .htaccess file into our repository and symlink to it from the Drupal root directory, so our changes to .htaccess are version controlled.

I'm leaning towards the second option.

# About
Redirect 301    /about.php      /who/about
Redirect 301    /people.php     /who/people
# Redirect 301  /collaborators.php
# Redirect 301  /outreach.php
# Redirect 301  /faq.php
Redirect 301    /logos.php      /who/logos
Redirect 301    /sustainability.php /who/sustainability

# Tools and Data
# Redirect 301  /datamaps.php
# Redirect 301  /charts.php
# Redirect 301  /maps.php
Redirect 301    /analysis_tools.php /analyze
#Redirect 301   /data.php

# Methods
# Redirect 301  /methods.php
Redirect 301    /downscaling.php    /methods/downscaling
Redirect 301    /modeling.php       /methods/modeling
Redirect 301    /planning.php       /planning
Redirect 301    /uncertainty.php    /methods/uncertainty

# Projects
Redirect 301    /projects.php           /projects
Redirect 301    /project_page.php?projectid=8   /node/53
Redirect 301    /project_page.php?projectid=14  /node/60
Redirect 301    /project_page.php?projectid=19  /node/61
Redirect 301    /project_page.php?projectid=6   /node/62
Redirect 301    /project_page.php?projectid=27  /node/63
Redirect 301    /project_page.php?projectid=25  /node/64
Redirect 301    /project_page.php?projectid=12  /node/65
Redirect 301    /project_page.php?projectid=22  /node/66
Redirect 301    /project_page.php?projectid=11  /node/67
Redirect 301    /project_page.php?projectid=15  /node/68
Redirect 301    /project_page.php?projectid=5   /node/69
Redirect 301    /project_page.php?projectid=23  /node/70
Redirect 301    /project_page.php?projectid=7   /node/71
Redirect 301    /project_page.php?projectid=17  /node/73
Redirect 301    /project_page.php?projectid=26  /node/74
Redirect 301    /project_page.php?projectid=13  /node/75
Redirect 301    /project_page.php?projectid=1   /node/76
Redirect 301    /project_page.php?projectid=3   /node/77
Redirect 301    /project_page.php?projectid=21  /node/78
Redirect 301    /project_page.php?projectid=10  /node/79
Redirect 301    /project_page.php?projectid=16  /node/80
Redirect 301    /project_page.php?projectid=2   /node/81
Redirect 301    /project_page.php?projectid=20  /node/82
Redirect 301    /project_page.php?projectid=4   /node/83
Redirect 301    /project_page.php?projectid=9   /node/84
Redirect 301    /project_page.php?projectid=24  /node/85

# Resources
# Redirect 301  /resources.php
# Add existing resources?

carolynrosner commented 10 years ago

Have resolved all questions RE: how to map old pages to new ones in the spreadsheet https://docs.google.com/a/alaska.edu/spreadsheets/d/1C7XBNr7LZSWM8ImE638KBn9NhO3Kc_5QI1PEpv2UAH0/edit#gid=0

carolynrosner commented 10 years ago

Project URLs are no longer /node/x - should their actual names be listed instead?

cstephen commented 10 years ago

Generally using /node/x is safer since it doesn't change if we change the custom URL or path. So, I'd suggest sticking with /node/x for the redirects. Should I go ahead and copy your spreadsheet info into the .htaccess file?

carolynrosner commented 10 years ago

Oh sure - that'd be great, thanks. Sounds good re: /node/x.

On Wed, Jul 9, 2014 at 11:30 AM, cstephen notifications@github.com wrote:

Generally using /node/x is safer since it doesn't change if we change the custom URL or path. So, I'd suggest sticking with /node/x for the redirects. Should I go ahead and copy your spreadsheet info into the .htaccess file?

— Reply to this email directly or view it on GitHub https://github.com/ua-snap/snap-drupal/issues/13#issuecomment-48515031.

Carolyn

Carolyn Rosner Designer + Science Communicator Scenarios Network for Alaska & Arctic Planning http://www.snap.uaf.edu/ University of Alaska Fairbanks Fairbanks AK 99701 775-343-6481

cstephen commented 10 years ago

The .htaccess file has been updated and merged, and I've pulled this down onto cerberus and set up a symbolic link to the new version controlled .htaccess file:

$ ls -la /var/www/snap/.htaccess 
lrwxrwxrwx. 1 drupal drupal 24 Jul  9 13:38 /var/www/snap/.htaccess -> sites/all/misc/.htaccess

I think this warrants an addition to the README. I'll do that next.

carolynrosner commented 10 years ago

Closing this, because Craig completed the week of 7/8.

ua-snap / snap-drupal

Map prior URLs to new site #13