ISPConfig

This step is most likely going to be performed by Networking.

Development Server Setup

[] Create the domain on ispConfig

- Go to https://dev55.gaslightmedia.com:8080
- Add new website - client is GaslightMedia
- Domain is websitename.gaslightmedia.com - no www!
- Auto-subdomain to None
- Check "SSL" (do not check "SSI")
- SAVE
- In the Websites menu, find the website by the Domain. Get back into the website editing screen. Go to the Options tab, and add the following to nginx directives

client_max_body_size 48M;

location / {
    try_files $uri $uri/ /index.php?$args;
}
location ~* \.(js|css|png|jpg|jpeg|gif|ico)$ {
    expires max;
}

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

- Save again, and go back again, to the SSL tab
- Fill in State (Michigan), Locality (Petoskey), Organisation (Gaslight Media), Org Unit (1), and Country (United States). Skip the rest of the fields except the last one, and set that to "Create Certificate"
- Save again, and the SSL will begin to be processed

Production Server Setup

- Go to https://eleusis.gaslightmedia.com:8080
- Add new website - client is GaslightMedia
- Go into the Eleusis IP address document on Aserv > 1-Gaslight Stuff > 0-Projects. Use the next available IP and update said file with this site
- Domain is websitename.com or .org or whatever, but no www. prefix!
- Auto-subdomain to www.
- SAVE
- Enter the same Nginx directives as for dev55. 
- Do not set up SSL at this point

After the site is created for Eleusis test that the php is working correctly by creating a php.php file with:

<?php phpinfo();?>

This will make sure that the php-fpm service is connecting with nginx. If it is not functioning correctly you'll probably get a bad gateway error message.

Fix Permissions

[] Fix permissions on web directory of each server you've set up

sudo chmod g+rws web

! When setting up an Eleusis site in conjunction with a dev55 site, you should stop here with any work performed on the production site, because the dev55 copy will be transferred over when the time comes to bring the site live. You don't need to waste any time setting up WordPress installations for these production sites if you just needed to create a server.

Install WordPress

[]Install wordpress using ispconfig

APS Installer > Available Packages > Search for "Wordpress"
Click newest version > "Install this package"
Install Location: <site to install>
Admin login: glmdev
password: <our default> -- you will get no confirmation!!!
Administrator's email: dev@gaslightmedia.com
Site Name: <site to install>

Refresh Installed Packages after ~60s, should say "Installation_success"

GLMDB

o Go into GLMDB for this client and add the necessary credentials

Site Configuration

This step should be performed after Networking has created the VS, and starts in the development server's Web directory

Folder permissions

Fix file permissions on web directory

In site top directory: 
sudo chmod -R g+rw web
Then in /web directory:
find . -type d -perm /g=x ! -perm /g=s -exec sudo chmod g+s '{}' \;

Start setupwpsite.sh script

FROM THIS POINT ON YOU CAN INSTEAD RUN setupwpsite.sh ON DEV55 OR DEV70, but ONLY if you are certain WP CLI is functional for you.

A good way to test this is trying the command "wp option get page_on_front". If it does not return a number (most likely 2), but complains about a missing function, do not attempt to run the script before WP CLI is set up correctly.

This script will work in the site's Web directory and will eliminate the following steps: "Editing WP-Config.php", "Running the Wp-Setup script", "Initial Wordpress Setup", "Common Plugins", "Themes", "Install GLM Plugins"

CLICK HERE to get to the end of everything covered by the setupwpsite.sh script. When there, be sure not to skip instructions on what to do after running the script.

Editing WP-Config.php

(this step is skipped if the wpsetupsite.sh script is ran)

Edit wp-config.php (located in web/). Grab the DB_NAME, DB_USER and DB_PASSWORD values while you're in there.

$table_prefix = 'glm_';

This changes default table_prefix to glm_ and allows all new pages to start using that prefix. Now you have to change the ones already set up with wp_

Add this to wp-config.php as well, with the defines Above the part that says " /* That's all, stop editing! Happy blogging. */

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

Running the Wp-Setup script

(this step is skipped if the wpsetupsite.sh script is ran)

Using WP-Setup to update the options,table names and setup our Gaslight User Accounts. If you don't have it yet: clone git@cvs2:prog/Grunt/WP-Setup. This should already exist on your home folder on dev55. CD into the wp-setup folder. Edit the (Gruntfile.coffee) following lines to setup the database credentials.

There are two areas:
mysqlrunfile: connection options
backup4mysql: options

change EVERY instance of the user, password and database

Then run

grunt wpSetup

At this point, sign into the site and make sure it's working, and all the webteam users are added.

Initial WordPress Setup

(this step is skipped if the wpsetupsite.sh script is ran)

Head into wordpress using sitename.gaslightmedia.com/wp-admin

[] update WordPress if needed
[] update any WordPress themes if needed
[] remove the WP Multibyte Patch
[] Create a new page called "News" or "Blog"
[] Settings > General > tagline to something better ("Website for ...")
[] export pages if needed and change any dev.gaslightmedia.com references to site url.
[] set Settings > Reading > front page to static: Front page
[] set Settings > Reading > blog page static to "News" or "Blog"
[] set Settings > Permalinks > Common Settings to "Post name"
[] import pages if needed
[] import options if needed
[] under Settings > Discussion 
    [] uncheck All of the settings at "Default article settings"
    [] uncheck both settings at "E-mail me whenever"
    [] Check "Comment author must fill out name and email
    [] Check "Comment must be manually approved"

If for some reason you did not run the WP-Setup script, the following items will also have to be done. Otherwise, proceed to the next section.
[]*setup users  (edit every user)
  []*set nickname for each user
  []*uncheck Show Toolbar when viewing site
[]*set Settings > General > timezone to detroit 
[]*set Settings > General > start of week to Sunday
[]*make sure there are no pages except one called "Front page", and only one "Hello world" post

Common Plugins

(this step is skipped if the wpsetupsite.sh script is ran)

Common Plugins

** Rather than doing this manually, it will be much quicker to do this through
 a script. Check [[WP Scripts]] if you do not already have one. **

- WP Plugins installed through the Wordpress installer:
 Advanced excerpt (by Delicious Brains)
 Breadcrumb Navxt (by John Havlik)
 Captcha By simplywordpress NOT Google Captcha (reCAPTCHA or BestWebSoft)
 CMS tree page view (Pär Thernström)
 EWWW Image Optimizer (Exactly WWW)
 Login LockDown (by Michael VanDeMar)
 MainWP Child (by MainWP)
 Media Category Management (by DeBAAT)
 Metaslider (by Team Updraft)
 Nextgen Gallery (by Imagely)
-  Nextgen custom fields (by Shaun Alberts) (this exact plugin name! There are ones very similar)
 Print, PDF, Email by PrintFriendly (by Print, PDF, Email by PrintFriendly) (yep, that's the exact name)
 Restricted Site Access (by Jake Goldman, 10up, Oomph)
 TinyMCE Advanced (by Andrew Ozz)
 User role editor (by Vladimir Garagulya)
 Wordpress importer (by wordpressdotorg)
 WP Options Importer (by Matthew Boynes)
 Yoast SEO (by Team Yoast)
 WP Security Audit Log (by WP White Security)

-- Plugins installed Manually
 Gravity Forms (get from Aserv2 > 1-Gaslight Stuff > 0-Projects > Plugin Downloads)
   - This plugin may need to be updated, in which case a new version may have to be downloaded. Have a look at WebClients > 1-Gaslight Stuff > 0-Projects > 1-Plugin Licenses and Websites.ods to see where this can be done

 Activate these up-to-date plugins. Remember to hold off in the first round on activating plugins that require others to be active (like NGG Custom Fields).

Delete these plugins

 Hello Dolly
 WP Multibyte Patch

- Optional plugin if you want to make every part of your WP admin work more tolerable

Jarvis

Themes

(this step is skipped if the wpsetupsite.sh script is ran)

Delete all default themes except for the latest "twenty{something}" one.

Also make sure all plugins and themes are updated.

Install GLM Plugins

(this step is skipped if the wpsetupsite.sh script is ran)

GLM Plugins Installed:
git clone git@cvs2:WP-Plugins/Gaslightify.git
git clone git@cvs2:WP-Plugins/glm-client-info.git
git clone git@cvs2:WP-Plugins/glm-blocks.git
git clone git@cvs2:WP-Plugins/glm-support-form.git
git clone git@cvs2:WP-Plugins/GlmPrototypes.git

End of setupwpsite.sh script

From this point on you have to configure things manually again (for now...). Here will be listed any important temporary fixes for flaws in the script (if any):

o (may no longer be necessary) Using WP CLI: wp option update admin_email dev@gaslightmedia.com

o Until GLM Client Info is fixed, the script will automatically disable it after install. You will need to enable it manually. (2020-9-1)

o Settings > General > Site Title, Tagline

o if there are any GLM Associate plugins to be installed, do so at this point, before reassigning the task to a project manager. This will ensure the necessary capabilities are attributable.

Plugin Configuration

WP Activity Log

(previously WP Security Audit Log)

((these settings are currently being tested in the setup script, remove this setting if this proves functional - 2020-9-1))

- Settings > General > "Who can change the plugin settings?" All Administrators
- Settings > General > "Is your website running behind a firewall or reverse proxy?" Yes

Breadcrumbs NavXT

((these settings are currently being tested in the setup script, remove this setting if this proves functional - 2020-9-1))

Go to Settings > Breadcrumb NavXT

- Breadcrumb Separator (empty)

- Home Breadcrumb: Home Template - replace "Go to %title%" with "Go Home"
- Home Breadcrumb: Home Template (Unlinked) - replace "%title%" with "Home"
- Mainsite Breadcrumb: Main Site Home Template - replace "Go to %title%" with "Go Home"
- Mainsite Breadcrumb: Main Site Home Template (Unlinked) - replace "%title%" with "Home"

If the breadcrumb styles are incorrect, you may have to do the following
- in the breadcrumb settings, change the separator to: <span class="bcn-separator">></span>
- look at the styles set for these breadcrumbs in the cityofharborsprings theme

Gravity Forms

((these settings are currently being tested in the setup script, remove this setting if this proves functional - 2020-9-2))

[ ] Setup using the key 88d5659ef4ebfeae7c234b3b11cb35e0
[ ] Turn on Toolbox Menu

MainWP

(being phased out of usage, no longer part of setup script - 2020-9-1)

 
Get into Settings > MainWP Child.
Check "Require unique security ID". Hit Save Changes.
Copy the id.
Head to admin.gaslightmedia.com/wp-admin. Sites > Add New
Enter all the information. No need to change Certificate and SSL version or anything, but enter the HTTP username and password based on our default glmdev account.

Login Lockdown

((these settings are currently being tested in the setup script, remove this setting if this proves functional - 2020-9-1))

  "Settings" -> "Login LockDown"
  Max Login Retries = 5
  Lockout Invalid Usernames" = Set to Yes
  Show Credit Link = "No, do not display the credit link"
  Click "Update Settings"

Nextgen Images

With Gaslightify active, the menu item will be called "Gallery". Click it to open the submenu.

Click "Skip" if it asks you to help improve Nextgen by sending usage statistics.

- Other Options > Thumbnail Options > Default thumbnail dimensions: 220 x 190

- Other Options > Roles & Capabilities: Set every capability to "Editor" except "Change options" which should be set to Administrator

- Importing Nextgen images (Not Needed for New Fresh Site Installs)

!!! First go to Media > Settings and make sure the dimensions are the SAME as on Dev, or you'll be missing 
image resizings and will have to copy them over

Get the export from the database at dev.gaslightmedia.com site on ISPConfig for ngg_albums, ngg_galleries, 
and ngg_pictures
Edit those files to replace wp_8 with glm, and take out the /sites/8 part (the 8 here will be dependent on 
the ID for that site in dev.gaslightmedia.com multisite)
Import those into the database of the new site AFTER installing the nextgen plugin,
 in this order: albums, galleries, pictures.

Make sure all the gallery templates are set properly again, they'll still point to their old location 
(This might be more easily doable through the database?) - also set default templates for thumbnails (and 
any other used) in Gallery Settings to glmPhotos, and Compact Album template to GlmAlbums.

Print Friendly & PDF Settings

(not installed through script, ignore unless manually installed)

!!! You cannot currently save settings unless we activate pro/trial version
[] Goto the setting > Print Friendly & PDF and uncheck for pages.

User Role Editor

Set user role permissions for Editor for:
- Nextgen managing albums and galleries and uploading images (all but " NextGEN Change Options")
- UNSET Yoast SEO bulk edit permission

gravity forms:
- gravityforms_delete_entries
- gravityforms_edit_entries
- gravityforms_edit_entry_notes
- gravityforms_export_entries
- gravityforms_view_entries
- gravityforms_view_entry_notes

advanced ads (not installed through script, ignore unless manually installed):
- all of the associated capabilities

WooCommerce

(not installed through script, ignore unless manually installed)

Go to WooCommerce > Settings > Emails(tab) > Recipient(s) and change the recipient to the client's desired address.

Change the wordpress settings so that it's www.website.com and not website.com

Once finished, archive the site on dev.gaslightmedia.com so only super admins can see it.

Yoast SEO

Menu item is called SEO
- Get User Role Editor so that "seo bulk edit" can be disabled for Editors (if not performed above)
- Search Appearance >  find any instance of "Show SEO settings for [type]" under all the tabs, and click the "Hide" selector. Be sure to save changes.
  You will need to expand any section that isn't already expanded (like Pages under Content Types) and look for more selectors there.

Permissions (yep, again!)

Make sure that after all plugins are installed they are set to the correct user. By default they are set to the person who installed them. Set them to the correct web###. Also verify the group for all plugins is set to client2.

SSL/https

((these settings are currently being tested in the setup script, remove this setting if this proves functional - 2020-9-2))

- wp db export exportedfile.sql
- wp search-replace 'http://sitename.gaslightmedia.com' 'https://sitename.gaslightmedia.com' --all-tables

Avada

From <site>/web/ :

rsync -av /var/www/server/deerranch.gaslightmedia.com/web/wp-content/themes/Avada/ ./wp-content/themes/Avada/

OSS

- In the theme, change header.php and the search part file to where the action of the form has "site-search/" appended
- also change the name of the first input field to "query" instead of our regular "s"
- Clone and activate the plugin (git@cvs2:WP-Plugins/glm-member-db-search.git)
- In admin > glm Associate > Management > Search, the default index may be either index_1 or index_2, you'll need to try both.
- in that same location, change the site from www.gaslightmedia.com to the live site of the given client (as long as it is indexed). This has to start with "www".
- Make sure the existing site styling accommodates the new OSS results.
- Make sure the search results work by typing a common query like "Michigan"

And possibly a combination of the steps as laid out here http://wiki.gaslightmedia.com/index.php?title=Wordpress_Site_Go_Live_Checklist#Add_a_site_to_OpenSearchServer_.28if_site_has_glmAssoc_search_plugin.29

Client User/Credentials

This step is likely performed by a project manager

GLMDB

o Set up a Wordpress user for the client. They should be an Editor. Think of a sensible, secure password, and uncheck sending them an email.

o Add the client's credentials for their new site in GLMDB

Wordpress New Single Site Install Checklist

Contents

ISPConfig

Development Server Setup

Production Server Setup

Fix Permissions

Install WordPress

GLMDB

Site Configuration

Folder permissions

Start setupwpsite.sh script

Editing WP-Config.php

Running the Wp-Setup script

Initial WordPress Setup

Common Plugins

Themes

Install GLM Plugins

End of setupwpsite.sh script

Plugin Configuration

WP Activity Log

Breadcrumbs NavXT

Gravity Forms

MainWP

Login Lockdown

Nextgen Images

Print Friendly & PDF Settings

User Role Editor

WooCommerce

Yoast SEO

Permissions (yep, again!)

SSL/https

Avada

OSS

Client User/Credentials

GLMDB

Finished

Navigation menu

Search