[Bug]: Browser page gives incorrect result when given new civitai.red links

[preyx]

Describe the bug.

The browser tab doesn't give the correct result when given a link beginning with "civitai.red". My initial guess is that it tries to search the link as a string, instead of directly reading the model, since it doesn't contain "civitai.com".

Steps to reproduce the problem.

1. Go to CivitAI Browser+ plugin, Browser tab
2. Enter a "civitai.red" model link into the search box. SFW example: https://civitai.red/models/912942/retro-sci-fi-90s-anime-style-animaillustriousxlzimageturbofluxchroma?modelVersionId=1021743
3. Result is not the linked model, but a different one (I got https://civitai.com/models/2105753?modelVersionId=2382293)

Expected behavior

If you replace ".red" with ".com" in the above example link, the search returns the correct model. The behavior should be the same in both cases.

System info

• Extension version: Current (published 2025-12-24)
• OS: Win10
• SD-WebUI version: WebUI Forge
• Python: 3.14

Console logs

[no errors]

Additional information

The CivitAI team says that the same API should work for both .com and .red sites (I haven't tested this myself). I imagine the extension code will need to be updated regardless since there are hard-coded occurrences of "civitai.com".

I don't have a strong suggestion how to handle this going forward. Perhaps directing all results and links to .red to cover all models? (.com is now SFW only, .red contains all .com models plus NSFW)

[preyx]

I tested the "Update Models" tab with some manually downloaded LORAs (from civitai.red). Not all of my LORAs got a result ("model ID not found" error in the console). It could be an API bug (the changeover happened today), so I'll wait to try this again in a week or so.

[anxety-solo]

Hi! It's great to see you again :3

Thanks for the detailed information and description of the issue.

I've already made some minor changes and pushed them to the dev branch. The link search now works properly for both .com and the new .green and .red domains.
As for the scanning issue, I can only rely on your observations and verification of the small fixes I’ve just made... (unfortunately, I can’t personally verify this yet; I can only make changes to work with the API...)

At the moment, I can only conclude that the API is currently working as usual and does not require any changes, but links not related to the API had to be replaced with the .red domain...

[preyx]

Likewise, I'm glad to see you're still active and keeping up with everything! :D

I downloaded the dev branch and confirmed that it does search correctly using the example model I mentioned. I was also able to download a different model through the Browser interface.

It took a few tries, several hours apart, but the "Update Models" function did work correctly. JSON and preview images were saved. (I'm 99% certain that the multiple tries were because of Civitai server lag, not the plugin's fault.)

The Civitai button on the lora/checkpoints gallery tabs (on generation pages) also work properly, and correctly link to civitai.red.

So far, all the features I use on a regular basis appear to be working correctly.

PS - Naturally, all the JSON files generated in the past reference civitai.com. This appears to affect the page loading using the Civitai button if you're not saving a local copy. I have a lot of (way too many) LORAs, so instead of re-downloading all the JSON data through the "Update Models" function, I found a program called grepwin (also on github) that let me find-replace "civitai.com/models" -> "civitai.red/models" in one shot. This step is not your responsibility to fix, but might be handy info in case someone brings up an issue related to this.

[preyx]

So far so good, I would say the issue in the OP post is resolved at this point. "Update model preview" action is still slower than before the com/red split, but I still think it is the API/site and not the extension.

I happened to encounter an edge case today, model link: https://civitai.red/models/2553842/naucrate-fate-grand-order
What makes this unusual is that the model is not visible on the civitai.red until the Civitai User "Mature Content" option is DISABLED(?!). The civitai.com version of this link works regardless of civitai.red settings, I'm guessing because NSFW is automatically disabled over there.

The "Browser" tab can't find the model using link or hash, nor can the "Update Models" tab write the JSON or preview image. It seems like this model is just not showing up in the API search. I don't know if "SFW-only" was a thing before the com/red split, and I didn't find an explanation/solution in a quick google search. Civitai's official post about the transition claims that the API and civitai.red should be able to see everything, this scenario isn't mentioned.