This repository has been archived by the owner on Sep 15, 2024. It is now read-only.
forked from ChatGPTNextWeb/NextChat
-
Notifications
You must be signed in to change notification settings - Fork 8
[Bug] After disabling the GPT 4 model, you can still use the GPT 4 model by manually entering a custom model #100
Comments
H0llyW00dzZ
added a commit
that referenced
this issue
Nov 14, 2023
[+] fix(common.ts): update condition to check if serverConfig.customModels starts with "gpt-4" instead of checking if it exists and req.body exists
can you try by clicking this a link before I push to main branch ? |
The above deployment link does not disable GPT4 |
hold on let me redeploy |
|
that's error from your one api |
I found it. It was my problem. I did not delete the previous conversation records. Now it is possible. Even if I manually add the GPT 4 model, I cannot select it. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
After disabling the GPT 4 model, you can still use the GPT 4 model by manually entering a custom model
Deployment
Vercel
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: