Christian Rodríguez

@jeremy, isn’t better to fix this issue in further updates instead letting people fixing this manually?

Thanks!

Solved in my last update ??

Thank you so much!

Same as @adam Nowak. I’m using a site with SSL + All In One WP Security plugin and is getting the same error from months ago:

Fatal error: Call to undefined function get_current_screen() in /home/xxxxxxx/public_html/wp-content/plugins/wordpress-seo/inc/wpseo-non-ajax-functions.php on line 467

Will the next update fix this?

Same here.

1. Tab “Search & Replace”.
2. Filling both fields (“Search for” and “Replace with”).
3. Select all tables.
4. Disable “Dry run”.
5. Check ” Save changes to Database”.
6. Pressing “Do Search & Replace”.
7. Does nothing.

All my plugins & WordPress are up to date ??

?Hola! ?Muchas gracias!

We’ve purchased the plugin in the website Acompany.es, so we’re waiting for this great new changes.

Thanks for the assistance.

Greetings from Barcelona!

Chris.

Hi!

2 very important aspects in this point:

1. It is better to let the user translate all the available fields.
2. The spanish is the 2nd native language in the world! ??

Thanks!

Hello Art,

All ok! So I’ll switch this topic to resolved.

Thank you so much for your feedback!

Hi @abbycallard! There’s a “solution” that I don’t like, but is a try while WordPress is fixing this issue by using Firefox. Firefox doesn’t paste this code. Just magic!

But I prefer to use Chrome : (

I don’t have any issue yet. In fact, it wasn’t related with the image editing. Just about blocking the Linkedin bot.

I wrote this post just to contribute enhancing the plugin. I solved this problem by my own way by disabling the 5G Blacklist and adding the original 5g Blacklist by hand in the htaccess.

I know this part. I’m just reporting this issue if you want to consider to fix this because the users of AIOWSF we cannot disable all our plugins to use this feature ?? I’m getting this error in multiple sites with different hostings and plugins, so I’m sure is a bug from the security plugin.

Thanks for hearing.

Ciao Marco! Thanks for helping. This checkbox was empty, but I’ve set 3 months from now.

Grazie mile!

@stephdotnet you mod rocks! Thanks for helping : )

I thought about it, but the number of probabilities to get a case as you described is very low. In fact, I never seen an email from a domain with special characters (this kind of domains aren’t a good idea).

As I tested, by the moment, removing the [name] field just worked fine for me : )

Solved. As I don’t like too much this way, that’s what worked for me:

Additional Headers: Reply-to: <[email]>

As the characters of the [name] field are causing this problem, I just removed this value from the “Reply-to” header. But maybe Takayuki has a most clean or optimized solution.

Same issue here.

To: [email protected]
From: [name] <[email protected]>
Additional Headers: Reply-to: [name] <[email]>

When I get a new message from a user called “Alberto Fernández” as [name] value, the character “á” causes an error that disables the [email] value, and the Reply-to value changes to [email protected]

Thanks for hearin, Takayuki! : )