[GH-ISSUE #332] Lora filenames break on comma #230

New issue

Closed

opened 2026-10-30 21:21:20 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-30 21:21:20 +00:00

Owner

Originally created by @rauhan-spec on GitHub (Sep 8, 2025).
Original GitHub issue: https://github.com/DominikDoom/a1111-sd-webui-tagcomplete/issues/332

Greetings, I have encountered a problem while using this extension.

If I have a lora file that contains one or more commas in the filename, then the autocompletion will only display and insert only the first part of the filename up to the first comma, which renders the lora autocompletion useless. Is there any way to remedy this?

Originally created by @rauhan-spec on GitHub (Sep 8, 2025). Original GitHub issue: https://github.com/DominikDoom/a1111-sd-webui-tagcomplete/issues/332 Greetings, I have encountered a problem while using this extension. If I have a lora file that contains one or more commas in the filename, then the autocompletion will only display and insert only the first part of the filename up to the first comma, which renders the lora autocompletion useless. Is there any way to remedy this?

bsakaguchi closed this issue

2026-10-30 21:21:20 +00:00

bsakaguchi commented

2026-10-30 21:21:21 +00:00

Author

Owner

@DominikDoom commented on GitHub (Sep 9, 2025):

This was a small oversight in path parsing, it should work now. Feel free to reopen if you still encounter some issues with your filenames.

Note: While this should fix the display and insertion, it might still cause trouble due to the autocompletion always assuming a new tag starts after a comma (which is not feasible to change as the whole extension is based on it). As a workaround, you can enter * as a placeholder, which will allow you to type and search for the parts after the comma without having to type the comma itself.
E.g.: A file with the name my cool, new lora will be searchable with both <my_cool*new_... or even just <*new_...

@DominikDoom commented on GitHub (Sep 9, 2025): This was a small oversight in path parsing, it should work now. Feel free to reopen if you still encounter some issues with your filenames. Note: While this should fix the display and insertion, it might still cause trouble due to the autocompletion always assuming a new tag starts after a comma (which is not feasible to change as the whole extension is based on it). As a workaround, you can enter `*` as a placeholder, which will allow you to type and search for the parts after the comma without having to type the comma itself. E.g.: A file with the name `my cool, new lora` will be searchable with both `<my_cool*new_...` or even just `<*new_...`