New user cannot upload images?

AI-generated summary

A discussion in the Support category addresses an issue where new users cannot upload images, despite the system allowing one image at trust level 0. Paul_King1 reports the restriction is preventing new users from uploading any images, even though the setting implies one should be allowed. IAmGav asks for the error message, which ChrisBeach identifies as “Sorry, new members can not upload images.” ChrisBeach shares that changing the newuser_max_embedded_media setting from 9999 to 25 resolved the issue, suggesting a possible bug in the setting migration. codinghorror confirms a known bug and recommends updating to the latest version to fix it.

How can I change this setting please?

It says:

Users at trust level 0 cannot …

  • Send personal messages to other users
  • “Reply as new topic” via Link button (UI removed)
  • Flag posts
  • Post more than 1 image <<<<<<<<<<<<<<<<<<<<<<<

So this means level 0 should be allowed to post 1 image , right? But it wont allow my new users to upload any images at all. I haven’t adjusted any settings at all.

what’s the error msg that the user get when trying ?

A new member just reported the same issue on my forum.

The error is “Sorry, new members can not upload images.”

Defined here js.post.errors.image_upload_not_allowed_for_new_user

I have no idea how long my site’s had this restriction, and how I can lift it :cold_sweat:

My newuser_max_embedded_media setting was 9999.

I just tried changing this to 25 and I believe the act of making this change has resolved the problem (even though I reduced the allowance!).

I tried impersonating the user and posting an image before and after the setting change.

So I think there’s still some kind of bug here, but for a workaround, try altering that setting.

I’ve had a trawl through the code commits and I think the following change might be related (perhaps my customised setting was stored against the old setting key, and this wasn’t “migrated” to a new setting key?):

https://github.com/discourse/discourse/commit/6391db5921d96f936ac2dd2e60bc86424ef75d95

There was definitely a bug around this, updating to latest should fix it.