Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter hrkdevy

    (@hrkdevy)

    Thank you very much for your prompt response and for releasing the update!
    I appreciate your efforts in addressing this issue.
    I will update to the latest version and let you know if I encounter any further problems.

    Thread Starter hrkdevy

    (@hrkdevy)

    Hi @nigelrsb ,

    Thank you for the update.

    I appreciate your team looking into this. Just to help with our planning, would it be possible to get an approximate timeline for when the fix might be released?

    Looking forward to hearing from you.

    Thanks,again!!

    Thread Starter hrkdevy

    (@hrkdevy)

    Hi again,

    Just following up on this issue — I understand from the earlier thread that a fix was planned or possibly already implemented.

    Would you mind sharing how the fix is progressing?
    Is there an estimated timeline for when this warning will be fully resolved in the plugin?

    I really appreciate all your hard work and just wanted to check in politely.
    Happy to provide any additional details from my environment if it helps.

    Thanks again for your continued support!

    Best regards,
    HRKDevy

    Thread Starter hrkdevy

    (@hrkdevy)

    Hi, thank you for your reply!

    I’ve confirmed that I’m using the latest versions of both:

    WordPress Core: 6.7.2

    WP Activity Log: 5.3.4.1

    Query Monitor: 3.17.2

    However, the notice still appears.
    When I activate the Query Monitor plugin, the following message is shown under the “Doing it Wrong” section:

    Message:
    Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-security-audit-log 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 init action or later.

    Call:
    _load_textdomain_just_in_time()
    Plugin:
    wp-security-audit-log

    I just wanted to check again because, although I saw that this issue had been marked as resolved in a previous thread, it still seems to be happening even with the latest version.

    Please let me know if there’s anything else I can do to help troubleshoot or clarify.

    Thanks again!

    • This reply was modified 1 year ago by hrkdevy.
    Thread Starter hrkdevy

    (@hrkdevy)

    Hello, and thank you for your continued work on the User Access Manager plugin.

    I saw this pull request on GitHub, and I really appreciate the effort the contributor put into addressing the issue.

    May I ask if this has already been merged or included in the latest release?
    Has the issue been resolved, or is it still under review?

    Many thanks in advance for any updates, and again, thank you to the contributor for the helpful work!

Viewing 5 replies - 1 through 5 (of 5 total)