About CeeVee Global: Empowering Your WordPress Journey

It’s late, the site is white, and nothing you click does anything

You updated one plugin. Or edited one line in wp-config.php. Or nothing at all — it just stopped.

No error message. No clue where to start. And every search result says “clear your cache” like that’s ever fixed anything on its own.

I know that feeling well, because I’ve caused it more than once.

Hi — I’m Dimu Harshana

I fix WordPress sites, and I write down what actually worked.

Not the theory. Not the twelve things it might be. The thing that fixed it, in the order I did it, with the commands I actually ran.

Here’s the rule I hold myself to

If I haven’t run it, it isn’t on this site.

Every fix in the Error Database came from a real error, on a real install, that I broke or inherited or walked into at a bad moment. I reproduce it, fix it, then write it up while it’s fresh.

That’s why the steps have the boring parts left in — the check that tells you whether it worked, the thing that looks right but isn’t, the step you can skip and the one you can’t.

It’s also why you’ll find “this didn’t work” in my guides. Because it usually didn’t, the first time.

Where I started: a white 486 and a floppy disk

My first computer was an old white 486 that loaded everything from a floppy disk. Nothing about it was forgiving, and when something broke, you fixed it yourself or it stayed broken. I think that’s where the habit comes from.

Years later I studied for my MSc in Computing with IT Management at the University of Gloucestershire in the UK, and stayed on to work at the university before moving back to Sri Lanka. Same lesson, bigger machines.

I’m not a guru, and I’d rather you didn’t treat me like one

I’m a builder who’s a bit further down the road than you. That’s it.

I’ve been in IT for over 15 years, the last 8 of them deep in WordPress, automation and AI tools, and the MSc mostly taught me that building a thing and running a thing are two different jobs.

But none of that is the reason to trust a fix here. The reason is that it’s been run.

The site you’re on was my own mess first

CeeVeeGlobal grew for years the way most sites do — a snippet here, a plugin there, a points system nobody asked for. It got slow. I couldn’t explain half of my own setup.

So in 2026 I tore it down and rebuilt it properly: the errors reorganised by how bad they actually are, a real search that understands error codes, and a lot of things I got wrong on the way and had to redo.

That rebuild is on the blog too — including the parts where I broke it.

Where this is heading

WordPress is where I learned all of this, and it isn’t going anywhere soon. But AI is changing how websites get built, and I think it will overtake the old way. I want to work out what really works before it’s obvious to everyone, and then write it down here.

I’ll be honest about my motive too: I’m lazy. I always look for the easy path, and these days that path usually runs through AI. Same rule as ever, though. If I haven’t run it, it isn’t on this site.

What you’ll find here

The Error Database — step-by-step fixes, filed by how bad the problem is, so you can start from what you’re seeing rather than guessing what it’s called.

Site completely down? Start with Critical — white screen, database connection errors, 503s. Working but broken? Warning — timeouts, failed uploads, redirect loops, 500s, 413 Request Entity Too Large.

The blog — longer pieces on WordPress, Python automation, self-hosting and the AI tools I’ve built and tested. Usually with the numbers I measured, because “it felt faster” isn’t a result.

YouTube — walkthroughs on the CeeVee Global channel, where you can watch the thing happen instead of reading about it.

Who this is actually for

You’re smart. You just haven’t done this specific thing yet.

You don’t want a 4,000-word essay that explains what a database is before it gets to the fix. You want the fix, the reason it works, and enough context that you can handle the next one yourself.

That’s the whole goal here: turn learners into builders. Start simple. Build fast. Learn by doing.

If you’d rather someone just did it

Some people want the fix. Some people want their site to work and would rather not learn any of this — which is completely reasonable.

If that’s you, get an instant price estimate. Takes about two minutes, no call to book, no follow-up sequence.

And if something’s broken right now, skip all of this and go straight to the Error Database. That’s what it’s there for.