Audit Log Pro

MikeJones

Any onetime purchase options?

clarkwinkelmann

MikeJones not at the moment, no. But I might add additional options in the future.

clarkwinkelmann

Version 1.4.2 - August 25, 2021

Fix Flarum boot error if Flags extension has been uninstalled via Composer.

matteocontrini

Hi @clarkwinkelmann, could you show us a screenshot of how the audit logs look in the discussion and user profile pages? Thanks!

clarkwinkelmann

matteocontrini sure! I don't have realistic data, but here are some screenshots from my local test website:

It's basically the same UI as the admin, but with a filter pre-set behind the scenes, and it's inside a modal.

I'll make a video presentation for this extension in the not too distant future.

Excuse the avatar, it's because I was re-creating the lost GIF for this discussion 😇

matteocontrini

clarkwinkelmann great, thanks!

Does the extension respect the "view IP address" permission, or does it show the IP address to all groups allowed to view the audit?

clarkwinkelmann

matteocontrini it doesn't use "view IP address" at the moment. Everyone who can see the log sees the full content of the log, including the IP.

I could add additional access permissions if there's a need for it.

matteocontrini

clarkwinkelmann that would be useful, yes, since it would otherwise be complicated to have IP addresses shown for example to moderators, for privacy-related compliance.

If that permission could be implemented without too much effort I would subscribe. 🙂 No hurry though. Thank you!

clarkwinkelmann

Version 1.5.0 - February 28, 2022

Add limited access permission and settings. This lets you give access to moderators to only a custom selection of actions and/or IP.
Add forum-side log access via session dropdown for users who cannot access admin panel.
Add optional IP country indicator. See documentation for how to enable.

This version requires Flarum version 1.2 or higher.

Price drop

A new 30 USD lifetime license is now offered in place of the previous 40 USD/year.

matteocontrini

If I have the free version installed, how do I upgrade to pro? Should I disable and uninstall the free version before installing the pro one?

Thanks!

clarkwinkelmann

matteocontrini safest way is to disable old extension, remove it with Composer, install new one with Composer, and finally enable new one.

But you can also simply run the composer require command for the new one, Composer will automatically remove the old one. Then enable the new one.

Do not click "Uninstall" in the admin panel, the 2 extensions use the same database table, and the existing data will be preserved if you just remove the old extension and add the new one.

clarkwinkelmann

Version 1.5.1 - March 22, 2022

Fix compatibility issues with some admin themes.

GreXXL

When running composer commands I receive the following warning:

Warning: the packages key 'kilowhat/flarum-ext-audit-pro' doesn't match the name defined in the package metadata 'kilowhat/flarum-ext-audit' in repository https://extiverse.com/composer

I don't recall this being an issue previously. I think it came up when the name change happened. Is this something that I misconfigured or something out of my control?

Also just to leave it here as well - adding FoF Merge would be awesome in a future update 🙂
What I didn't mention so far but also might be interesting would be to see events from Moderator Warnings in Audit Log.

clarkwinkelmann

GreXXL Warning: the packages key 'kilowhat/flarum-ext-audit-pro' doesn't match the name defined in the package metadata

Composer might be complaining about an older release. I didn't delete the previous version tags from before the package rename so Composer will probably still see them while evaluating which version to choose. All the recent versions have the correct metadata though. So it should be safe to ignore.

Merge and Moderator Warnings are definitely on the shortlist for next update!

GreXXL

clarkwinkelmann Merge and Moderator Warnings are definitely on the shortlist for next update!

Is there an ETA for the next version yet? 🙂

GreXXL

clarkwinkelmann Moderator Warnings are definitely on the shortlist for next update!

Hey Clark, Merge has already been included - is there any chance that we can see moderator warning also be included in a future version soon? 🙂

pkernstock

I'm seeing the same error like @GreXXL on all updates too, while being up-to-date with all packages and with the most recent audit extension release. Completely clearing the composer cache didn't change anything.

When checking composer.lock, there's a mention of flarum-ext-audit but not sure if that's related:

        {
            "name": "kilowhat/flarum-ext-audit-pro",
            "version": "1.5.1",
[...]
            "require": {
                "ext-json": "*",
                "flarum/core": "^1.2",
                "maxmind-db/reader": "^1.11"
            },
            "replace": {
                "kilowhat/flarum-ext-audit": "*",
                "kilowhat/flarum-ext-audit-free": "*"
            },

It's just a minor annoyance, so it's not too bad.

clarkwinkelmann

pkernstock it's expected to have the old name listed in replace.

I'm pretty sure I know what's causing the warning but I haven't decided how to fix it. I need to delete older releases from Extiverse and it seems I will have to delete the releases from my private GitHub repo to achieve it. I need to do some backing up before I can delete those from the main codebase.

QyInvoLing

Hello! I'm interested in whether this extension can log the event of user register with Fof doorman's invite code?

clarkwinkelmann

QyInvoLing not at the moment, but it's a feature I could add.

I see Doorman already logs the invitation code used internally, it can be found in the invite_code column on the users table.

I could log it similarly to a first social login (?).

QyInvoLing

clarkwinkelmann OK, thank you!

clarkwinkelmann

GreXXL I haven't started work on it yet but I will try to push an update with this before the end of the year.

clarkwinkelmann

Version 1.7.0 - August 8, 2023

Fix for possible MySQL errors if another extension added id or slug columns to intermediate relationship tables.
Fix for possible duplicate Nickname change logs if other extensions perform additional database queries during the same lifecycle.
[pro only] Log events from FoF Merge Discussions extension.
[pro only] Restore 1.5.1 fixes that were accidentally reverted in 1.6.0.

Jeff-B fixes your issue
GreXXL FoF Merge Discussions is now included

« Previous Page Next Page »