About

Sep 24, 2014: I’m currently a final semester student enrolled in SAIT’s SAGD Water Treatment Operator program.

Since the program requires students to work towards a 4th Class Power Engineering certificate, I’ve set up this blog as a personal study aid for some of the standard operating procedures for the equipment in SAIT’s power engineering labs. The blog will also be used to express some of my thoughts about studying for the Alberta Boiler Safety Association (ABSA) 4th Class exams.

Dec 12, 2014: Completed the SAGD Water Treatment program.

Apr 17, 2015: One of the WordPress blogs on my site was hacked. (Fortunately, not this blog.)

The hack was discovered about a month later, and fixed Jun 1, 2015.

To reduce time spent on security maintenance, this WordPress installation was converted to static HTML on Nov 6, 2015.

May 23, 2016: Completed the 4th Class Power Engineering certificate.

Nov 24, 2016: This blog was moved to its current URL and was re-converted back to WordPress from static HTML.

Dec 4, 2016: Theme, styles and plugins restored over past 10 days. HTACCESS file now redirects all web traffic from previous blog (and the static site) to the current URL. Current blog is now viewable by all visitors.

Dec 2, 2017: Google bots were still indexing the previous blog and the static site despite the redirect commands.

HTACCESS now delivers 410 (Gone) errors upon any attempt to access these two obsolete sites.

Sep 22, 2018: Site domain was changed from non-WWW to WWW, and visitors to http://powerengineeringalta.ca will now be redirected to http://www.powerengineeringalta.ca.

Benefits are expected to be marginal (very slight increase in speed & security as well as increased site scalability).

The real reason for the transition was as a dry-run for a different site, which will require a similar change in order for the CloudFlare CDN to be implemented (ie: CloudFlare requires WWW sites).

The only observable problem that occurred seemed to be on the back-end, where the CSS editor stopped working for the Child Theme. (However, this issue may have existed prior to the move).

Sep 26, 2018: After extensive troubleshooting, the problem with the WordPress editor not displaying the Child Theme’s CSS was eventually solved.

The issue was not caused by the move to WWW, or by plugins or HTACCESS files, but instead by an IE filter in the STYLE.CSS file. In order for old versions of Internet Explorer to display a color gradient in the top navbar, the following filter in the Child Theme’s stylesheet was used:

filter: progid:DXImageTransform.Microsoft.gradient(startColorStr='#3a66a7', EndColorStr='navy'); /* IE6-9 */

Evidently, there was some sort of syntax error in this code which WordPress’ CSS editor did not like, causing the editor to return a blank edit box for the Child Theme’s CSS.

At any rate, the above (correct) code is no longer preventing the Child Theme’s stylesheet from loading into the CSS editor in WordPress administration.

Sep 27, 2018: Discovered widget drag-and-drop capability was lost, and none of the widgets were editable.

Some sites advise that deactivating all plugins should fix the problem.

This action did not work, but this link has instructions on how to set up widgets so they are editable and can be added to the widget area. (Note: Does not restore widget drag-and-drop functionality, but instead uses Add and Edit buttons).

  1. DASHBOARD > APPEARANCE > WIDGETS
  2. ENABLE ACCESSIBILITY MODE

Jun 2, 2020: Website migrated to a new host with free SSL, so the site should be more secure than it was before. Accordingly, the site’s protocol has changed from HTTP to HTTPS.

The new host also utilizes a much more recent version of PHP, so the site should be a little faster.

Mar 31, 2021: Flame animation on the H1 tag in the header was stopped for screens less than 800 px wide because it freezes screens on older mobile phones. For narrow screens, a static CSS3 fire effect is served instead.

Since the theme used does not include a hamburger menu, a hamburger menu plugin has also been added for mobile users. Unfortunately, it seems to load a little slowly on my cell phone (3 second load time after tapping the hamburger menu).