Nodes/ComfyUI_MaraScott_Nodes/❌ Display Info - Text v1 /i
ComfyUI Node

❌ Display Info - Text v1 /i

The renamed display node, and why old workflows ask for it

By MaraScott·Created 3 years ago·Updated 10 months ago· 178
❌ Display Info - Text v1 /i
    • STRING
    text

    You're probably here because a downloaded workflow is screaming that MaraScottDisplayInfoNode is missing. Good news: it's the pack's text display node under its "MaraScott" naming era, and it's the same one-input, one-output utility as the original "Display Info - Text" - just registered under a versioned class name.

    It takes a text STRING, shows it on the canvas, and passes the identical value out of its STRING output so the text can keep flowing into the rest of the graph (the pack's own README pitches this for feeding values through ForLoop open/close workflows). It's marked as an output node in the registry, but the pass-through means you can leave it mid-chain and use the visible text as your debugging surface. That's the whole feature set - there are no knobs.

    Installing it

    cd ComfyUI/custom_nodes
    git clone https://github.com/davask/ComfyUI-MarasIT-Nodes
    

    Restart ComfyUI, or Manager → search "MaraScott" → Install → restart.

    If the node still shows as missing

    This exact class name is a legacy registration. The current pack exports the display node as MaraScottDisplayInfo_v2 ("Display Any", shortcut /i), so a workflow that references this old class may need a rename to the current one - ComfyUI will keep saying it's missing if it can't match the class. Same behavior either way: one text input, one pass-through text output, text printed on the node. If the goal is just to see what a string contains, you've lost nothing by switching to the current name.

    Where you'll actually use it

    Prompt assembly and loop debugging are the two spots it earns its keep. Drop one after a text-concatenation node and you can verify the combined prompt before it hits the encoder; put one inside a ForLoop-style pass and the changing value is visible with every iteration instead of buried in a log. It won't fix your workflow for you - but it will tell you, instantly, when the string you think you're sending is not the string you're actually sending.

    CategoryMaraScott/utils

    Inputs (1)

    NameTypeDefaultDescription
    textSTRING

    Outputs (1)

    NameTypeDescription
    STRINGSTRING