Kuba Mikita

Hi, usually that’s an issue with conflicted plugins or poorly designed cron logic. Our plugin can only show the issues and let’s you visually see what’s happening within WP Cron.

Hey, it’s not! We’ll releasing an update soon to match Notification v9.

Hi, this is exactly what it does – it just defines the constant for you so you don’t have to edit the wp-config.php file.

You need to setup the server scheduler still, even with the checkbox on.

Well, looks like it’s not implemented server cron, or your WordPress doesn’t spawn WP Cron correctly. Make sure the “Enable server scheduler” option is disabled, and DISABLE_WP_CRON constant in wp-config.php file is set to false or is not there at all.

Otherwise, it’s a instance specific issue, not the plugin error.

Hi, we’re not providing live support. You can describe the issue here and we can try to figure it out.

Hi, the function name doesn’t matter at all, we’re generating its name everytime to be unique to prevent from fatal errors. What’s more important is the hook name which is always the same.

We’ll change that code to a closure in the future releases

You’d simply decrease the number of logs kept in the database, by default it’s 1000. When you reduce it to 100 it won’t grow beyond that.

I hope this helps!

Hey, the plugin has been already fixed and it’s pending review. It should be back in the repository within few days. There was a minor security issue, but they decided to take it down ???♂?

Hi, it doesn’t seem like that’s the issue. The website is hosted on AWS.

I can see the “OPTIMIZE THE WORDFENCE FIREWALL” button, so it was never activated.

What to do in this case?

Hey, please use the merge tags from the sidebar, probably {post_permalink} will become {business_user_permalink} or something similar.

As for the meta field, you’ll need the Custom Fields extension. You can find the docs how to use it here.

Hi, thanks for the report!

Yes, it’s already fixed and waiting for the release of Notification v9 ??

Absolutely, refund on the way!

Hi Corey, I did reply to each of those messages, but they didn’t seem to hit your inbox.

You mentioned the lack of email testing is the reason for the refund, and my reply was:

Our plugin is too complicated to allow sending test emails, but we have a better option.

Simply go to Notifications -> Settings -> Debugging and enable Notification logging + Suppressing. This way you’re able to test the emails exactly how they’ll be sent. Alternatively, you can just provide your email as the only notification recipient.

Let me know if that helps. If not, I’ll provide the refund as requested.

Thanks!

Hi, that means the event was supposed to be triggered 280 seconds earlier. See the cron handbook

You might want to use the Server Scheduler instead.

NaN in the memory used means we couldn’t get detailed data about the memory consumption.

Sorry for the inconvenience, we had a small distribution issue which caused the package to not have any CSS and JS assets. This has been fixed in version 2.5.9.