Categories
Updates

Fighting a One Man War Against Magento

Photo by James Pond on Unsplash

It struck me today that I might be fighting a one-man war against Magento.

That’s a weird place to be in. A copywriter who used to be into web development versus one of the biggest ecommerce CMS’s on the planet.

Talk about some David and Goliath shit right there.

It’s not really a place where I expected to be in, nor wanted to find myself.

And certainly not a couple years back when I actually considered the platform kind of alright and thought my year and a half of experience with it would be worth a damn.

But then came a project where it all came tumbling down and I had the worst month of my life career-wise.

For a platform that prided itself on versatility, flexibility and being robust, it sure ended up being a royal pain the ass.

I survived, but the web development side of my business didn’t.

In response, I wrote a ranty, garbled blog about Magento to vent, and then the remarkable thing happened.

People read it. A lot of people. People just like me. Web developers getting fucked by Magento.

Reading over the comments from developers and investors who’ve worked with the platform, it’s clear that my story isn’t by any means unique.

The scary part is that story is by no means the worst. In fact, I count myself among the fortunate ones.

I’ve heard from people who’ve wasted years of their live stuck with Magento. Others, who sunk tens of thousands of dollars into that garbage heap, only to eventually have to pull the plug and start anew.

The even sadder thing is that nothing has changed. Magento is still a big pile of dogshit.

I didn’t think of it much at first, but by the second and then third year of the same comments rolling onto my blog and the emails hitting my inbox, I knew this was bigger than just me. Maybe bigger than a couple dozen other angry devs.

It had to be bigger, because Magento was and still is one of the largest ecommerce platforms out there. It’s bigger because Magento wants this fight to be bigger.

When it hit me, that’s when I became an anti-Magento evangelist. It wasn’t entirely conscious, but any time I saw a question about it on a forum, a suggestion on a site, anything, I would try to answer it honestly.

And the honest truth is stay the fuck away from that CMS.

Some weeks, it feels more and more like a war that I didn’t start nor want to be part of, but because Magento is still out there, ruining lives, I’m stuck in this never-ending clusterfuck of a battle.

I find people talking about it on Reddit. Others asking about it on Quora.

Dear God, the people on Quora.

It’s remarkable how many asshat developers mostly out of South Asia or Eastern Europe try to lure people into that platform. They talk about it being the best, how it’s free, and then sneakily add a couple of spam or affiliate links into their post, suggesting they could make the damn site for them.

Fuck those gargoyles. All they’re doing is luring more people into the trap. I know how it goes.

It’s something like: “hey, let me build you a Magento site. Unlike Shopify, it’s free, so you’ll save money.” And then that entrepreneur ends up having to shit money fixing their site with that dumbass developer for the next five years.

Fuck those guys.

I’d say that 9 out of evert 10 questions I answer on Quora fall under the ecommerce section. And of those answers, at least half deal with Magento – or more specifically, warning developers and entrepreneurs as best I can about it.

In all, over the years, I’d estimate I’ve messages or replied to over a hundred people about the woes of Magento. Add the fifty or so people who commented on my blog and the thousand or so others who read it without commenting and I’ve warned probably close to 1200 people.

I’m just one person, and all things considered, my opinion and reviews of the platform might have affected close to a thousand people who were thinking of using it and then (hopefully) learned otherwise.

In terms of marketing cloud, that’s a lot of power. I wouldn’t say that I’m an influencer when it comes to steering people away from shitty ecommerce choices, but I’m down near as prolific.

Still, it seems like I’m out on the front line all alone. I’m the only one. Why aren’t there other people like me trying to fix ecommerce, warn the world and keep people safe?

Okay, scratch that. No more maybes. I’m fighting this war. People have to know about the evils of Magento before it breaks them.

Categories
Technical Support

Google Calendar is Down? There’s a First.

Hmmm…

Google Calendar is down? Now there’s a first.

I was working in Adwords… sorry, Google Ads, all morning and noticing that things were a little on the slow side.

Of course, in the case of Google Ads, “on the slow side” really means “on the slower side” since that new dashboard always takes forever to load.

Anyways, after I saved up some work, I went to add an event into my calendar and then the fun started happening.

After adding a meeting, I got a message saying that the calendar couldn’t create this event and to please try again later.

I X’d out the notification, and then it popped up again. And again. And again.

Nothing like a spin around the block.

Finally, I refreshed the page and that’s when I got hit with that little 404 message up there.

Definitely not something I’ve seen before – nor expecting from Google.

Usually, that company gets pretty creative with its error messages and pages not found. Just check out what happens with Chrome when you try to browse and you’re not connected to the internet.

Why is it apps always seem to break when you need them the most? Here’s hoping it comes back to life soon.

Categories
SEO

Why is my WordPress Sitemap not Working? One Simple Answer.

Ah sitemaps.

They play an essential role in WordPress SEO by telling Google and friends what pages to crawl.

When they work, we love them. When they don’t, well, just thinking about all that lost traffic makes us shake our fists and want to smash our keyboards.

My WordPress Sitemap isn’t working, what do I do?

So you’re running a WordPress site and you got a faulty sitemap that’s not working?

There are a lot of different reasons why a sitemap might not function correctly in WordPress.

Some are technical, such as issues with an integrated WordPress ache plugin like WP Super Cache or developer code that went a little awry in its implementation.

Others could be much more mundane, such as having an out of date plugin generating your sitemap, or even something as simple as the box for sitemaps being unchecked by accident.

However, if you’re running a WordPress site and having issues with the sitemap that’s being generated, I’m willing to bet that it’s a plugin conflict issue.

I’ve had tons of issues with sitemaps over the years, and from my own experience (not to mention what I’ve read from browsing around the net), I’m gonna say this is one of the top culprits for faulty sitemaps.

What plugins are causing my sitemap to malfunction?

From my experience, the two main plugins that typically lead to a broken sitemap are Yoast SEO (or other comprehensive SEO plugin) and Google XML Sitemap.

Now don’t get me wrong. Both of these are great plugins. Yoast is the most popular WordPress SEO plugin for a reason, and Google XML Sitemaps does a great job at, well, making sitemaps.

The issue is when you have both of them installed and activated at the same time. The reason for this is because Yoast has a built-in sitemap feature.

If you try to activate two different sitemap plugins, your site simply won’t know what to do with itself.

What seems to happen is that one sitemap becomes static, frozen, while each time you try to update it causes a duplicate sitemap or backup to be created in your root directory.

The problem here is that the one frozen in time, never updating or completing itself, is the one bots will crawl and not the other file.

Fixing this is fairly simple, if not exactly straightforward.

Just going into your WordPress backend and disabling one of the two conflicting sitemaps won’t solve the issue. Neither will deactivating one of your plugins.

You’ll notice if you have Yoast installed and Google XML Sitemaps too, and you disable the latter, the conflict will persist in your sitemap file.

The only solution as far as I know is to delete one of the plugins. Not disable, actual DELETE.

In my case, when this happened to me, Google XML Sitemaps and then installed Yoast and didn’t even notice the issue for months. It was only when I replaced Yoast with the SEO Framework did I realize how bugged my sitemap was.

So if you’re in the same situation try:

  1. Double check to see if you have two plugins that both generate XML sitemaps.
  2. Disable / un-check all your sitemap creation tools.
  3. Delete one of the plugins. If you’re running Yoast, I would recommend deleted Google XML Sitemaps simply because it affects less of your posts.
  4. Reactive one sitemap tool.
  5. Refresh your page and maybe even clear your browser’s cache just to be sure.
  6. Verify that your sitemap is now correct and voila!

An optional step, in case your issue lasted for an extended period of time, is to re-submit your sitemap.xml file to your Google Search Console. That way Google will be able to discover all the “lost” pages that might not have been getting crawled or indexed correctly.

Of course, if you’re not sure where to look for your Yoast sitemap in the first place, try this:

Open WordPress and find Yoast:

Next, go to features:

Third, scroll down and see if Sitemaps is activated.

Hope this helps. If it does (or doesn’t), leave a comment below and let others know.