ToddB

CORRECTION, the WordPress version is 6.1.1.

Rather than risking the dev version. What about a workaround?

Actually Paul, the path to BaseProtectionProvider.php may not be as outlined.
On my end it is located in /wp-content/plugins/wp-simple-firewall/src/lib/src/Modules/LoginGuard/Lib/AntiBot/ProtectionProviders

Thanks for the fix. ??

• This reply was modified 4 years, 10 months ago by ToddB.

Hey @donncha

Having a somewhat similar issue. There is a constant message at the top of the plugin settings:

CRON System Disabled
The WordPress CRON jobs system is disabled. This means the garbage collection system will not work unless you run the CRON system manually.

However, wp-config.php includes the define('ALTERNATE_WP_CRON', true); code. Since wp-cron is disabled. There is a manual cron job running every 30 minutes.

Stats show:

WP-Cache (0KB)

0 Cached Pages
0 Expired Pages

WP-Super-Cache (65.90KB)

304 Cached Pages
0 Expired Pages
List all cached files

Expired files are files older than 3600 seconds. They are still used by the plugin and are deleted periodically.

Preload mode is enabled. Supercache files will never be expired.

Is there a way of using a cron job to further automate Garbage Collection?

Hey @donncha

Having a somewhat similar issue. There is a constant message at the top of the plugin settings:

CRON System Disabled
The WordPress CRON jobs system is disabled. This means the garbage collection system will not work unless you run the CRON system manually.

However, wp-config.php includes the define('ALTERNATE_WP_CRON', true); code. And wp-cron is disabled.
But there is a manual cron job running every 30 minutes.

Stats show:

WP-Cache (0KB)

0 Cached Pages
0 Expired Pages

WP-Super-Cache (65.90KB)

304 Cached Pages
0 Expired Pages
List all cached files

Expired files are files older than 3600 seconds. They are still used by the plugin and are deleted periodically.

Preload mode is enabled. Supercache files will never be expired.

Is there a way of using a cron job to further automate Garbage Collection?

Thank you. That worked. Completely reset the plugin and settings.

Since the Jetpack 7.4 update wiped out the whole sidebar.

• This reply was modified 5 years, 9 months ago by ToddB.

@nicolamustone

4 Scheduled are able to post to Discord.

Thanks Nicola… very much appreciated.

What did you change or setup @thequasar?
Did you add anything to the functions.php file?

Since the plugin still does not work for me. This is after uninstalling and completely re-installing.

Unless there is some config file I have to delete as well.

@nextscripts

Done. Thanks. ??

Well WP Discord Post still does not work.

This line seems to produce some errors:

add_action( ‘publish_post’, array( WP_Discord_Post::instance()->post, ‘send_post’ ), 10, 2 );

Actually WP_Discord_Post produces an undefined instance error. Lol

Everything else continues to work but this plugin. And it was working up until v1.1.3.

• This reply was modified 6 years, 9 months ago by ToddB.

@igetin

Random question. What are you using for “post_type” in functions.php?

add_action( ‘publish_{post_type}’, array( WP_Discord_Post::instance()->post, ‘send_post’ ), 10, 2 );

I’m looking to compare notes. Any help would be great.

@nicolamustone

What’s going on with this plugin. I disabled then completely removed WP Discord Post.
Then re-installed, which my settings were maintained. But still missing that PHP file, class-wp-discord-post-jetpack-contact-form.php.

Should I be removing the WP Discord code from functions.php?

@nicolamustone

So uninstalled the plugin completely and then re-installed.

I have the same missing file and still unable to post to Discord. Either scheduled posts, updated posts or new posts.

And also missing the jetpack php file, still:

wp-content/plugins/wp-discord-post/includes/class-wp-discord-post-jetpack-contact-form.php

@nicolamustone

Okay… so this file does not appear to be on the server:

wp-content/plugins/wp-discord-post/includes/class-wp-discord-post-jetpack-contact-form.php

Also, 66915 refers to a post published on May 27, 2018 at 11am EDT that was scheduled to publish to Discord. But did not.
And the timezone is EST.

• This reply was modified 6 years, 10 months ago by ToddB.

@nicolamustone

These are for new posts mainly. But usually I will see a notification when updating posts. I just remove the @ everyone option.
And yes, all of the new posts are scheduled and published automatically.

PHP error log:

[27-May-2018 15:00:05 UTC] WP Discord Post – Post 0 is not a new post. Skipping.
[27-May-2018 15:00:05 UTC] WP Discord Post – Post 66906 is not a new post. Skipping.

[27-May-2018 15:00:59 UTC] WP Discord Post – Post 0 is not a new post. Skipping.
[27-May-2018 15:00:59 UTC] WP Discord Post – Post 66915 is not a new post. Skipping.

[27-May-2018 15:00:54 UTC] PHP Warning: include_once(includes/class-wp-discord-post-jetpack-contact-form.php): failed to open stream: No such file or directory in /home/username/public_html/wp-content/plugins/wp-discord-post/wp-discord-post.php on line 108
[27-May-2018 15:00:54 UTC] PHP Warning: include_once(): Failed opening ‘includes/class-wp-discord-post-jetpack-contact-form.php’ for inclusion (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in /home/linuxgame/public_html/wp-content/plugins/wp-discord-post/wp-discord-post.php on line 108
[27-May-2018 15:00:56 UTC] PHP Notice: Undefined index: HTTPS in /home/username/public_html/wp-config.php on line 8
[27-May-2018 15:00:59 UTC] WP Discord Post – Post 0 is not a new post. Skipping.
[27-May-2018 15:00:59 UTC] WP Discord Post – Post 66915 is not a new post. Skipping.

• This reply was modified 6 years, 10 months ago by ToddB.