make sense to me

Instead of writing the code to do that (needs new db columns etc) why not take advantage of user action logs?

We absolutely can. I was just thinking it would make more sense in the
extensions view as an over view and part of the extension ? Since you are
usually there anyway.

I suppose technically it should be in the user actions logs if they are
setup correctly.

On Thu, 18 Jul 2019 at 08:52, Brian Teeman notifications@github.com wrote:

Instead of writing the code to do that (needs new db columns etc) why not
take advantage of user action logs?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/joomla/joomla-cms/issues/25627?email_source=notifications&email_token=AAKWBFTO3DSCNAAJRWQMBT3QAAOMTA5CNFSM4IEX4GO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2HUPYY#issuecomment-512706531,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAKWBFQQUGLL57IXKKREIODQAAOMTANCNFSM4IEX4GOQ
.

not sure we can avoid to add new columns to the db (the actions log can be disabled)

Sounds like an action log thing to me, not something that belongs as part of the #__extensions table schema.

@mbabker Disable action log? Do you have any idea what consequences it might have on whole site? I bet you dont! Otherwise you wouldnt write something as absurdish as this.

@mbabker Disable action log? Do you have any idea what consequences it might have on whole site? I bet you dont! Otherwise you wouldnt write something as absurdish as this.

Given Michael knows the insides out of Joomla! of the top of his head and was the main release lead for way too long I'd say he knows what he's talking about ;-).

But he hasn't day disable action logs? but just to use it instead of being part of the core extensions table...

Trolling and sarcasm aside, I actually would know a little bit about how the action log component works. Logging the time an extension was installed or last updated is not so critical that it needs to be handled in the #__extensions table and related PHP APIs (and yes I get that to some people it's more urgent than others, but IMO the action logging system fits this use case perfectly for those who desire it).

i'm really sorry if my previous comment #25627 (comment) about the option to disable action log have raised this missunderstanding, i'll explore a way to deal this with user action logs

Folks, please do not reply to trolls. Just ignore them.

after some dirty hack to the com_patchtester manifest to let it point on localhost with a fake new version & the corresponding hack to the table #__update_site

so after my silly test i think we already have this feature .....

@tonypartridge can you consider this issue as closed ?