[bug] Can't attach media descriptions #510

Closed
opened 2023-03-13 23:43:37 +00:00 by fedward · 5 comments

Your setup

From source

Extra details

FreeBSD 13.1

Version

2023.03

PostgreSQL version

14.6

What were you trying to do?

I cannot attach media descriptions to any media, whether during initial upload or when editing an existing post.

What did you expect to happen?

I should be able to add media descriptions. It worked before I upgraded to 2023.03.

What actually happened?

In the UI I get this message: "Error: Failed to update media, try again." If I look at the javascript console in the browser I see a 403 error on api/v1/media/OBJECTID.

Logs

Even with logging turned up to debug there is no log event associated with this issue.

Severity

I cannot use the software

Have you searched for this issue?

  • I have double-checked and have not found this issue mentioned anywhere.
### Your setup From source ### Extra details FreeBSD 13.1 ### Version 2023.03 ### PostgreSQL version 14.6 ### What were you trying to do? I cannot attach media descriptions to any media, whether during initial upload or when editing an existing post. ### What did you expect to happen? I should be able to add media descriptions. It worked before I upgraded to 2023.03. ### What actually happened? In the UI I get this message: "Error: Failed to update media, try again." If I look at the javascript console in the browser I see a 403 error on api/v1/media/OBJECTID. ### Logs ```shell Even with logging turned up to debug there is no log event associated with this issue. ``` ### Severity I cannot use the software ### Have you searched for this issue? - [x] I have double-checked and have not found this issue mentioned anywhere.
fedward added the
bug
label 2023-03-13 23:43:37 +00:00
fedward changed title from [bug] to [bug] Can't attach media descriptions 2023-03-13 23:43:53 +00:00

I cannot replicate this issue, media description works fine on that release for me
is it limited to a specific image?

I cannot replicate this issue, media description works fine on that release for me is it limited to a specific image?
Author

It is not limited to a single image or even media type (I've tried jpeg, gif, and png).

Roughly concurrently with the upgrade I went in to "fix" my frontend configuration, managed to corrupt it, and had to export my configuration from the DB, edit the text file, and load it back into the DB. Everything else works so I don't think it's a contributing factor, but it's a thing that happened so maybe it is?

Anything I should look for? Any way to get that API endpoint to log the error?

It is not limited to a single image or even media type (I've tried jpeg, gif, and png). Roughly concurrently with the upgrade I went in to "fix" my frontend configuration, managed to corrupt it, and had to export my configuration from the DB, edit the text file, and load it back into the DB. Everything else works so I don't think it's a contributing factor, but it's a thing that happened so maybe it is? Anything I should look for? Any way to get that API endpoint to log the error?

yes, things to check include which filters you run over uploaded media

yes, things to check include which filters you run over uploaded media
Author

Current setting is:

config :pleroma, Pleroma.Upload, [uploader: Pleroma.Uploaders.Local, base_url: "https://[DOMAIN]/media", filters: [Pleroma.Upload.Filter.Dedupe, Pleroma.Upload.Filter.Exiftool, Pleroma.Upload.Filter.AnalyzeMetadata, Pleroma.Upload.Filter.AnonymizeFilename]]

But it happens with every combination of some or none that I've tried.

Current setting is: config :pleroma, Pleroma.Upload, [uploader: Pleroma.Uploaders.Local, base_url: "https://[DOMAIN]/media", filters: [Pleroma.Upload.Filter.Dedupe, Pleroma.Upload.Filter.Exiftool, Pleroma.Upload.Filter.AnalyzeMetadata, Pleroma.Upload.Filter.AnonymizeFilename]] But it happens with every combination of some or none that I've tried.
Author

Definitely because of the export and import, it turns out. The Pleroma.Web.Endpoint configuration was lost in the round trip.

Definitely because of the export and import, it turns out. The Pleroma.Web.Endpoint configuration was lost in the round trip.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: AkkomaGang/akkoma#510
No description provided.