Justin Norton

Yes, please also WP version would be helpful.

Hi @w-sky, could you deactivate the plugin and let me know what happens?

Hello @w-sky, this issue should be resolved now. I have changed the Genres select field to be a standard text field and made some code updates to reflect this change. I think this is the best way forward as Google will most likely introduce new Genres all the time so having a free-form text field will allow publishers to adapt to these changes.

Hello @w-sky, this issue should be resolved now. I have changed the Genres select field to be a standard text field and made some code updates to reflect this change. I think this is the best way forward as Google will most likely introduce new Genres all the time so having a free-form text field will allow publishers to adapt to these changes.

Hello,

No that doesn’t solve the issue as relying on users to trigger the cron is not acceptable.

The problem with relying on users to trigger cron is that some sites I manage have limited traffic but large mailing lists. Site content is updated on a regular basis and newsletters should be sent immediately. If the site isn’t visited for several hours then no newsletters are sent.

Please fix as currently your plugin doesn’t work on WP Engine.

Hello, this issue has been fixed in the latest release. Apologies for not fixing sooner.

Hello, this issue has been fixed in the latest release. Apologies for not fixing sooner.

Hi there, apologies for the massive delay in getting to this. The (beta) plugin has now been updated and should be working as expected.

Hi there, thanks for the feedback. The (beta) plugin has been updated and should be working as expected now. Please test.

Hi there, thanks for the feedback. The plugin has recently been updated so please test. Cheers, J

Thanks for the fix Tim – much appreciated. As this issue has cured the bug for versions below WP 3.9 could you update the minimum WP version entry in the plugin readme.txt? Or is the release only tested against 3.9 and above?

The plugin file /lib/wfUtils.php, Line 104

Cheers Justin

I have patched affected sites using this:

public static function getPluginBaseDir(){
		if(function_exists('wp_normalize_path')){
			if(defined('WP_PLUGIN_DIR')) {
				return wp_normalize_path(WP_PLUGIN_DIR . '/');
			}
			return wp_normalize_path(WP_CONTENT_DIR . '/plugins/');
		} else {
			return WP_PLUGIN_DIR . '/';
		}
	}

You have deployed a release of Wordfence that contains wp_normalize_path() – this function is not supported on WordPress versions below 3.9. The result is a fatal error on affected sites. Please fix this issue ASAP as I imagine lots of sites are now broken due to auto updates.

Not fixed, just a suggested fix as the feed wasn’t found and caused an exception on my local machine.