Wordpress Site Go Live Checklist

From GLMWiki
Jump to: navigation, search

Quick checklist

pre go live checklist:
[ ] site is created on production server and php works for the site
[ ] site is added to the bandwidth database by name (ask Brian)
[ ] ssl cert is installed if needed

go live list:
[ ] export database
[ ] lockout client user
[ ] Move site files over to production server
[ ] Move database over to production server
[ ] verify defines for SSL and disallow file edit in wp_config.php
[ ] verify tracking pixels or google analytics code is brought into theme
[ ] all plugins that can be updated are updated
[ ] verify client user has correct permissions
[ ] all pages with nextgen photo or video galleries are working and set to correct template.
[ ] settings for the nextgen are correct
[ ] old stats are moved to new site
[ ] Check the site as a nonpriv user ( not logged in)

Old Sites:
[ ] Update .htaccess so client can get to it by IP address.
[ ] Update site with robots.txt file to keep search engines out

Communicator:
[ ] If site has mailchimp, constant contact or streamsend we need to set the forms up for sending data to it.

Contacts:
[ ] If we have an old contact database then export two files and save it client folder on aserv2
 [ ] all contacts export file
 [ ] all mail_ok flagged contacts export file

OpenSearch:
[ ] If site has the search plugin we need to make sure it has opensearchserver.ignore class setup in the theme.
[ ] Setup site on opensearch server

Additional Plugins:
[ ] Advanced Google Universal Analytics -StefanoAl (if need for the google analytics account - tracking code)
[ ] bandwidth plugin
[ ] seo-redirection-premium

Gravity Forms:
[ ] If site has a gravity form, that is linked with payment gateway, we need to setup reCAPTCHA on form.

Woocommerce:
[ ] Email address updated
[ ] Payment Processing. Set for production mode with production credentials.
[ ] Test mode or sandbox mode is turned off.

Registrations:
[ ] Payment Processor account exists
[ ] Payment Processor has been selected and credentials entered
[ ] Payment Processor has been set to Production mode

DNS Update:
[ ] Have Brian update dns records

Wrap-up:
[ ] Finally after the dns has been updated do a final check of the website.
[ ] Notify Anthony D. that the site is live.
[ ] Check the error pages

Grab copy of the the mysql database for the site.

Creds are in wp-config.php 

mysqldump -u [username] -p[password] [database_name] > [database_name].sql

Using WP-CLI 

wp db export ~/{sitename}.sql

Lock out client user account

Edit client user accounts and set to 'no role'

This may not work if they have woocommerce installed. Trying to update a user when woo is install requires that the address information be completed. Verify with Charis that the client will not be going into the site and making edits if this is the case.

All wp sites

This should be in the wp-config.php file for the site. 

define('DISALLOW_FILE_EDIT', true);
if (   isset( $_SERVER['HTTP_X_FORWARDED_PROTO'] ) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') {
    $_SERVER['HTTPS'] = 'on';
}

WooCommerce

  • E-Mail Addresses 
 Check main WooCommerce "From" Email Address in "WooCommerce" -> "Settings" -> "Emails" -> "Email Options".
 If any E-Mail messages to the shop administrator go to someone other than the main "WordPress" E-Mail contact address, 
 add them in the various E-Mail types tabs on the same page.


  • Payment Processing 
 Check if any payment processing requires production credentials.
 Check all active payment processing to make sure they are set for production.
 Check that all E-Mail address settings for any payment processor are set for production.
  • Setup 'WP reCaptcha Integration' Plugin
  • See setup for reCaptcha instructions on how to get the keys
  • Turn this on only for woocommerce checkout

get old tracking pixels (only for our old sites)

Check with the old sites template to make sure that any tracking pixels are carried over to the new theme.

Release Theme in git flow

Make sure that the theme for the site has been pushed to a release.

(do a git pull first on both your master and develop branches) 

git flow release start {release}
  • bump the version # in style.css
  • update gruntfile to use compressed and no css map

Run grunt to compress the style sheet 

git flow release finish {release}
git push --all
git push --tags

Move site to norax

On norax use rsync to copy dev70 files (in the /var/www/server/{sitename} directory) 

sudo rsync -av {dev70 or dev55}:/var/www/server/{sitename}.gaslightmedia.com/web/ web

Fix any file Permissions

inside the web directory 

sudo chown -R {webid}.client2 .
sudo chmod -R g+rw .
find . -type d -perm /g=x ! -perm /g=s -exec sudo chmod g+s '{}' \;
  • Set all plugins to master branch

Update ispconfig Settings

open the ispconfig dashboard
click Sites
select the website
click the Statistics
Do not Enter a password (leave blank)
select awstats
save

 [] Setup Stats (Awstats leave password blank)
 [] Setup Backups (daily 2 exclude web/* )
 [] Setup Options(tab) the Wordpress directives (may already be done)

Verify Wordpress directives 

client_max_body_size 48M;

location / {
    try_files $uri $uri/ /index.php?$args;
}
# Cache static files for as long as possible
location ~*.(ogg|ogv|svg|svgz|eot|otf|woff|mp4|ttf|css|rss|atom|js|jpg|jpeg|gif|png|webp|ico|zip|tgz|gz|rar|bz2|doc|xls|exe|ppt|tar|mid|midi|wav|bmp|rtf)$ {
    expires max;
    log_not_found off;
    access_log off;
}

# Add trailing slash to */wp-admin requests.
rewrite /admin$ $scheme://$host$uri/ permanent;

Update & Restore the Database (production)

On norax the dbusers and dbnames from angelia cannot be reliably used. Need to use new ones. 

 [] create a new database user (use sitename c2{sitename})
 [] create a new database for the site (use sitename c2{sitename})
 [] edit the wp-config.php on production server to new dbname and user

Copy over the sql dump file to the web directory of the livesite 

 - wp db import exportedfile.sql
 - wp search-replace 'http://{sitename}.gaslightmedia.com' 'https://www.{sitename}.com' --all-tables
 - wp search-replace '{sitename}.gaslightmedia.com' 'www.{sitename}.com' --all-tables
 - wp search-replace '{oldWeb###}' '{newWeb###}' --all-tables

Avata theme style and script files in uploads

grep the dev url on the wp-content/uploads directory and replace any dev url with live url

Sample grep: 

grep -rl 'turkeyville.gaslightmedia.com' ./ | xargs sed -i 's/turkeyville.gaslightmedia.com/www.turkeyville.com/g'

Setup your hosts file with ip address

66.129.42.{newip} www.{newsite}.{com,org,net} {newsite}.{com,org,net}

You can get the ip address from ispconfig setting for the site.

Move the index.html

mv index.html index.save.html

Setup Robots file

The robots.txt file in the main web directory needs to be linked from /var/www/robots.txt 

ln -s /var/www/robots.txt robots.txt (inside the web directory)

Wordpress updates

[] update the emails and subject lines in the Forms Notifications. No form should have {admin_email} or the default as to. Setting_up_GravityForms_notifications
[] create release for the theme folder
[] ***** turn off site restriction (settings > reading > Allow search engines to index this site *****
[] Pingbacks and comments need to be disallowed unless specifically indicated otherwise.
[] No WP bar should be visible for client (can change in heir profile
[] Make sure the site is not still called DEV -in the tile (or anywhere, really)

Update pages with NextGen Galleries

from the wordpress mysql database (wp db cli, in web directory) 

SELECT ID,post_title from glm_posts WHERE post_content like '%ngg_%' and post_type = 'page' and post_status = 'publish';

Update emails for Pending Event Coupons and Packages

Update client email so they get notified of: 

[ ] Pending Events
[ ] Pending Packages
[ ] Pending Coupons

Should use forms@websiteurl for the from address.

Install/Setup PiWik Plugin

Wordpress Piwik Setup Checklist NOT FOR QUICKSITES

Move old Stats folders over (old sites)

Documentation is in Tech on Aserv2 > Systems Documentation / Procedures / Moving Awstats to Angelia.odt

Awstats can be taken from the old site from the admin/logs/history directory. Need to cp each folders index.html page to awsindex.html 

rsync -av ws0:/var/www/server/oldsite.com/admin/logs/history/ oldsite

You can rsync the folders from the old site. After you copy them remove the index file from the History directory. You should only have directories from the history folder. Each directory will be named like 2014-12 or 2009-01

I made a script to go though each of the directory and copy the files. To be run from the history folder you rsynced over. 

#!/bin/bash
for dir in $(find * -type d);
do
    cp "$dir/index.html" "$dir/awsindex.html"
done

You can copy the files to your local machine and copy over the index files then copy the files onto norax in web/history directory. Then just copy over all directories from their into the stats directory. Make sure to update the file owner so then can be read by the site.

You can use rsync 

rsync -av oldsite/ norax:/var/www/server/sitename.com/web/stats

this will copy all folders in history and put them into the stats directory.

Client user setup

Deactivate any plugins not needed by the site. This includes the prototype plugin that is only used on development sites.

Verify that the client user can get to and use their admin to view edit pages and post 
get to form entries, export them

gravity form:
gravityforms_delete_entries
gravityforms_edit_entries
gravityforms_edit_entry_notes
gravityforms_export_entries
gravityforms_view_entries
gravityforms_view_entry_notes

next gen:
NextGEN Attach Interface
NextGEN Edit album
NextGEN Gallery overview
NextGEN Manage gallery
NextGEN Manage others gallery
NextGEN Manage tags
NextGEN Upload images
NextGEN Use TinyMCE


Glm Members:
Add an additional role called GLM Members Manager to the users that need access to all members.


Glm Client Info:
glmclientinfo_edit_client

old site

[ ] Make sure we can get to the old site by ip address
[ ] Uncomment the part in .htaccess which is forcing the www part.
This will probably look like these two lines:
 RewriteCond %{HTTP_HOST} !^(.*)\.harborpointassociation\.com$ [NC]
 RewriteRule ^(.*)$ http://www.harborpointassociation.com/$1 [R=301,L]

[ ] Add robots.txt file

robots.txt file 

User-agent: *
Disallow: /

Google Maps JavaScript API Keys

NOTE: Required for any GLM Associate install that does front-end mapping.

NOTE: Can be ignored for any site using Leaflet for front-end mapping.

For each site...

  • Next to "Google APIs" there's a picklist with "My Project" (or something) - Select "Create a Project"
  • Enter the name of the project (i.e. the Website name)
  • Click "Create" (this may take some time, just wait)
  • When that's done, the page will re-display with the "Library" list
  • Click "Credentials" in the left menu then click "Create credentials" then select "API key"
  • Copy the API key then select "Restrict key"
  • Optionally give the key a Name
  • Select "HTTP referrers (web sites) and enter the site URL as shown in the example and click "Save" 
 *.gaslightmedia.com/*
 *.{websiteurl}/*
  • Click on "Library" at left then "+ ENABLE API" at top
  • Click on "Google Maps JavaScript API" under "Google Maps APIs"
  • Click "ENABLE" at top 
 * If you get an "empty referer blocked" error, you will just have to wait a while before trying again
  • Enter key in GLM Associate at "Management" -> "Misc. Settings" -> "Google Maps API Key:" field.

Also need to enable the google maps geocoding API.

Event Calendar PDF graphic

[ ] Make sure the site has graphic for event pdf if events are installed.

If it does not then create task for Ian to create one.

SSL

SSL (if site has secure pages - which is should) 

[ ] Check that the entire page has secure elements. css, javascript, fonts, favicons

Leads (old sites)

[ ] Export all old leads to files (all and mail_ok) and save on 5-WebClients under the client folder.
[ ] Make sure that any communicator accounts have been setup.
  [ ] Stream Send
  [ ] MailChimp
  [ ] Constant Contact

Add a site to OpenSearchServer (if site has glmAssoc search plugin)

Note that you may have to wait for DNS to propagate to the OSS server. The first step below is to verify that this has happened.

  • Log into oss.gaslightmedia.com by ssh and make sure that the site hostname is resolving with the expected IP address (use "host {site}" to get that). If not, wait for DNS to propagate to IS0.
  • Log into the OpenSearchServer management interface at "http://oss2.gaslightmedia.com:9090".
  • Go to "Indices:..." (might be "Index" with an already selected index) tab at the top left
  • If the old site has been indexed by the OpenSearchServer - Remove the old site from its index 
 * Select that index the old site is in
 * Select "Crawler" tab at the top
 * Check the box next to the site in the list below and click the "delete" list at the bottom (NOT THE "delete all" link!)
  • Select the desired Index (Index2 currently for norax sites or Index_SSL for ssl ones)
  • Select the "Crawler" tab at the top
  • Select the "Pattern list" tab
  • Enter the base URL in the edit window, end with "/*"
  • Select "Add"

Updated process to add a site to index_SSL

  • Enter site into the "Pattern List" page
  • Enter site url into manual crawl
  • Enter the site into URL Browser to make sure it has the page. (should be unfetched so far)
  • Stop the crawler and goto URL Browser and tell it to fetch first
  • Restart the crawler (let it run for a minute)
  • Stop the Crawler and goto URL Browser (should see more urls now)
  • Tell it to fetch first
  • Restart the crawler
  • After a while test the search results. It should have results pretty quickly now.


Exclusion Review - Need to review all areas that are not to be indexed by the OpenSearchServer. If an area to be excluded is not covered by one of the entries below, the site either needs to be changed to comply with these standard exclusions or a new exclusion needs to be added to the OpenSearchServer.

ID's excluded 

 gallery
 footer
 page-header
 left-off-canvas-menu
 head-img
 reservation
 breadcrumbs
 copyright
 wu-copyright
 wu-wrapper
 mid
 blog-feed-front
 footer_address

HTML tags excluded 

 head
 header
 footer
 form
 nav
 aside

If there are non-standard tags with contents that need to be excluded the tag can be excluded by adding the following class. 

 opensearchserver.ignore

Use the following procedure to update or add excluded IDs and HTML tags.

  • Click "Schema" tab
  • Click "Parser list" sub-tab
  • Click "Edit" to the right of "HTML parser" line.
  • At the bottom of the page edit the "XPATH Exclusions" to update or add the desired exclusion.
  • When done, click "Save" at the bottom of the page.

Forcing OpenSearchServer to Re-Index a Site

If it becomes necessary to re-index (re-crawl) a site due to areas that should be excluded not having been properly excluded, you can follow the proceedure below.

  • Log into OpenSearchServer
  • Select the desired index (normally INDEX_SSL) - all sites will be https now
  • Select the "Crawler" tab then "Crawl process" sub-tab
  • Click the "Running - Click to stop" button and wait for the sever to stop crawling.
  • Select the "URL browser" sub-tab
  • Enter the base URL of the site in the "Url" input field. Use wildcard to specify entire site (i.e. "http://www.gaslightmedia.com/*").
  • Click the "Search" button and review the list of URLs produced to make sure you have your URL selection correct.
  • In the "Commands:" pick-list, select "Set selected URLs to Unfetched" then click the "Go" button.
  • Optionally (may be required) - In the "Commands:" pick-list, select "Delete selected URLs" then click the "Go" button.
  • When that is done, select the "Crawl process" tab again and click the "Not running - Click to run" button.
  • Just to make sure things get kicked off again, click on "Manual crawl", enter the URL for the base of the site (i.e. "http://www.gaslightmedia.com/"), then click the "Crawl" button.

This should start the OpenSearchServer re-crawling the specified site. It's also possible to crawl any specific part of a site by specifying the base URL to that area of the site followed by "/*", or to otherwise use wildcard characters to specify the desired URLs. Be sure to check your URL selection by reviewing the generated URL list.

Removing a url from opensearch

goto Index Index_SSL

goto the main Delete tab

Enter the query 

url:"{full url of page to delete}"

Click on 'Check' to see how many it finds Click on 'Delete'

IMPORTANT NOTE ON PAGE TITLES

The theme should have the title set in the meta-header template as 

   <title><?php wp_title();?></title>

And not have 

   add_theme_support( 'title-tag' );

Added to the theme.

This will prevent our event and member plugin from setting the titles on the event and member detail pages.

Also the Yoast plugin has an option to overwrite titles 'Force rewrite titles' which should be disabled.

Install and Setup Bandwidth Reporting Plugin (all sites)

Install the bandwidth reporting plugin. Only the Stand Alone plugin is used for this, retrieved using: 

git clone ssh://git@bitbucket.gaslightmedia.com:7999/plug/glm-serverstats.git

All the parameters are now automatically taken care of.

Reset the serverstats transient for notifications 

wp transient delete ServerStatCacheUpdate

Install Additional Plugins (all sites)

For the seo we need to install and activate a paid plugin. Seo Redirection Premium. You can simply copy this from another website on the same server. So inside the plugin directory. 

cp -r /var/www/server/gaslightmedia.com/web/wp-content/plugins/seo-redirection-premium ./

Setup reCaptcha for all gravity forms

login to google with Gaslight account GLM Front Office (creds in glmdb)

https://www.google.com/recaptcha/admin#list

Register a new site if it's not there. Use reCAPTCHA V2 (v2 invisible)

Enter the domains. You can put both dev55 and the live url's here (one per line)

Accept the reCAPTCHA Terms of Service leave Send alerts turned on

Copy the Site key and the Secret Key to the setting in Gravity Forms.

Add the CAPTCHA field to the form.

Remove the label for the field on the form so it doesn't show Captcha. the captcha actually shows on the page but it is floating on the footer to the right. So the label would output all by itself.

Setup Super Cache Plugin

Add Super Cache plugin to website

Activate

Enable caching in settings

Update the DNS

[ ] Have Brian update the DNS

Set up mainwp for live site

NOT USING THIS PLUGIN ANYMORE

Set up error pages

Setting_up_error_pages

Go over the site

[ ] Let Anthony Dwyer know that the site is live. [ ] Verify that the dev site restriction plugin is activated and setup so there's no way the site can be indexed in search engines.

Retrieved from "https://wiki.gaslightmedia.com/index.php?title=Wordpress_Site_Go_Live_Checklist&oldid=8439"