Setting up error pages

LIVE SITES:

- cd /var/www/server/<yoursite>.org/web/error/
- rsync -av /var/www/server/landmasters.com/web/error/* .
  (You may at this point rarely receive an error of being unable to copy the files. This usually means
   the permissions for the /web directory were not properly set during the server/wordpress setup. 
   A simple "sudo chmod -R g+rw web" in the site's root directory should resolve this.)

- Go to the site. In header and footer, check for phone number and logo. Find out logo location and filetype extension. 
  (open image in new tab works well in chrome)
- cp that logo file into current dir (error) in the terminal, name it "logo.png" or .jpg, .tif, etc.
  (If the logo is white, or only works on its background: grab a screenshot -> rsync new file from local onto eleusis )
  (e.g. rsync newlogo.png laury@eleusis:/var/www/server/landmasters.com/web/error/logo.png)
  (If no logo in header or footer and nothing else that acts like it: ¯\_(ツ)_/¯ )

- Edit 404.html -> replace site both urls with correct ones.
- Change 404.html logo reference to match the right extension (.jpg, .png)
  (If there is no logo, comment out the img tag)
- Save/close 404.html
- Edit 504.html -> replace phone number. Change logo filetype extension as needed.
  (If there is no logo, comment out the img tag)
  (If the site has no phone number, just remove the number itself, leave the structure intact.)

- visit www.<yoursite>.org/asdjaskdjak. Check that both links (button and logo), as well as the logo image, are correct

- run this: cp 504.html 503.html && cp 404.html 403.html && sed -i 's/YOU LOOK LOST/ACCESS DENIED/g' 403.html && 
 sed -i "s/Don't worry, the link you clicked may be broken or the page may have been removed./You are not permitted to access the requested URL./g" 403.html

- Check a restricted location shows the correct 403 page. A good way to check this is grabbing the url of the logo, and removing just the image from the end
 (e.g: https://www.hpacamp.com/wp-content/themes/hpakidscamp/assets/)

DEV SITES:

These generally do not require custom error files as they are not publicly accessible. Otherwise, see above.
If we did set them up on devsites, then with dev URLs they'd have to be changed anyway, and with live URLs they're broken until live anyway.