# Resource dropwell (bug)

**URL:** <https://forums.realmacsoftware.com/t/resource-dropwell-bug/46727>\
**Category:** RapidWeaver Elements\
**Created:** [March 14, 2025, 3:45am UTC](https://forums.realmacsoftware.com/t/resource-dropwell-bug/46727 "2025-03-14T03:45:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gaza](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/gaza/32/28258_2.png) [@Gaza](https://forums.realmacsoftware.com/u/Gaza)\
**Post date:** [March 14, 2025, 3:45am UTC](https://forums.realmacsoftware.com/t/resource-dropwell-bug/46727/1 "2025-03-14T03:45:54Z")

</div>

Maybe a bug, or maybe I’m holding it wrong.

Image illustrates, but for completeness…

Component properties

```auto
{
	"groups": [{
		"title": "Settings",
		"icon": "folder",
		"properties": [{
			"title": "mp3 Audio File",
			"id": "audiofile",
			"resource": {
				"accepts": "mp3"
			}
		}]
	}]
}

```

Component hooks

```auto
const transformHook = (rw) => {    

	const { audiofile = {} } = rw.props
	
	rw.setProps({
		audiofile,
		node: rw.node
	})
}

exports.transformHook = transformHook;

```

Firstly, the dropwell isn’t being restricted to mp3 files, I can drop anything in there.

Secondly, the resulting path is appended with @1024.png, so somehow the mp3 file is being processed as a png image file.

Link to screenshot  
[http://www.garysimpson.co.uk/vault/temp-sharing/uicontrol-shot.png](http://www.garysimpson.co.uk/vault/temp-sharing/uicontrol-shot.png)

---

<div class="post-metadata">

**Author:** ![ben](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/ben/32/28488_2.png) [@ben](https://forums.realmacsoftware.com/u/ben)\
**Post date:** [March 14, 2025, 9:00am UTC](https://forums.realmacsoftware.com/t/resource-dropwell-bug/46727/2 "2025-03-14T09:00:14Z")

</div>

> [@Gaza](#):
>
> Firstly, the dropwell isn’t being restricted to mp3 files, I can drop anything in there.

This is a known “bug” - we haven’t actually gotten around to implementing restrictions to the resource drop well… yet!

It’s on the list and will be implemented before final release 🙂

> [@Gaza](#):
>
> Secondly, the resulting path is appended with @1024.png, so somehow the mp3 file is being processed as a png image file.

It looks like there may be a bug here—we’ll need to do some internal testing to understand why and how `@1024` is being appended in your case.

For context, the appended `@{number}` comes from the resource resizing API (`rw.resizeResource()`). If you’re not using that, it shouldn’t be adding the extra value.

I also wanted to clarify a couple of things about the resource control. When accessed directly in a template, the resource control returns an image for the resource. For example, if you have a resource control with the ID `audioResource`, using `{{audioResource}}` in a template will return an image representation of the resource. I think this makes sense for videos, where a thumbnail can be useful, but might not be what you want for audio files.

If you’re looking to get the actual file path instead, you should access the `path` property from the resource. Using `{{audioResource.path}}` in your template will give you the full path to the file.

Let me know if that helps 🙂