WordPress | Visser I/O

Configuring WordPress after installing OpenLiteSpeed on Google Cloud Platform

Bitnami is great, until it comes to updating the stack. I’m now using OpenLiteSpeed which gives me better control over updating the stack without having to regularly migrate to new instances.

Here’s my cheatsheet for setting up OpenLiteSpeed to run WordPress.

Run the openlitespeed-wordpress Marketplace installer
Assign a Static IP from VPC Network > External IP addresses
Turn off DNS routing on Cloudflare for the A record and the www C record
Update the A record to your allocated static external IP address

Connect via Google Cloud SDK Shell with your preferred SSH user

gcloud beta compute ssh --zone "us-west1-b" "[username]@[instance name]" --project "[project name]"

Complete the OpenLiteSpeed installer with Let’s Encrypt
Turn DNS routing on again in Cloudflare
Add your SSH user to the www-data user group
```
sudo usermod -a -G www-data [username]
```
Run the WordPress installer

That’s it!

Setting up a Cloudflare SSL certificate for Bitnami WordPress on Google Cloud Compute Engine

Bitnami WordPress on Google Cloud Compute Engine does not out of the box ship with SSL turned on, site owners need to secure communication to and from their website using SSL.

Here’s how to configure SSL using a free Cloudflare SSL certificate for Bitnami WordPress on Google Cloud Compute Engine.

Creating certificate files with Cloudflare

First we generate and download the SSL certificate files from Cloudflare.

1. Open up your site profile on Cloudflare.com
2. Switch to the Crypto tab
3. Within the Origin Certificates section click the Create Certificate button
4. Ensure the Let Cloudflare generate a private key and a CSR option is set to RSA
5. Click Next
6. With the Key format field set to PEM (Default) highlight and paste the contents of the Origin Certificate and Private Key blocks into separate new files on your Desktop:
  - Origin Certificate: server.crt
  - Private Key: server.key

Configuring Apache on your WordPress Bitnami instance

Now we connect with SSH to the hosting server; your Google Cloud Compute Engine instance. You can do this via the Google Cloud Platform > Compute Engine > VM Instances > Connect with SSH or with your preferred terminal client.
1. Open an SSH session to your Google Cloud Compute Engine instance
2. Navigate to the /opt/bitnami/apache2/conf/ directory with the following terminal command:
```
 cd /opt/bitnami/apache2/conf/
```
3. Delete or rename the existing server.crt and server.key files in this directory (I prefer to rename them to server.crt_legacy and server.key_legacy):
```
 sudo mv server.crt server.crt_legacy

 sudo mv server.key server.key_legacy
```
4. Create two new files in their place:
```
 sudo touch server.crt

 sudo touch server.key
```
5. With your preferred terminal text editor paste the contents of the two Cloudflare certificate files mentioned above into these new files on your hosting server
```
 sudo nano server.crt

 sudo nano server.key
```
6. Restart the Apache service
```
sudo /opt/bitnami/ctlscript.sh restart apache
```

Enable SSL within Cloudflare

Open up your site profile on Cloudflare.com
Switch to the Crypto tab
Change the SSL dropdown from Flexible to Full
Change the Always use HTTPS option to On
Change the Automatic HTTPS Rewrites option to On

That’s it!

Turning off PageSpeed and OPcache in Bitnami Apache for Google Cloud Platform

Here’s how to turn off the Google PageSpeed module within Apache and PHP’s OPCache functionality that is enabled by default within Bitnami instances on Google Cloud Platform.

1. Establish a terminal session to your Google Cloud Platform instance with your preferred terminal client (e.g. Putty).
2. Open up /opt/bitnami/apache2/conf/httpd.conf with your preferred file editor and find the following lines:Include conf/pagespeed_libraries.conf
  Include conf/pagespeed.conf
3. Comment them out to match the following lines:
  # Include conf/pagespeed.conf
  # Include conf/pagespeed_libraries.conf
4. Save changes and return to terminal prompt.
5. Open up /opt/bitnami/php/etc/php.ini with your preferred file editor and find the following line:opcache.enable=1
6. Comment it out and disable opcache.enable by matching the following lines:
  # opcache.enable=1
  opcache.enable=0
7. Save changes and return to terminal prompt.
8. Restart the Apache service with the following command:
  sudo /opt/bitnami/ctlscript.sh restart apache

That’s it 🙂

WordCamp Brisbane 2017: Extending WordPress and WooCommerce core

Source: Extending WordPress and WooCommerce core

Fixing Installation Failed message on Bitnami WordPress and Google Cloud Compute Engine

Getting WordPress installed on Google’s Cloud Compute Engine service is super easy using the Bitnami Launchpad for Google Cloud Platform, the gotcha is the default permissions set during installation mean you cannot use the WordPress Administration to update Theme’s, Plugins or WordPress core itself.

To set the file and directory permissions correctly you will need to connect via SSH to the container that your WordPress instance is installed on.

Here’s how to set the directory and file permissions correctly, split up into the different WordPress core directories:

WordPress base directory

sudo find /opt/bitnami/apps/wordpress/htdocs -type f -exec chmod 664 {} \;

sudo find /opt/bitnami/apps/wordpress/htdocs -type d -exec chmod 775 {} \;

sudo chown bitnami:daemon -R /opt/bitnami/apps/wordpress/htdocs

wp-admin

sudo find /opt/bitnami/apps/wordpress/htdocs/wp-admin -type f -exec chmod 664 {} \;

sudo find /opt/bitnami/apps/wordpress/htdocs/wp-admin -type d -exec chmod 775 {} \;

sudo chown bitnami:daemon -R /opt/bitnami/apps/wordpress/htdocs/wp-admin

wp-includes

sudo find /opt/bitnami/apps/wordpress/htdocs/wp-includes -type f -exec chmod 664 {} \;

sudo find /opt/bitnami/apps/wordpress/htdocs/wp-includes -type d -exec chmod 775 {} \;

sudo chown bitnami:daemon -R /opt/bitnami/apps/wordpress/htdocs/wp-includes

wp-content

sudo find /opt/bitnami/apps/wordpress/htdocs/wp-content -type f -exec chmod 664 {} \;

sudo find /opt/bitnami/apps/wordpress/htdocs/wp-content -type d -exec chmod 775 {} \;

sudo chown bitnami:daemon -R /opt/bitnami/apps/wordpress/htdocs/wp-content

That’s it!

Trends in persistent WordPress Administration notices

I’ve been helping out store owners in maintaining their stores for a little while now and the trend for Plugin and Theme developers to introduce persistent WordPress Administration notices for non-critical site activities or inappropriate site wide notices is becoming too common. I want to bring this to the attention of other WordPress users so that this can be addressed.

A ‘good’ developer will limit persistent notices to critical site activities only (e.g. caching Plugins, major database updates).

In the above case WooThemes Subscription and Envato’s Theme notices are considered critical; subscription sales won’t work and the Theme will be missing core functionality without addressing those notices.

Configuring default options for a CSV exporter or installing a Plugin update helper isn’t a critical activity.

A ‘great’ developer will still add the ability to dismiss these notices even in the case of a critical site activity.

Envato’s Theme and SkyVerge have added a dismiss option with their exporter setup notice but in SkyVerge’s case the notice does not need to be on all screens or considered an error. Dropping the error CSS class and limiting this setup notice to just the Plugins, Dashboard > Updates and own CSV Export screens would be better.

WooThemes don’t offer a dismiss option at all which makes for unnecessary nagging and screen clutter and goes against the WordPress Plugin Guidelines.

It’s fine to put an error message at the top of the admin for special cases, but it should be linked to a way to fix the error and it should be infrequent. Any form of “nagging” is absolutely prohibited.

That’s my rant. I’ll add an option to the next release of Store Toolkit for WooCommerce to hide that persistent notice so this post isn’t all for a lost cause.

Finally a Fix for XAMPP and WordPress Permalinks

Error 500 – Server error!

Fun times with Apache… Recent releases of XAMPP for Windows hide additional Apache overrides outside of the reach of …/apache/conf/httpd.conf. If you’re like me and exhausted all prior Google results to get Permalinks working with XAMPP give this one a go.

Open …/apache/conf/extra/httpd-xampp.conf
Replace all instances of AllowOverride None and AllowOverride AuthConfig with AllowOverride All
Save changes
Open XAMPP Control Panel and restart the Apache service or open the Windows Services dialog and restart the Apache2.4 Service
Breathe and give that Error 500 tab a refresh

Woop! In case this doesn’t work it’s likely you’ve missed one of the basics:

Open …/apache/httpd.conf
Uncomment #LoadModule rewrite_module modules/mod_rewrite.so
Replace all instances of AllowOverride None and AllowOverride AuthConfig with AllowOverride All
Save changes
As above, restart the Apache Service.

Hidden bbPress Admin menus conflict due to WP e-Commerce

If you have a WordPress site that has previously been using WP e-Commerce (version 3.8.13 and and earlier) upon activating bbPress you will notice, well, no bbPress menus or references. Anywhere.

Update: You may get a “You have insufficient WordPress permissions” notice when activating bbPress, the following steps will fix this conflict with WP e-Commerce.

Earlier releases of WP e-Commerce adjusted the default role capabilities of WordPress User’s which for one reason or another – I am yet to identify the exact cause – results in bbPress not loading it’s welcome script (e.g. creating new default Pages, intro screen, WordPress Admin menu’s, etc.). Here’s the fix.

Install and activate User Role Editor from Plugins > Install within the WordPress Administration
Open Users > User Role Editor
Click Reset
De-activate and re-activate bbPress

That’s it!

Don’t do e-Commerce Plugin releases on Christmas Day or before Holidays

Just don’t do it. Here’s why in 3 concise reasons:

Store owners don’t update their stores during peak season
Limited support staff are around to help store owners
Store owners that have updated their stores, and haven’t done backups, which then run into problems are going to flip out

Turn on Link Target support for Custom WordPress Menu Items

Hidden away in the Screen Options dropdown of the Edit Menus screen of the WordPress Administration are a set of advanced menu properties that can be toggled to extend WordPress menu items even further.

Display list of Custom Post Type items under Pages list
Open link in a new window/tab
Optional CSS classes
Link Relationship (XFN)
Link Description

Pretty sneaky WordPress!

Reference: Add ‘target’ element to Menu Editor