pierreripka

Hi @wfpeter,

Thank you for you quick reply.
I can confirm the issue is still happening after cleaning site’s end cache.
I just sended the site diagnostic.

Thanks,
Pierre

Effectivement j’ai peur que notre problème passe un peu à la trappe puisque les équipes de YARPP doivent pour l’instant être concentrées sur cette faille de sécurité. Il faut toutefois préciser qu’elle ne peut être exploitée que par un compte utilisateur (de niveau abonné ou plus), donc les sites sans utilisateurs autres que l’admin / l’équipe de gestion et dont les inscriptions sont fermées ne sont pas exposés.

Bonjour,
Nous avons le même souci ici sur une vingtaines de sites.
Il s’agit d’un bug lié à la traduction fran?aise qui ne survient que sur PHP 8.0 et plus (les sites en 7.4 ne sont pas impactés).
Pour fixer temporairement le problème, vous pouvez supprimer les fichiers .po et .mo de YARPP dans le dossier /wp-content/languages/plugins.
En espérant que ce bug soit corrigé rapidement !

Hi @wfpeter,

Thanks for your reply, I will wait for this to be fixed!

Regards,
Pierre

The issue is back for the “Allowlisted services” field.
Nothing for “Scan Schedule” for the moment.

• This reply was modified 2 years, 6 months ago by pierreripka.

Hi @wftiffany,

Thank you for your reply and this fix.

I can confirm that the problem is solved for “Scan Schedule” and “Allowlisted services”.

However, there are still “Local changes” for the “Allowlisted IP addresses that bypass all rules” field.

The problem comes from the separator of IP addresses (comma on the plugin, space on your site).

I resynchronized all the sites several times and the “Local changes” status reappears systematically for this field.

Regards,
Pierre

• This reply was modified 2 years, 6 months ago by pierreripka.

Hi @wftiffany,

I already sent a report on September 5th.
I had then edited my message to make it clear to you, I don’t know why this modification was not saved, sorry!

I just sent 3 new reports from 3 other websites, so that you can compare them with each other if necessary.

Note that today, all the websites we have on Wordfence Central (128) have the “Local Changes” state, yet I resynchronized everything yesterday.

Thanks!

Hi @wftiffany,

I reopen this topic because the issue is happening again.
Except that this time, the template duplication does not solve anything.
After a few minutes, some of the websites have the “Local Changes” state again.

The fields where the problem occurs are always the same: “Scan Schedule”, “Allowlisted IP addresses that bypass all rules” and “Allowlisted services”:

Scan Schedule
- []
+ {}
Allowlisted IP addresses that bypass all rules
- 217.x.x.x,141.x.x.x
+ 217.x.x.x 141.x.x.x
Allowlisted services
- { "sucuri": true, "facebook": true, "uptimerobot": true, "statuscake": true, "managewp": true, "seznam": true }
+ {"sucuri":true,"facebook":true,"uptimerobot":true,"statuscake":true,"managewp":true,"seznam":true}

The bug seems to come from the separators (spaces, commas).

What can I do to prevent the “Local changes” state from constantly coming back?

Thanks for your help.

Hi,

Thank you for your reply!

This is exactly what I tried to do earlier today and everything seems to work, so far I don’t have any new “Local changes”.

Thanks!

I can confirm, the sites with a PHP version older than 7.3 are the only ones affected.

Same issue on multiple sites.

I’m experiencing the same issue:

Détails de l’erreur
======================
Une erreur de type E_ERROR a été causée dans la ligne 102 du fichier ***/www/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php. Message d’erreur : Uncaught TypeError: Argument 1 passed to Yoast\WP\SEO\Builders\Indexable_Hierarchy_Builder::build() must be an instance of Yoast\WP\SEO\Models\Indexable, boolean given, called in ***/www/wp-content/plugins/wordpress-seo/src/integrations/watchers/indexable-ancestor-watcher.php on line 175 and defined in ***/www/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php:102
Stack trace:
#0 ***/www/wp-content/plugins/wordpress-seo/src/integrations/watchers/indexable-ancestor-watcher.php(175): Yoast\WP\SEO\Builders\Indexable_Hierarchy_Builder->build(false)
#1 ***/www/wp-includes/class-wp-hook.php(294): Yoast\WP\SEO\Integrations\Watchers\Indexable_Ancestor_Watcher->build_post_hierarchy(6851)
#2 ***/www/wp-includes/class-wp-hook.php(316): WP_Hook->apply_filters(NULL, Array)
#3 ***/www/wp-includes/plugin.php(484): WP_Hook->do_action(Array)
#4 ***/www/wp-includes/taxonomy.php(2737): do_action('set_object_term...', 6851, Array, Ar

• This reply was modified 3 years, 12 months ago by pierreripka.

Hi Peter,

Thanks for your feedback.

Indeed, the login page is hidden with WPS Hide Login.
However this is not what is blocking the connection, I tried to deactivate the plugin and it does not change anything.
On the hundred other sites that I manage, this plugin is also installed and the connection is established without any issue.

I have seen this video before and share your point of view about that.
However, we were previously using iThemes Security which already hid the login pages and we wanted to avoid such an important change on every site switching to Wordfence, which would have been a bit complicated to explain to our clients in addition to taking a lot of time.

In any case, that’s not the issue here, so I reactivated the plugin.
Thanks again for your help, hope we will find out what is wrong.

Regards,
Pierre

Hi Peter,

Thanks for your reply.
I just sent the report as requested.

Regards,
Pierre

Hello,
Your issue seems to be related to your SSL certificate and not to Wordfence.
I advise you to contact your hosting provider to resolve this.
Regards