John Sundberg

Hi Phil,

I don’t use SolidWP’s security plugin, but I do use their backup plugin. I suppose the reason their plugin doesn’t help with spam registrations is that your default WordPress registration form is still open to the web at https://christformationencounters.com/wp-login.php?action=register.

It looks like you do have reCAPTCHA protecting that registration page, sort of, but it still allowed me to register for your site under a fake username and password (test, [email protected]). And if I can do it, the spammers definitely can and will.

Your LearnDash configuration appears to be a bit different than mine since you’re also using WooCommerce to sell access to your courses, but the solution I’m using on my client’s site may still work for you with some modifications to the code. I’d have to look under the hood, so to speak, to know for sure.

You can contact me directly through my contact form at https://blackhillswebworks.com/contact/ if you’d like to hire me to look into this further.

John

I was also dealing with spam registrations on a LearnDash site and came up with a solution that has stopped those spam registrations completely. I just wrote a blog post that explains what I did, which you can read here.

Hope that helps!

For a temporary fix until GiveWP sends out an update, comment out line 34 in the file listed in the Warning message – /plugins/give/src/License/PremiumAddonsListManager.php

Line 34 should be this line:

$response = wp_remote_get( self::PRODUCTS_LIST_API_URL . '?number=-1' );

Comment that line by adding // in front of it.

It looks like this error didn’t show for a while due to the plugin using a cached transient that must have ended recently.

That seems to be working. Thanks much!

Has something changed with how this filter works?

I need to give editors the capability to manage_options on a client’s site, but using the add_filter code posted above, with ‘update_core’ as the returned value, doesn’t have any effect on whether the editors can see the dashboard widget (they still can).

I’ll add my voice to this thread. I just installed Error Log Monitoring for the first time and the times in the log are remaining UTC, even though the timezone is set for “Denver” (Mountain Time, US).

Automatic newsletters had stopped sending for one of my clients, and what I ended up doing to fix it was go into MailPoet > Settings > Geeky Options and uncheck Enable MailPoet’s Cron, click Save settings, then check Enable MailPoet’s Cron, and click Save settings again.

Two automatic newsletters that had stopped working immediately started sending after I did this.

Hi Brady,

Yeah, it did, more or less.

Uncaught TypeError: Cannot read property ‘av’ of undefined indicated mce-view.js at line 63.

The other three errors fell under the load-scripts.php compilation.

Nice! I did notice that filter when I was looking at the Pro version on your website – thanks for including it on this version also.

Sounds good!

The problem seems to be in mysql2date() as used in woo_ce_format_date.

mysql2date() is only recognizing some strings, such as ‘U’, ‘l, F j, Y’, ‘m/d/Y’, and ‘d/m/Y’ but not ‘F j, Y’ for example.

‘F j, Y’ is an acceptable PHP date format from what I can tell, so I’m not sure what’s happening that would cause this?

No problem, Matty – glad to help!

martinh_uk, thanks for that solution!

sba7elfol,

As far as I know it’s still working, and from looking at Jetpack’s code I don’t see where this filter is WordPress-version dependent.

I’m currently running WP 4.4.2 on 30+ sites along with this Jetpack filter and the messages seem to be turned off.

If you want to copy/paste the code you’re using into a comment here I’ll see if I can see any issues with it.

John

Hey Umocrajen,

Thanks for working through that code. It would be nice to only have to create the array of meta_keys once, but this works for now.

In wp-post-meta-revisions.php there is this code block:

// Add the revisioned meta to get_post_metadata for preview meta data
public function _add_metadata_preview_filter() {
	add_filter( 'get_post_metadata', array( $this, '_wp_preview_meta_filter'), 10, 4 );
}

And on the plugin’s description page there is this bullet point:

• Adds revisioned meta to the preview data via get_post_metadata

That code and that bullet point led me to think that the meta data would be displayed on the Compare Revisions screen. Perhaps I misunderstood?

Anyhow, thanks again for working on this!
John