Greg

No, Akismet doesn’t currently look over registrations, just comments and feedback forms.

We have Akismet

What does the history link show (when hovering your mouse over the comment)? Marked as spam, or cleared by Akismet? If marked as spam, drop a line here with your API key and site URL:
https://akismet.com/contact

If you don’t have comments enabled or feedback forms on your site, the you really wouldn’t need to use Akismet.

Hi,

Go into your spam folder, and mark the message as “Not Spam”.

That’s likely the reason, wp-cron needs to run in order to check post dates and remove those.

One of the posters sometimes ends up in the Trash folder — I found an Akismet developer elsewhere who said it was impossible that Akismet would do this,

That’s correct, if Akismet marks something as spam it would go into the spam folder. After 15 days, WP should delete it, but not place it in the spam folder. Do you maybe have something in your WP comment blacklist that matches something (email, IP, comment) that this person is posting?

Your best bet would be to get in touch with us here, please include your site URL, API key and we’d be happy to have a look. Just reference this topic in your message.

https://akismet.com/contact

Hi Pepe,

Can you get in touch as I mentioned above?

If you go to your Dashboard > Comments > Spam tab and hover over the comment, there should be an option beneath that says “Not Spam”. Does that not appear for you?

Happy to have a look. Can you drop us a line with your site URL and API key here?
https://akismet.com/contact

Just reference this thread in the message so we can keep track of things.

With the comment only being held for moderation, and not being marked as spam, it does indeed sound like something in your comment moderation section might be causing this. There are no blacklist settings in Akismet.

For account issues, it’s best if you drop us (Akismet) a line here with the details:
https://akismet.com/contact

But, I do recall something about an API key.

I have a strong feeling that this is referring to their API key. An API (application program interface) key is really just a site/software specific authorization code that allows access to a service. Think of it as a password for the program you’re running, many vendors use them, but they’re specific to their services.

From their site documentation:

Generate API Keys
The API keys created by our system are the heart and soul of how the product verification system works. After confirming your purchase codes via Envato’s Marketplace API, we can then take those valid codes and use them to generate unique keys that are assigned to a specific domain. Each verified license allows you to generate one Themeco API key, which can then be used for unlocking automatic updates as well as future member features for that one domain. You do not need to have an API key to use X; however, you must verify your purchase(s) if you wish to unlock automatic updates and future member only features. If you chose not to verify your purchase, you will need to update X manually.

Thanks, by the way.

You’re very welcome, hope this helps. ??

I didn’t see it until I activated Akismet. To be fair, I hadn’t been able to successfully gain access to the XTheme customation page before that.

Hmm, that seems very strange. Akismet is included in each distribution of WordPress Core and is tested very thoroughly. I would guess that another plugin is causing this error, or conflict. To test this theory you could either disable all other third party plugins, or enable debug: https://docs.akismet.com/general/how-do-i-debug-the-akismet-plugin/

I honestly don’t know if I don’t know about Apache Logs or how to access them.

Your webhost could probably assist in getting those, just ask for the logs with an error 500 status.

Did you see my question about whether I will even need Akismet if I don’t include a blog/comment feature?

I did see that, if you don’t allow comments and don’t have any contact forms, then no, you wouldn’t need Akismet.

Going back to your initial question, did the X-theme installation process indicate specifically that Akismet was needed, or just that you needed to enter an API key to activate the theme?

Is the 500 error new, or did you see that before?

Do you have access to the Apache logs to see what might be causing that error?

A dialog box along the way seemed to indicate I needed Akismet to proceed with the install process of X.

Hi Adam,

What exactly did this dialogue box say?