Addon Change Log

Addon Change Log v1.1.5

No permission to download

Wutime

Well-known member
Wutime submitted a new resource:

Addon Change Log - Logs GUI-based add-on installs, upgrades and uninstalls thru the XenForo logger

Logs GUI-based add-on installs, upgrades and uninstalls thru the XenForo logger.

I wanted a way to share community updates with the community to show that the forum is kept up to date. This logger is the first step to building something to share with the specific usergroups and to ensure the data is currently being logged.

Each entry includes a linked username and relevant metadata for easy auditing.


💡 Use Cases​

  • Track add-on changes made by all...

Read more about this resource...
 
CLI-based installs, upgrades, and uninstalls are not logged (by XenForo design)
Hmm ... they are logged and I don't see any reason why that shouldn't work?

The admin route is missing the section context and the admin controller does not check the permission, eg. any admin can view the log (by directly accessing the link).

License seems confusing, README.md states it's MIT but the conditions in LICENSE are completely different.

What are AddonLog.txt, addontxt.py and opt/homebrew/var/www/xf-current/cmd.php meant for?
I'd keep one format for everyting (either Text or Markdown, but not mixed).
 
Last edited:
Hmm ... they are logged and I don't see any reason why that shouldn't work?
Currently CLI installs aren’t logged since there’s no event listener for them — it was only meant for GUI installs. The project’s on GitHub, so you’re welcome to commit the change.
The admin route is missing the section context and the admin controller does not check the permission, eg. any admin can view the log (by directly accessing the link).
Would have thought if they're an admin they're welcome; added $this->assertAdminPermission('viewLogs'); to the controller
License seems confusing, README.md states it's MIT but the conditions in LICENSE are completely different.
Thanks, removed the LICENSE; sticking with the README.md
What are AddonLog.txt, addontxt.py and opt/homebrew/var/www/xf-current/cmd.php meant for?
I'd keep one format for everyting (either Text or Markdown, but not mixed).
Garbage, removed with build.json in next release
 
Currently CLI installs aren’t logged since there’s no event listener for them — it was only meant for GUI installs. The project’s on GitHub, so you’re welcome to commit the change.
I didn't test install yet, but at least upgrade and rebuild are already logged via CLI - no need for any changes.
So I'd assume install and uninstall would also work as the events are fired by the AddOn class which is used for both GUI and CLI.
 
Well, I upgraded this Add-on via CLI and it was logged, so I am pretty sure it does work just fine for all events but I'd have to test this (with development turned off) to be sure.
 
Last edited:
Your online store doesn't handle free add-ons very well. I have to place a new order for each version you release. It would be nice to just have this on XF.com since it's free.
 
Your online store doesn't handle free add-ons very well. I have to place a new order for each version you release. It would be nice to just have this on XF.com since it's free.
Oh, I didn't realize. That's not intentional - thanks for letting me know.
 
Your online store doesn't handle free add-ons very well. I have to place a new order for each version you release. It would be nice to just have this on XF.com since it's free.
This is fixed now; each new release will be added to your existing order.

Furthermore, simply clicking "go to download" here on xenforo should immediately force the download to you (provided you've "remembered login").

That should make it a one-click download to save you time
 
This is fixed now; each new release will be added to your existing order.

Furthermore, simply clicking "go to download" here on xenforo should immediately force the download to you (provided you've "remembered login").

That should make it a one-click download to save you time

Thank you.
 
Back
Top Bottom