Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Action Logs for com_contact frontend actions are not recorded #44589

Closed
AndySDH opened this issue Dec 7, 2024 · 5 comments
Closed

Action Logs for com_contact frontend actions are not recorded #44589

AndySDH opened this issue Dec 7, 2024 · 5 comments

Comments

@AndySDH
Copy link
Contributor

AndySDH commented Dec 7, 2024

Steps to reproduce the issue

  • Make sure the Contacts component is enabled in the User Action Logs global configuration
  • Display a Contact via the frontend (eg. via menu item)
  • Edit the contact and save

Expected result

  • An action for the contact being updated should be added to the Action Log

Actual result

  • No action is recorded.

(On the other hand the Action is recorded normally if the contact is edited through the backend)

System information (as much as possible)

  • Latest Joomla 5 version.
@AndySDH AndySDH changed the title Action Losg for com_contact frontend actions are not recorded Action Logs for com_contact frontend actions are not recorded Dec 7, 2024
@fgsw
Copy link

fgsw commented Dec 8, 2024

Can't confirm; used default values of User Action Logs on a multilanguage site (en-gb menu+contact). (see #44589 (comment))

@AndySDH
Copy link
Contributor Author

AndySDH commented Dec 8, 2024

Follow the test instructions. It's impossible that you can't confirm.

@brianteeman
Copy link
Contributor

I can confirm that when editing a contact in the front end it is not logged in the UAL as shown in the image below where I edited a contact in the admin then logged in to the front end and did the same

Image

@alikon alikon added the Feature label Dec 9, 2024
@fgsw
Copy link

fgsw commented Dec 9, 2024

@brianteeman Thanks for the screenshot. Now i understand the issue and can confirm.

Sorry for false alarm @AndySDH.

@alikon
Copy link
Contributor

alikon commented Dec 9, 2024

please test #44596

@alikon alikon closed this as completed Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants