Wiles WordPress Theme
The Wiles WordPress Theme was a free three-column masonry blog theme built on Underscores, distributed with a footer credit link back to this site. It is no longer maintained. If you arrived from a credit link in somebody’s footer, that site is running theme code nobody is patching — and this page sets out what that means, how to confirm it, and what to do about it.
What the Wiles WordPress Theme was
Wiles laid posts out in a three-column masonry grid — tiles of varying height packed to fill the available space, rather than a stacked list of full-width entries. That presentation suits blogs where posts are visually led and vary in length: photography, recipes, short-form notes, anything where the reader browses rather than reads top to bottom.
It was built on Underscores, the starter theme from the WordPress community — a deliberate choice that says something about the code underneath. Underscores is not a framework you depend on at runtime; it is a starting point you copy and then own. That means Wiles has no third-party framework to be abandoned out from under it, and its template structure follows conventional WordPress patterns rather than a proprietary system. Both are good things. Neither means the theme is maintained.
The sibling themes from the same release group are documented here:
- Trope — a clean, content-first theme for personal and fashion blogs
- Candour — for blogs, travel and magazine-style sites
- Bubbly — a lighter blogging theme with multiple homepage layouts
- Delish — a free blog theme from the same group
- Engross — a zigzag-layout blog theme
- Dansal — a child theme of Twenty Sixteen
- Parole 2015 — a child theme of Twenty Fifteen
Is the Wiles WordPress Theme still maintained?
No. No PHP compatibility patches, no updates for WordPress core API changes, no security fixes if a vulnerability is found. The theme sits exactly where development left it.
Being built on Underscores does not change this. Underscores is a starting template that gets copied into a theme, not a dependency that keeps updating in place — so improvements made to Underscores since Wiles was built have never reached it and never will. The code is as old as the theme.
One caveat on reading 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 problem today depends on your PHP version, your plugin set, and how much has been modified. The checks below are how you find out.
What goes wrong with an unmaintained theme
PHP version drift
The most common actual failure mode. Hosts move their default PHP forward, and each major release turns previously tolerated patterns into fatal errors — null passed where a string is expected, a removed function still called, a type coercion no longer permitted. A maintained theme is patched ahead of the deadline; an unmaintained one meets it on upgrade day, usually as a white screen rather than a useful message. Treat a scheduled PHP upgrade email from your host as a deadline.
Masonry is the fragile part here
Worth being specific, because it is the theme’s defining feature. Masonry layouts of this era are produced by JavaScript that measures tiles after the page loads and repositions them. That has two consequences you will feel today rather than at some future upgrade.
The first is Cumulative Layout Shift. Content that gets repositioned by script after first paint is, by definition, layout shift — and CLS is one of the Core Web Vitals Google measures. Modern CSS grid can produce comparable layouts without any post-load repositioning, but a theme from this period will not be using it.
The second is fragility. Script-driven layout depends on the script running successfully, which depends on jQuery or a bundled library still loading correctly alongside everything else on the page. A plugin conflict, a deferred-script optimisation, or an aggressive minifier can leave you with a column of overlapping tiles. If your Wiles site has ever looked broken after you enabled a performance plugin, this is almost certainly why.
Core API drift
Slower and gentler, because WordPress protects backward compatibility — but cumulative. Deprecated functions, adjusted template behaviour, newer editor features assuming theme support that was never declared. Symptoms begin cosmetic: a block rendering unstyled, alignment controls doing nothing, a widget area refusing a newer block type.
Security exposure
A small theme has less attack surface than a large commercial one bundling a plugin framework, so the baseline risk is lower. What differs is what happens after a flaw is disclosed: a maintained theme ships a patch, an unmaintained one does not. If you are keeping it, that is the argument for a security plugin and tested backups.
Image handling
A grid theme is an image theme, and Wiles predates the current baseline: no native modern responsive image markup, no lazy-loading of below-the-fold media by current defaults, no attempt to prioritise the largest contentful element. On a three-column grid that loads many thumbnails above the fold, this 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 |
| You enable a performance plugin | High, and this one bites today | Overlapping or stacked tiles — deferred or combined JavaScript broke the masonry script | Change one script setting at a time and check the homepage after each |
| Core Web Vitals assessment | Ongoing, and structural here | Layout shift by design — tiles are repositioned by script after first paint | Cannot be configured away. CSS grid in a block theme fixes it |
| 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 |
How to check whether you are running it
- Appearance → Themes in your admin — the active theme is labelled.
- The footer — a surviving credit link is the theme announcing itself.
- 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.
What to move to
A currently maintained theme. Twenty Twenty-Five is maintained by the WordPress project itself, patched on the same schedule as core. For a grid layout specifically, the block editor’s Query Loop block produces multi-column post grids using CSS grid rather than post-load JavaScript — which means no repositioning after paint, and therefore none of the layout shift the old masonry approach causes. That is a genuine improvement on what Wiles does, not merely a newer way of doing the same thing.
For alternatives, see the block-based themes worth considering and the broader free theme roundup. The criterion that matters most is unexciting and checkable: when was it last updated, and does the developer have a record of updating it.
How to migrate without breaking the site
- Back up files and database off the server — not an untested host snapshot. See backup plugins.
- Work on staging. Most decent hosts include it; otherwise clone the site to a subdomain.
- Check your featured images. Grid themes lean on featured images, and posts without one often look broken in a grid. Before switching, note which posts are missing them — the new theme will expose the same gaps differently.
- Inventory what the theme owns: custom widget areas, theme shortcodes, custom post types registered in
functions.php, and any layout settings stored as theme options. All of it disappears on deactivation. - Activate the new theme on staging and walk every template: homepage, single post, archive, page, search, 404. Check on a phone, where a three-column grid collapses to one and the differences show most.
- Rebuild menus and widgets. Menu locations are theme-defined.
- Verify SEO output. Titles, descriptions and structured data usually live in your SEO plugin and carry over — confirm rather than assume. A current SEO plugin makes this straightforward; our Rank Math review covers one in depth.
- Deploy in your quietest hours and re-check the same list live.
If you decide to keep running it
- Know your PHP version and check it before your host’s next migration window.
- Keep core and every plugin current.
- Test your backups. An untested backup is a belief, not a backup.
- Be careful with performance plugins. Script deferral, combination and minification are the settings most likely to break a JavaScript masonry layout. Change one at a time and check the homepage after each.
- Re-check key templates after any core or PHP change.
- Choose a host that warns you before PHP changes and gives you staging — see our hosting comparison.
Common questions
Is the Wiles WordPress Theme still available to download?
It is no longer distributed or supported here. Do not install a copy from a third-party file-sharing site — repackaged themes from unofficial sources are a well-established vector for injected backdoor code.
Does the theme being built on Underscores make it safer?
It makes the code more conventional and easier for a developer to read, which helps if you ever pay someone to fix it. It does not make it maintained. Underscores is copied into a theme at the start, not linked to afterwards, so nothing that has improved in Underscores since has reached Wiles.
My grid looks broken on mobile. Is that the theme?
Probably, though not certainly. Script-driven masonry from this period handles narrow viewports less reliably than modern CSS grid, and it interacts badly with performance plugins that defer or combine JavaScript. Try disabling script optimisation first — if the grid recovers, you have found the interaction rather than a fault in either piece alone.
Is a child theme a safer position?
It depends on the parent. A child of a WordPress default — Dansal on Twenty Sixteen, or Parole 2015 on Twenty Fifteen — inherits fixes from a parent the WordPress project still maintains. Wiles is standalone, so nothing underneath it is being maintained. That is the distinction in the diagram above.
The short version
The Wiles WordPress Theme was a three-column masonry blog theme on a solid, conventional Underscores base. The base is good; the maintenance is absent. Its defining feature — JavaScript masonry — is also its weakest point today, because it causes layout shift by design and breaks when performance plugins touch the scripts it depends on. A current block theme produces the same grid with CSS and none of that fragility. Back up, test on staging, and move when it suits you.
