Tag: WordPress (page 1 of 1)

How to Enable Akismet Anti-Spam on WordPress

This is going to be a super quick post, inspired by my late-night searching while trying to finally enable the anti-spam feature from Akismet (Jetpack) on this website. Every time I went through the Jetpack settings page and tried to enable the Personal version of the tool, I would click the “Learn More” button to try to enable it, but would then find myself on a plain page that simply said, “Sorry, you are not allowed to access this page.” When searching for how to resolve that through a normal search engine, I never found anything specific enough to help me. But I finally figured it out with the assistance of an AI chat, and I am so excited about finally fixing this issue that I needed to share it with everyone else.

What’s in this post

How to Enable Akismet Anti-Spam from Jetpack

I don’t know why this didn’t click for me earlier, but Akismet Anti-Spam is a plugin for WordPress, so to be able to enable the feature through the Jetpack main page, you first need the plugin installed on your website.

Once you install the plugin on your site, it is then easy to get it running by going through the entire process as prompted by Jetpack.

Install Plugin from Plugins Page

In your WordPress admin dashboard, click “Plugins > Add Plugins” from the menu on the left side.

Screenshot from the WordPress admin console showing that you should select the subitem "Add Plugin" under menu item "Plugins"

On that page, enter “Akismet” in the search box at the top right of the screen, then click “Install Now” on the “Akismet Anti-Spam: Spam Protection” plugin:

Screenshot of the WordPress admin console page where you can install the Akismet plugin by searching for it using the search box on the top right of the screen

You will then be directed through the purchasing process for the plugin, which applies even if you are doing the free personal version of the plugin. You will be asked to set an annual price for yourself (I chose $0 since I’m not currently making money on this site), then finish the “checkout process” using your Jetpack or WordPress account information.

After finishing the checkout process, I was provided with a screen and an API key for the plugin and received an email for setting up the plugin from Jetpack. I copied the API key to a safe location from the checkout screen, then went to my email and clicked the link for setting up the plugin. That took me to a screen in my WordPress admin console where I could choose to manually enter the API key, which I did.

At that point, the plugin was installed, set up, and already protecting me from spam!

Summary

I wish the explanation of how to handle the Akismet anti-spam plugin was a little more straightforward. The “Products” page of the Jetpack section on the admin portal makes it seem like you can get the feature directly from that section of the website, and people (like me) may get confused when they end up at an error screen instead of being prompted to install the plugin.

To enable the Akismet anti-spam feature on your WordPress site, first install it from the “Plugins” page of the admin portal, then work through the process as prompted by the setup process with Jetpack.

Related Posts

Using the WordPress Local Development Tool to Avoid JSON Errors

When I started my blog a couple months ago, I determined a posting schedule for myself of once a week on Tuesdays. If you are someone who notices details and patterns, you may have noticed that I went a few weeks without posting at the end of December and into January, but it wasn’t for lack of me trying. In this post I’m going to talk about the issues I faced that prevented me from posting and how I finally got a workaround for the problem that has finally allowed me to start posting again.

Background

While trying to create and edit my tutorial post about working with Liquibase, I kept running into the same vague JSON error when trying to save drafts, always at the same point. The error was: “Updating failed. The response is not a valid JSON response”.

The point at which it always failed was about midway through the post, either when I copied in text that contained double-quote characters or when I added the first image. I spent several weeks going back and forth with Flywheel (the web host I use) support, trying to figure out what was causing this JSON error when I tried to save a draft.

We tried many different things, including the normal troubleshooting steps of disabling plugins, reverting to the default WordPress theme, disabling all of my browser extensions, trying to work in an incognito window, and several other things. I read so many of the articles online discussing how to resolve this error, and none of those solutions worked. On the Flywheel side, they told me they were trying several different server changes, including extending timeout values and other firewall type changes. I even completely restored my website to default, but not even that worked. And then I had to rebuild everything on my website (except for posts and pages which I exported before restoring).

As of the time of writing this, I still don’t officially have a resolution from Flywheel for this error that keeps popping up and generating 403 errors on the backend (I figured that out myself by inspecting what happened when I clicked the “save draft” button). However, thanks to some kind folks on a WordPress forum, I finally figured out a viable workaround that I am actually enjoying using more than the online WordPress admin portal.

The Successful Workaround

The workaround that I am now using, even as I write this, is to use the development tool for WordPress called Local. This tool gives you a local development environment for WordPress that can seamlessly connect with Flywheel and other hosting providers. The setup for the tool was super easy, took me less than 5 minutes. After going through the setup, all I had to do was pull a copy of my site to local and then I have been able to locally edit my website through the tool.

Once you’re done making all your changes, you only need to select to “Push” to your production site, then select which changes you want to be pushed, then it’s quickly sent to your actual production website. It takes a few minutes for Flywheel to update with the changes, but then you can see your locally developed changes on your real site. All without the hassle of the ever-present JSON error when trying to save a draft.

I will be continuing to work with Flywheel to try to resolve the error on my production site, but at least for now, I am able to keep working and posting, back to my normal schedule.

Summary

If you are facing endless errors when trying to create posts for WordPress and you’re hosted with Flywheel, try using the Local tool to develop on your own local machine to see if that helps you in the same way it helped me.

UPDATE

We finally seem to have resolved my issue after going back and forth so many times with the Flywheel support team and continuing to escalate it through all their support levels. I’m not sure if this is what finally resolved the issue as I wasn’t provided any further details, but the last detailed message I received seemed to indicate that something was set up incorrectly with their Web Application Firewall (WAF) that was preventing me from editing. Before getting the issue fixed, I also found that I couldn’t edit the footer of my site because I was also getting 403 errors when trying to save those changes, and that along with my post creation issue has been resolved.

The moral of this update is that if you’re having this same issue and your site is hosted on Flywheel, keep pushing them to try more things on their end, don’t let them say that it must be something with your local environment. They were super great in continuing to try as long as I kept pushing and saying it still wasn’t working. It also seemed to help when I started showing them the exact errors I was getting with the Inspect tool in Chrome so they would have something to work with.