# Console warnings when toggling editor types - are these normal?

**URL:** <https://support.zenmasters.team/t/console-warnings-when-toggling-editor-types-are-these-normal/99>\
**Category:** Zen Dock\
**Tags:** question\
**Created:** [May 30, 2025, 7:10pm UTC](https://support.zenmasters.team/t/console-warnings-when-toggling-editor-types-are-these-normal/99 "2025-05-30T19:10:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Max](https://avatars.discourse-cdn.com/v4/letter/m/e5b9ba/32.png) [@Max](https://support.zenmasters.team/u/Max)\
**Post date:** [May 30, 2025, 7:10pm UTC](https://support.zenmasters.team/t/console-warnings-when-toggling-editor-types-are-these-normal/99/1 "2025-05-30T19:10:08Z")

</div>

Hi,

I have a question about some console warnings I’m seeing whenever I toggle between different editor types using the addon buttons, I get these warning messages in my console. For example, with shader editor button I see something like:

WARN (bpy.rna): C:\Users\blender\git\blender-v440\blender.git\source\blender\python\intern\bpy\_rna.cc:1357 pyrna\_enum\_to\_py: current value ‘0’ matches no enum in ‘SpaceNodeEditor’, ‘(null)’, ‘texture\_type’

and similar messages for other editors like timeline, UV editor, or asset browser. I have not tested it with every single editor type, but one that i tested and i am not getting this warning is the ‘Info’ editor. I’m using Blender 4.4.1 (also tried it on 4.2) and I see your addon lists these versions as compatible, so I’m wondering if these warnings are something I should be concerned about?

---

<div class="post-metadata">

**Author:** ![Alexander\_Zhornyak](https://yyz1.discourse-cdn.com/flex011/user_avatar/support.zenmasters.team/alexander_zhornyak/32/6_2.png) [@Alexander\_Zhornyak](https://support.zenmasters.team/u/Alexander_Zhornyak)\
**Post date:** [June 5, 2025, 8:46am UTC](https://support.zenmasters.team/t/console-warnings-when-toggling-editor-types-are-these-normal/99/2 "2025-06-05T08:46:42Z")

</div>

Hi, thank you for report the issue is reported to Blender developers but it seems that they won’t fix it.

[Blender issue #82250](https://projects.blender.org/blender/blender/issues/82250)
