Skip to main content
Craft CMS

Return to Answer

edited body
Source Link
Brad Bell ♦
Brad Bell ♦
  • 67.6k
  • 6
  • 75
  • 145

I'd classify this as a feature request for a "Replace Asset" user permission.

I think it'd be a security related "privilege escalation" bug if we supported it and you found a way to get around it or it just wasn't working.

For the record, we do check existing permissions on file upload and we also verify that the file you want to replace with it with is allowed within the allowedFileExtensions and extraAllowedFileExtensions config settings.

I'd classify this as a feature request for a "Replace Asset" user permission.

I think it'd be a security related "privilege escalation" bug if we supported it and you found a way to get around it or it just wasn't working.

For the record, we do check existing permissions on file upload and we also verify that the file you want to replace with it with is within the allowedFileExtensions and extraAllowedFileExtensions config settings.

I'd classify this as a feature request for a "Replace Asset" user permission.

I think it'd be a security related "privilege escalation" bug if we supported it and you found a way to get around it or it just wasn't working.

For the record, we do check existing permissions on file upload and we also verify that the file you want to replace with is allowed within the allowedFileExtensions and extraAllowedFileExtensions config settings.

Source Link
Brad Bell ♦
Brad Bell ♦
  • 67.6k
  • 6
  • 75
  • 145

I'd classify this as a feature request for a "Replace Asset" user permission.

I think it'd be a security related "privilege escalation" bug if we supported it and you found a way to get around it or it just wasn't working.

For the record, we do check existing permissions on file upload and we also verify that the file you want to replace with it with is within the allowedFileExtensions and extraAllowedFileExtensions config settings.