WordPress and This Blog - Helpful Colin

Sorry the sizes below relate to my old theme. I have to readjust them for the Twenty Sixteen theme I now use.

Current Maximum Width Screen Sizes

All Screens

Site Width: 1305px

Header Width: 1305px

Header Height: ?px

Menu Bar, etc. Width: ?px

Menu Bar, etc. Height: ?px

Sub Menu Items, Width: 200px

Sub Menu Items, Height: 36px

Go To Top Icon: 48px x 48px

Featured Images

Width: ?px

Height: ?px

Aspect Ratio W:H =?

Blog Posts

Content Width: 600px

Maximum Image Width: 600px

Maximum Image Height: 1100px

Left Margin: 111px

Text Width: 672px

Right Margin: 111px

Right Border: black 1px within right margin

Video Width: 672px

Video Height for Aspect Ratio 4:3 : 504px

Video Height for Aspect Ration 16:9 : 378px

Content Sidebar Width: 366px

Left Margin: 15px

Widget Width: 336px = 672 ÷ 2

Right Margin: 15px

Variable Full Width Pages

Left Margin: 30px

Text Width Max: 1200px

Right Margin: 30px

Fixed Full Width Pages

Left Margin: 30px

Text Width: 1200px

Right Margin: 30px

Select Posts by Category?

My Latest News

1st February 2019: I have just deleted a file named wordfenceScanner.php.bin from my PHP .opcache folder on my server. Wordfence had detected it contained the TimThumb script which is considered to be unsafe. I must look into methods of cleaning my PHP cache. It looks as if it contains some outdated files.

2nd January 2019: Again I couldn’t get my WP v5.0.1 to update to v5.0.2 so I followed Wordfence’s instructions and upgraded it manually. I made a good job of it and searched for the cause of the problem. It turned out to be caused by the plugin DGXPCO which is designed to improve Core update security.

Hopefully if the Core updating server got hacked and a false Core program was sent this plugin wouldn’t allow it to be applied due to manual intervention. Well that manual intervention failed to allow valid Core updates through so I have deactivated that plugin for the time being.

21st December 2018: I just upgraded my server from PHP 7.2 to PHP 7.3. I had an immediate problem with the plugin Taxonomy List Widget. I have sent a comment to the author Erick T. Hitter asking him to look into it. Otherwise so far so good.

14th December 2018: Having experimented with the new Gutenberg editor for over a year I was finally able to update WordPress to version 5.0.1 with Gutenberg in core yesterday. I couldn’t do it last week due to a technical hitch resolved by 1&1 IONOS. I then deleted the Gutenberg plugin, which had already been de-activated by the update. That caused a block editing problem where I only had Classic Paragraphs instead of Gutenberg Paragraphs. That was resolved by me de-activating TinyMCE, a plug in to enhance the original editor.

I can now report that I have adjusted some posts created or edited using various versions of Gutenberg to be editable using version 5.0.1.

Continue to My Latest News Archive.

Site Construction

The site helpfulcolin.com was originally built in September 2011 by Digitalog© using the Side Blog theme and handed over to Helpful Colin by his mentors (see their links below) in December 2011. It was changed to a ‘Twenty Fourteen’ child theme in February 2014 by Helpful Colin.

The latest major change took place in December 2015 when WordPress version 4.4 became active and Helpful Colin changed the theme to the ‘Twenty Sixteen’ theme which is designed to look good on all screen sizes. Although this may have improved the blog for mobile users it has removed some functionality available in ‘Twenty Fourteen’.