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

MediaService CreateMediaWithIdentity is generating malformed History log messages #17738

Open
skidmow opened this issue Dec 5, 2024 · 2 comments

Comments

@skidmow
Copy link
Contributor

skidmow commented Dec 5, 2024

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

13.5.2

Bug summary

If you use the Umbraco MediaService CreateMediaWithIdentity method to create a media item, the media item will be generated with a malformed history, displaying:

{{item.logType}} {{item.comment}}

See below:
Screenshot 2024-12-04 at 15 49 43

Specifics

No response

Steps to reproduce

  1. Follow instructions here to create media programatically, but use the CreateMediaWithIdentity method instead of CreateMedia. Use the default user (userId = -1), which should be the administrator account.
  2. Login to the back-office and view the media item you created
  3. Check the history on the info tab

Expected result / actual result

Expected Result
The history shows a log message for Media Saved

Actual Result
The history shows a malformed message {{item.logType}} {{item.comment}}

Copy link

github-actions bot commented Dec 5, 2024

Hi there @skidmow!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

  • We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
  • If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
  • We'll replicate the issue to ensure that the problem is as described.
  • We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

@NguyenThuyLan
Copy link
Contributor

I was able to reproduce it on v13.5.2.
Tested on v14.3.1 and v15.1.0-rc2, the log is displayed like this
image

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

2 participants