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

bug: Interesting Lookup do not accept new values #1027

Closed
1 task done
carboncrystal opened this issue Oct 31, 2023 · 2 comments · Fixed by #1071
Closed
1 task done

bug: Interesting Lookup do not accept new values #1027

carboncrystal opened this issue Oct 31, 2023 · 2 comments · Fixed by #1071

Comments

@carboncrystal
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Menu Scan Engine > Interesting Lookup > do not accept new values.
Error is: Press comma , to separate the keywords.

Expected Behavior

Add new desired values in Interesting Lookup

Steps To Reproduce

Try to add new values in menu: Scan Engine > Interesting Lookup

Environment

- reNgine: 2.01
- OS: Ubuntu 22.04.3 LTS
- Python: 3.10.12
- Docker Engine: 24.0.7, build afdd53b
- Docker Compose: v2.5.0
- Browser: Firefox

Anything else?

Screenshot from 2023-10-31 08-00-54

@github-actions
Copy link
Contributor

👋 Hi @carboncrystal,
Issues is only for reporting a bug/feature request. Please read documentation before raising an issue https://rengine.wiki
For very limited support, questions, and discussions, please join reNgine Discord channel: https://discord.gg/azv6fzhNCE
Please include all the requested and relevant information when opening a bug report. Improper reports will be closed without any response.

@yogeshojha
Copy link
Owner

Hi @carboncrystal oops sorry :D that is not an error, I changed the font color to gray. that was just an message. Your interesting lookup keyword is saved already.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants