# Why warn about projects.enabled = false?

**URL:** <https://discourse.nodered.org/t/why-warn-about-projects-enabled-false/94295>\
**Category:** General\
**Created:** [1 January 2025 17:47 UTC](https://discourse.nodered.org/t/why-warn-about-projects-enabled-false/94295 "2025-01-01T17:47:38Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ThingsTinkerer](https://avatars.discourse-cdn.com/v4/letter/t/91b2a8/32.png) [@ThingsTinkerer](https://discourse.nodered.org/u/ThingsTinkerer)\
**Post date:** [1 January 2025 17:47 UTC](https://discourse.nodered.org/t/why-warn-about-projects-enabled-false/94295/1 "2025-01-01T17:47:39Z")

</div>

Got a NR instance I don't want projects for. It is it's own thing and is handled in git as a normal project, not with NR's git client. But why would Node Red warn about this on startup?

`[warn] Projects disabled : editorTheme.projects.enabled=false`

Any way to silence it?

---

<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 January 2025 20:59 UTC](https://discourse.nodered.org/t/why-warn-about-projects-enabled-false/94295/2 "2025-01-01T20:59:22Z")

</div>

I agree, that should show an `info` message not a `warn`.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [1 April 2025 21:00 UTC](https://discourse.nodered.org/t/why-warn-about-projects-enabled-false/94295/3 "2025-04-01T21:00:01Z")

</div>

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
