Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prompt component dosent' show the Input and cotext fields #6321

Open
lasantha13 opened this issue Feb 13, 2025 · 1 comment
Open

Prompt component dosent' show the Input and cotext fields #6321

lasantha13 opened this issue Feb 13, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@lasantha13
Copy link

Bug Description

After updating my components, I found that the 'Question' and ' Context' fields are missing in the Prompt component. I'm using online version

Image

Image

Reproduction

create new flow form online site
drag Prompt component

Expected behavior

dispaly the Input and context fields in the prompt component

Who can help?

No response

Operating System

Na

Langflow Version

latest

Python Version

None

Screenshot

No response

Flow File

No response

@lasantha13 lasantha13 added the bug Something isn't working label Feb 13, 2025
Copy link

dosubot bot commented Feb 13, 2025

Hey @lasantha13! I'm here to help you with any bugs, questions, or contributions. Let's tackle this together!

The issue you're experiencing with the missing 'Input' and 'Context' fields in the Prompt component might be related to recent changes in the Langflow codebase. The latest version of Langflow introduced a MessageTextInput named "tool_placeholder" with the advanced attribute set to True, which could affect how fields are displayed, especially in advanced configurations or tool modes [1].

To troubleshoot this, you might want to check if the fields are hidden due to the advanced setting or if there are specific conditions in your configuration that might be affecting their visibility. Additionally, ensure that your prompt template includes the necessary variables that would trigger the creation of these fields automatically. If the issue persists, reviewing the component's configuration or checking for any conditional logic that might hide fields could be helpful.

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other | Bug Report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant