Components pass the database table prefix to the user activity log. Probably not worth doing.
See #36889 (comment)
To reproduce the problem, just play with the task scheduler component in the plan to create / execute / unlock the task, then look in the action log, having previously checked the scheduler component in the action log settings (by the way, if I don’t confuse anything from memory, this is the only DISABLED component in the action log after installing Joomla).
Localhost, PHP 7.2, MariaDB 10.3, One of the latest nightly builds of Joomla 4.1.
Labels |
Added:
No Code Attached Yet
|
I wrote carefully :)
Probably, this should not be done, given that this has never been noticed in the work of other components.
At first glance, it's hard for me to imagine a situation with a security breach, even if NOT a super administrator (but just an administrator) knows the prefix of the database tables.
I think that more experienced developers will be able to appreciate this behavior. If I'm wrong, just close.
You are correct it should not show the prefix
I am unable to replicate. Please provide steps to reproduce.
From your screenshot it looks odd because there are 4 logs of a checkin and only one of those does not have the prefix removed.
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2022-01-30 09:46:25 |
Closed_By | ⇒ | Kostelano |
Hmmm, now I have the prefix displayed in any component, not just the scheduler. I have not yet determined what sequence in the Joomla control panel should be done to get this behavior.
I'll close this for now.
@Kostelano Can you reopen please. I can replicate it.
Check-in via buttons (close) or lock icon works fine
Check-in via Global Check-in not
Actionslogs:
Also, it's not specific to task scheduler. I've tested it with the contact component.
Status | Closed | ⇒ | New |
Closed_Date | 2022-01-30 09:46:25 | ⇒ | |
Closed_By | Kostelano | ⇒ |
Title |
|
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2022-03-03 18:07:06 |
Closed_By | ⇒ | Kostelano |
May you elaborate as of why this shouldnt be done?