Manny Rodrigues

Thank you for reporting a compatibility conflict with the WP Mail Logging plugin.

Just had the same thing occur on one of my client sites. The issue is indeed with this plugin. What I discovered is that it is adding extra characters to one of the Facebook for WooCommerce variable fields. So much so that it is exhausting the servers php memory. You would want to locate that field and clear it of the extra inputted text. Then it works. For me it was under the “Product data” meta box > “Facebook” > “Show advanced options” checkbox > “Size” variable. I was using the quote symbol (“) for inches and it freaked out adding a bunch of backslashes followed by a percent sign ( \\\\\% ). Hope this helps!

I agree with @theamnesic the limit-login-attempts link is now in two locations. One on the main admin menu, the other one is under Settings. This plugin really runs itself and there is no need to clutter up the admin menu with a double lined option. Just my opinion and suggestion.

You are correct on both fronts @cybr

Bing should be able to parse them as valid html, but then again we are taking about Microsoft.

The HTML magnification benefit is worth this minor inconvenience so I will just leave verification to the XML until bing gets their act together.

I apologize for assuming it was an issue with your plugin. Which is fantastic by the way. Switching from yoast and google xml plugins to just yours. Well done sir!

Forgot to tag you @vmarko

Just wanted to chime in and confirm that since the most recent update, any gravity forms which usually use google’s recaptcha feature does not permit the form to submit.

Two work arounds:
– Disabling the recaptcha allows the form to send (not ideal).
– Keeping recaptcha enabled while disabling W3 Total Cache also fixes it.

As Marko suggested I cleared the cache, updated said HTML.php file, reloaded and recleared the cache and attempted to submit the form again with recaptcha enabled on it.

IT WORKED! Hope this gets submitted as a solution soon for the next release. I appreciate your time and attention Marko!

Thanks for the reply @sterndata

Malwarebytes doesn’t report anything on that file either.

Reported it to Microsoft. We will see what they say…

You are correct, very much appreciated @joedolson

Checked my error logs.. all sorts of issues with this upgrade. Reverting Immediately.

The link and code line referencing https://gmpg.org/xfn/11 does not appear to effect whether or not a site is secure. My other sites show a “secure” symbol even though gmpg.org is just http. Rather, the issue may steam from a cached file. Clear your browser or server especially if you are using w3c. Also, your theme may have its own cache system which would also need to be cleaned. In any case, this is what worked for me. My site is now “secure” and gmpg.org is still just http. Hope this helps!

Thank you for taking the time to post a potential solution Bryan. Very thoughtful and considerate not to mention much appreciated.

Thank you! Excellent work.

Look for all recently modified files and remedy accordingly. The longer the infection goes undetected the worse the infection it appears. Four UltimateMember sites hacked thus far, lucky I have monitoring software installed. No idea if they are aware of the situation but I trust they will look into it as soon as possible. I can provide server logs.

All my sites with ultimate member are being hacked as well. To be exact, remote files are being uploaded like “uploads/.ini.php” along with other ‘image files’ not to mention they must have full directory control since they were able to CHMOD the wp-config.php file to 777 from 444 and add data to it. Error logs show: wp-content/plugins/ultimate-member/assets/dynamic_css/dynamic_profile.php on line 5 and line 6. Suggest everyone lock down or keep a watchful eye out until the developers discover what is going on and have a chance to resolve it.

This could also be occurring because the normal content #BEGIN WordPress and #END WordPress is missing from within the .htaccess file as well as failing to set the Permalinks under Settings. At least this is what happened to me and how I resolved it. Thank you @nicolaskulka for suggesting to look within .htaccess

• This reply was modified 6 years, 5 months ago by Manny Rodrigues.