mojamba

Thanks for the update and fix.

Thanks

I have a few different cron jobs. The wp-cron.php job is as you say via a direct call to PHP but the others are via wget. I’m not sure if that will make a difference on your end or not.

Yes, I do. I actually disabled the internal WP cron and run it via my server crontab because I have a plugin that runs better that way. I run it every 5 minutes I think. I also have a daily admin script I run and have a separate cronjob for that. Though, that one doesn’t align with the timestamp so I am guessing it isn’t related.

I just re-checked the errors log file and I do see this entry. Not sure if it’s your full-stack trace or something else, but:

[23-Jul-2024 13:09:50 UTC] Array
(
 [0] => Array
    (
        [file] => .../public_html/wp-content/plugins/all-in-one-wp-security-and-firewall/classes/firewall/rule/rules/general/rule-advanced-character-filter.php
        [line] => 46
        [function] => contains_pattern
        [class] => AIOWPS\Firewall\Rule_Utils
        [type] => ::
    )

[1] => Array
    (
        [file] => .../public_html/wp-content/plugins/all-in-one-wp-security-and-firewall/classes/firewall/rule/wp-security-firewall-rule.php
        [line] => 73
        [function] => is_satisfied
        [class] => AIOWPS\Firewall\Rule_Advanced_Character_Filter
        [type] => ->
    )

[2] => Array
    (
        [file] => .../public_html/wp-content/plugins/all-in-one-wp-security-and-firewall/classes/firewall/family/wp-security-firewall-family.php
        [line] => 72
        [function] => apply
        [class] => AIOWPS\Firewall\Rule
        [type] => ->
    )

[3] => Array
    (
        [file] => .../public_html/wp-content/plugins/all-in-one-wp-security-and-firewall/classes/firewall/wp-security-firewall-loader.php
        [line] => 52
        [function] => apply_all
        [class] => AIOWPS\Firewall\Family
        [type] => ->
    )

[4] => Array
    (
        [file] => .../public_html/wp-content/plugins/all-in-one-wp-security-and-firewall/classes/firewall/wp-security-firewall.php
        [line] => 19
        [function] => load_firewall
        [class] => AIOWPS\Firewall\Loader
        [type] => ->
    )

[5] => Array
    (
        [file] => .../public_html/aios-bootstrap.php
        [line] => 20
        [args] => Array
            (
                [0] => .../public_html/wp-content/plugins/all-in-one-wp-security-and-firewall/classes/firewall/wp-security-firewall.php
            )

        [function] => include_once
    )

)

The timestamp is the same as for the shortened PHP Deprecated error message. I also just realized that rather than lots of deprecated error messages at different times, I see 76 identical error line entries all with the exact same timestamp.

I am still getting regular errors, but not are logged with stack trace. Perhaps there is a code error for enabling that?

Yes, I have both of those config settings enabled and I am getting an error log generated in the wp-content folder but it’s not the place that this particular error is getting logged and it’s not a full stack trace.

I have added that code. In fact, the new error shows the line is line 27 where before it was line 23. But, no error showing up in the wp-content/debug.log file. The errors are being recorded in the main public_html/PHP_errors.log file instead, and no full stack details.

Good to hear. Thanks for the update/reply.

UPDATE: After upgrading my server to PHP 8.1 the problem no longer exists. Thanks for the help.

• This reply was modified 1 year, 2 months ago by mojamba.

Thanks for the reply. That server is behind on PHP version but it is 7.4 which you seem to be saying should be fine. I just updated it to 8 so I’ll see if that makes any difference and report back (there are no plugin updates needed now so cannot test this moment).

Sorry, I was a bit busy and since I had downgraded to the previous version the problem went away. To double-check before opening a ticket I just upgraded (now to 4.9.2) and the problem no longer exists. So, I don’t know if it was a change you made in the latest update or something else, but it seems like things are OK now.

That’s really strange because the site I am having a problem with is not using the paid version. Or, perhaps I uploaded a copy of the paid version without realizing it but am still able to use that version in free mode? Now I am a bit confused. So, I am not sure if I can/should post a ticket with Tribulant in this situation or not (because my paid sites are not having a problem).

Actually, I use the paid version on two sites and the free version on a third. The paid version is on a server already upgraded to PHP8+ but the free version is still on PHP 7+ If you see the error message I included it is quite clearly your script not an incompatibility with another plugin. Did you try to verify on a user environment of PHP 7.x? If not, of course you will not replicate the error.

I have it on all my sites so I will just manually update a couple of them and see and wait for proper release of next version for the rest. But, one question occurs to me: if your solution is to just not log the timeout, there is still a large (4s) timeout occurring. Is that slowing render of the page for users?