# UI\_MEDIA warning

**URL:** https://discourse.nodered.org/t/ui-media-warning/18646
**Category:** Dashboard
**Created:** [1 December 2019 05:55 UTC](https://discourse.nodered.org/t/ui-media-warning/18646 "2019-12-01T05:55:48Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![AsHex\_66](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ashex_66/32/31151_2.png) [@AsHex\_66](https://discourse.nodered.org/u/AsHex_66)
#### Post date: [1 December 2019 05:55 UTC](https://discourse.nodered.org/t/ui-media-warning/18646/1 "2019-12-01T05:55:48Z")

</div>

When starting node red, a warning is being displayed:

18 Nov 17:58:25 - [warn] [ui\_media:Test] \*\*\* Order property not set. Please contact developer. \*\*\*

No performance issues have been detected

Environment  
18 Nov 17:58:09 - [info] Node-RED version: v1.0.2  
18 Nov 17:58:09 - [info] Node.js version: v12.6.0  
18 Nov 17:58:09 - [info] Windows\_NT 10.0.18362 x64 LE

Anybody else has this and does it really matter?  
Contacted the developer but no reply so far

Keen to resolve this myself, but have no idea where to start looking as 'google' does not give me lots of feedback what is wrong. If I know the problem, might even 'fork' the development and fix it for others

---

<div class="post-metadata">

### Author: ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)
#### Post date: [1 December 2019 07:57 UTC](https://discourse.nodered.org/t/ui-media-warning/18646/2 "2019-12-01T07:57:57Z")

</div>

If you are using a contributed node then the first place to look when you have a problem like this is to look on the node's GitHub page. You haven't said which node you are using but I guess it is node-red-contrib-ui-media. In this case it appears the issue has already been reported.

> <https://github.com/netsmarttech/node-red-contrib-ui-media/issues/12>
>
> When starting node red, a warning is being displayed:
> 18 Nov 17:58:25 - \[warn\] \[ui\_media:Test\] \*\*\* Order property not set. Please contact...

---

<div class="post-metadata">

### Author: ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)
#### Post date: [1 December 2019 08:12 UTC](https://discourse.nodered.org/t/ui-media-warning/18646/3 "2019-12-01T08:12:34Z")

</div>

Ok, I'll redact what I said. I do have it installed.

How about you past the part of the flow where the message is created and the node itself.

I had a bit of trouble getting it working, but it shouldn't be that hard. I got it working - and I'm not the sharpest tool in the shed.

---

<div class="post-metadata">

### Author: ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)
#### Post date: [1 December 2019 08:39 UTC](https://discourse.nodered.org/t/ui-media-warning/18646/4 "2019-12-01T08:39:53Z")

</div>

This is just a warning. Ui nodes need to have a hidden property called order preset so the ui can save the position of the node. Without it it may mean the widget can randomly move around the display when other items are repositioned. Once we found the issue we added this warning so other nodes could be flagged and fixed.

---

<div class="post-metadata">

### Author: ![gfcittolin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/gfcittolin/32/23354_2.png) [@gfcittolin](https://discourse.nodered.org/u/gfcittolin)
#### Post date: [10 December 2019 12:02 UTC](https://discourse.nodered.org/t/ui-media-warning/18646/5 "2019-12-10T12:02:43Z")

</div>

Just for the record, this issue and some others have been resolved. Version 1.2.0 have been published with all of them. Thanks for reporting, and let me know if there's any other issue!
