Candour WordPress Blog Theme

The Candour WordPress Blog Theme was a free theme built for blogs, travel sites and magazine-style layouts, distributed with a footer credit link back to this site. It is no longer maintained. If you arrived here from a credit link in somebody’s footer, that site is running theme code nobody is patching — and this page explains what that actually means, how to confirm it, and what your realistic options are.

What the Candour WordPress Blog Theme was

Candour sat between a plain blog theme and a magazine layout. It offered a wider content presentation than a single-column personal blog theme, with room for featured imagery and multiple post entries visible at once — the sort of structure that suits travel writing, photo-led posts and sites publishing several categories rather than one running stream.

Like the other free themes released here in the same period, it was deliberately light on machinery. No proprietary options framework, no bundled commercial slider, no page builder dependency. That matters for how it has aged: themes built on a bundled third-party framework tend to break hard when that dependency is abandoned, while themes made mostly of template files and CSS degrade slowly and quietly instead.

The sibling themes from that release are documented here too:

• Trope — a clean, content-first theme for personal and fashion blogs
• Delish — a free blog theme from the same group
• Bubbly — a lighter blogging theme with multiple homepage layouts
• Wiles — a three-column masonry theme built on Underscores
• Engross — a zigzag-layout blog theme
• Dansal — a child theme of Twenty Sixteen
• Parole 2015 — a child theme of Twenty Fifteen

Is the Candour WordPress Blog Theme still maintained?

No. There are no compatibility patches for new PHP releases, no updates when WordPress changes a template function or a core API, and no security fixes should a vulnerability be found. The theme is frozen where development left it.

That is not the same as saying it is broken. Sites are running it today and serving pages fine. It means nobody is minding the gap between the theme and the platform beneath it, and that gap grows on its own schedule rather than yours.

One caveat on how to read this page: it is written from the theme’s history and from how WordPress and PHP have changed since, not from an inspection of your site. Whether your install has a real problem right now depends on your PHP version, your plugin set, and how much the theme has been modified. The checks below are how you find that out.

What goes wrong with an unmaintained theme

PHP version drift

The most common way these themes actually fail. Hosts move their default PHP version forward, and each major release turns previous warnings into fatal errors — null passed where a string is expected, a removed function still being called, a type coercion that no longer applies. A maintained theme is patched before the deadline. An unmaintained one meets it on upgrade day, usually as a white screen rather than a useful message. If your host emails about a scheduled PHP upgrade, treat it as a deadline.

Core API drift

Slower and less dramatic, because WordPress takes backward compatibility seriously — but cumulative. Deprecated functions, adjusted template behaviour, and newer editor features that assume theme support an older theme never declared. Symptoms start cosmetic: a block rendering unstyled, alignment controls doing nothing, a widget area refusing a newer block type. The site does not fall over; it just drifts out of step with current WordPress.

Security exposure

A small, simple theme has less attack surface than a large commercial one with a bundled plugin framework, so the baseline risk is lower. The real difference is what happens after a flaw is disclosed: a maintained theme gets a patch, an unmaintained one does not. If you keep the theme, that is the argument for a security plugin and tested backups, rather than trusting simplicity to protect you.

Performance and Core Web Vitals

Candour predates the current performance baseline. It will not emit modern responsive image markup on its own, does not lazy-load below-the-fold media the way current themes do, and makes no attempt to prioritise the largest contentful element. WordPress core now handles some of this automatically and not the rest. On an image-heavy travel or magazine site — exactly what this theme was for — that matters more than it would on a text blog. A caching plugin improves delivery but cannot fix the markup.

What breaks, when, and what it costs you

Trigger	Likelihood	What you see	What to do
Host upgrades PHP	High — and scheduled by your host, not you	White screen or a broken template, usually with no useful error	Test on staging before the upgrade window closes
WordPress core update	Moderate, and cumulative	Blocks rendering unstyled, alignment controls doing nothing	Cosmetic. Worth noting, not worth panicking about
Theme vulnerability disclosed	Low — but no patch will ever come	Nothing, until it is exploited	Security plugin and tested backups, or migrate
Core Web Vitals assessment	Ongoing, and worse on an image-led site	Weak LCP from many unoptimised images above the fold	Cannot be configured away — needs a newer theme
You replace the theme	Certain, eventually	Featured-post and category-block settings gone, sidebar empty	Screenshot the homepage and inventory theme options first

How to check whether you are running it

1. Appearance → Themes in your WordPress admin. The active theme is labelled there.
2. The footer — if the credit link is still present on the live site, the theme is announcing itself.
3. View source on the homepage and search for /wp-content/themes/. The directory name in those asset paths is the theme genuinely loading. Trust this one if the answers disagree, because it reflects what the server is serving rather than what a settings screen claims.

What to move to

A currently maintained theme, and for blog and magazine layouts the WordPress default themes are a real option rather than a fallback. Twenty Twenty-Five is maintained by the WordPress project itself, so it is patched on the same cadence as core and cannot quietly become an abandoned side project. Being a block theme, its layout and typography are edited visually instead of in PHP — which is a meaningful advantage if the reason you never replaced Candour was that you did not want to touch template files.

For alternatives with more layout variety, the block-based themes worth considering and the broader free theme roundup cover current options. The selection criterion that matters most is unglamorous: when was it last updated, and does its developer have a track record of updating it. A striking theme last touched three years ago simply moves you back to where you are now.

How to migrate without breaking the site

1. Back up files and database to somewhere off the server first — not an untested host snapshot. See backup plugins.
2. Work on staging. Most decent hosts include one-click staging; otherwise clone the site to a subdomain. Never test a theme switch on production.
3. Inventory what the theme owns. This is the step people skip. Custom widget areas, theme-specific shortcodes, custom post types registered in functions.php, and social or layout settings stored as theme options all vanish when the theme is deactivated. On a magazine-style theme, featured-post and category-block settings are especially likely to live here. Write the list down first.
4. Activate the new theme on staging and walk every template that matters: homepage, single post, category archive, page, search, and 404. Check on a phone as well.
5. Rebuild menus and widgets. Menu locations are theme-defined, so assignments nearly always need redoing.
6. Verify your SEO output. Titles, descriptions and structured data usually live in your SEO plugin and carry over — but check rather than assume. A current SEO plugin makes this straightforward; our Rank Math review covers one in depth.
7. Deploy during your quietest hours and re-check the same list live.

If you decide to keep running it

Sometimes replacing the theme is not worth it. That is a legitimate call — just make it deliberately rather than by default, and reduce the blast radius:

• Know your PHP version and check it before your host’s next migration window.
• Keep core and every plugin current. The theme is the one thing you have chosen not to update; do not let the rest drift with it.
• Test your backups. An untested backup is a belief, not a backup.
• Cut plugin count — fewer interactions the theme has never been tested against.
• Re-check key templates after any core or PHP change. An unmaintained theme will not tell you it broke.
• Pick a host that warns you. Managed WordPress hosts flag PHP changes in advance and provide staging — see our hosting comparison. Here that is worth more than raw speed.

Common questions

Is the Candour WordPress Blog Theme still available to download?

It is no longer distributed or supported here. If you find a copy on a third-party file-sharing site, do not install it — repackaged WordPress themes from unofficial sources are a well-established vector for injected backdoor code, which would add a genuine security risk on top of an already unmaintained codebase.

Will my site break immediately if I do nothing?

Almost certainly not. Unmaintained themes tend to fail at a specific trigger, most often a PHP major-version upgrade, rather than degrading gradually. The risk is not that today goes wrong — it is that the day it does will be picked by your host rather than by you.

Can I just remove the footer credit link?

You can, by editing the footer template. But if you are editing theme files anyway you are doing unpaid maintenance on abandoned code, and every edit is lost the moment you replace the theme. That effort is better spent on the migration.

Is a child theme a safer position?

It depends on the parent. A child of a WordPress default — like Dansal on Twenty Sixteen or Parole 2015 on Twenty Fifteen — inherits fixes from a parent the WordPress project still maintains, so most of the code beneath you is still patched. Candour is standalone, so nothing underneath it is being maintained. That is the distinction in the diagram above.

The short version

The Candour WordPress Blog Theme was a free blog and magazine theme that has outlasted its own development because it was simple enough to keep working. It is not maintained and will not be. Nothing forces you to act today, but the site is carrying code nobody is watching, and the failure will most likely arrive with a PHP upgrade you did not schedule. Back up, test a maintained theme on staging, and move on your timing rather than your host’s.