swissspaceboy
Forum Replies Created
-
Hi,
Great. Thanks for the fix. I will try it out.
Didier.
Forum: Plugins
In reply to: [Translation with DeepL API] FILTER_SANITIZE_STRING deprecatedThanks.
Forum: Plugins
In reply to: [Translation with DeepL API] FILTER_SANITIZE_STRING deprecatedAny reply on this?
Hi Peter,
This is only a PHP warning so there is no product impact for now. Thanks for the upcoming fix and keep up the good work.
Didier.
Here is a stacktrace of today:
[05-Jan-2026 23:57:50 UTC] --- Early Translation Load Detected ---
#0 /.../public_html/wp-includes/class-wp-hook.php(343): {closure}()
#1 /.../public_html/wp-includes/class-wp-hook.php(365): apply_filters()
#2 /.../public_html/wp-includes/plugin.php(522): do_action()
#3 /.../public_html/wp-includes/functions.php(6020): do_action()
#4 /.../public_html/wp-includes/l10n.php(1381): _doing_it_wrong()
#5 /.../public_html/wp-includes/l10n.php(1419): _load_textdomain_just_in_time()
#6 /.../public_html/wp-includes/l10n.php(195): get_translations_for_domain()
#7 /.../public_html/wp-includes/l10n.php(307): translate()
#8 /.../public_html/wp-content/plugins/wordfence/waf/wfWAFBlockI18n.php(46): __()
#9 /.../public_html/wp-content/plugins/wordfence/waf/wfWAFBlockI18n.php(8): getBlockFormatString()
#10 /.../public_html/wp-content/plugins/wordfence/waf/wfWAFBlockI18n.php(28): formatBlockDescription()
#11 /.../public_html/wp-content/plugins/wordfence/lib/wfLog.php(720): getTranslatedBlockDescription()
#12 /.../public_html/wp-content/plugins/wordfence/lib/wordfenceClass.php(2451): do503()
#13 /.../public_html/wp-includes/class-wp-hook.php(341): veryFirstAction()
#14 /.../public_html/wp-includes/class-wp-hook.php(365): apply_filters()
#15 /.../public_html/wp-includes/plugin.php(522): do_action()
#16 /.../public_html/wp-settings.php(593): do_action()
#17 /.../public_html/wp-config.php(111): require_once()
#18 /.../public_html/wp-load.php(50): require_once()
#19 /.../public_html/wp-login.php(12): require()Hi,
I only get this one-liner in the debug log. I was not connected to the admin backend so I am unable to tell what happened in parallel. I enabled the stacktrace. I have this message daily so we’ll see quite fast.
More to come. Didier.
Hi Peter,
oh yes, this is repeating on multiple website long after any upgrade of WP or WF. This is an error of 04-Jan. I can enable the stacktrace if it would help you.:
Plugin version: 8.1.4
[04-Jan-2026 16:42:22 UTC] PHP Notice: Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>wordfence</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. Please see <a href=”https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/”>Debugging in WordPress</a> for more information. (This message was added in version 6.7.0.) in /…/wp-includes/functions.php on line 6131
Forum: Plugins
In reply to: [Broken Link Checker] WP error undefined variableThanks. Didier.
Forum: Plugins
In reply to: [Bold Timeline Lite] 1.2.6 fails during installationHello,
I tried with version 1.2.7 and still the same crash. Here the analysis of Claude AI on this bug:
I can see the problem. There’s a class name conflict between your Bold Timeline Lite plugin and your Showcase theme. Both are trying to declare a class called
CssCrush\Functions.Now I understand the problem completely. Both your Showcase theme and the Bold Timeline Lite plugin include their own copies of CSS Crush library files, and they’re trying to declare the same classes in the
CssCrushnamespace.Your theme has:
/wp-content/themes/showcase/php/BTCrushFunctions.phpThe plugin has:/wp-content/plugins/bold-timeline-lite/BTCrushFunctions.phpBoth try to declare
CssCrush\Functionsclass, causing a fatal error.Hello,
Following the update to 7.11.1, my permalinks got broken again. Most of my pages are pointing to the blog page. I applied the fix that you proposed to switch to plain, save, and change to postname + save. Let’s see how this works during the next plugin update if my links get broken.
You got a chance to look at my diag log that I have sent you?
Thanks,
Didier.
Thanks.
Yes, we disabled this rule in our WAF. I have no warning message anymore.
We can close this ticket.
Didier.
Hello,
Not better with the latest version 4.5.0. The warning message is still present. ModSec firewall is enabled on this site, with the rule enabled.
Didier.
Hi,
So this is firewall rule that gets fired for your plugin:
[Tue Nov 14 02:09:43.465445 2023] [error] [client 185.67.193.35] ModSecurity: Access denied with code 403, [Rule: 'MATCHED_VAR' '@rx [A-Z]'] [id "77318019"] [msg "IM360 WAF: Authenticated Privilege Escalation in All in One SEO < 4.1.5.3 plugin for WordPress (CVE-2021-25036)||T:APACHE||MV:/wp-json/aioseo/v1/||"] [severity "CRITICAL"] [tag "wp_plugin"] [hostname "www.talentbox.solutions"] [uri "/wp-json/aioseo/v1/"], referer:I am using a much later version of the plugin, so this rule is not valid anymore right? Can you do something with this? How to proceed further?
At least you know that all users with ModSec enabled and this standard rule, will have problems with your plugin.
Didier.
- This reply was modified 2 years, 4 months ago by swissspaceboy.
Hi,
We found the problem. It is the mod_Security module that gives the 403 forbidden error. This module is enabled by default by the hoster.
Can you check that please for the plugin to support the ModSecurity firewall?
Thanks,
Didier.
I would gladly whitelist this URL, if I knew where it is coming from. Interesting to see that the other URL is working fine. I will check with my hoster if they have an idea.