brianpetro / obsidian-smart-connections

Chat with your notes & see links to related content with AI embeddings. Use local models or 100+ via APIs like Claude, Gemini, ChatGPT & Llama 3
https://smartconnections.app
GNU General Public License v3.0
2.82k stars 185 forks source link

[2.2.77] no settings shown to choose models or switch to legacy transformers #816

Closed alk0 closed 1 month ago

alk0 commented 1 month ago

image

image

brianpetro commented 1 month ago

@alk0 do more settings appear when you click the Smart Connections tab in the Obsidian settings again?

Those settings should include the toggle for legacy transformers which should solve that error.

🌴

brianpetro commented 1 month ago

THis should be fixed in 2.2.78, thanks for bringing this issue to my attention 🌴

alk0 commented 1 month ago

Thanks! Everything is working now on a test vault (not without minor glitches, but working). Will report if any problems occur on a real vault.

notuntoward commented 1 month ago

After this update, smart connections finishes its initialization, and I can click the settings button in the smart connections pane. But I only see a subset of the settings, and not the ones which would allow switching transformers:

What I see when I click the settings icon

image

alk0 commented 1 month ago

@notuntoward

After this update, smart connections finishes its initialization, and I can click the settings button in the smart connections pane. But I only see a subset of the settings, and not the ones which would allow switching transformers:

It may be a bit confusing, having two setting panes. The setting for the legacy transformers is in the "main" plugin settings (Ctrl + , or Ctrl + P, "Open settings", then scroll down on the left to "Community plugins", "Smart Connections", and there you should see the one you need. You may not see it, if the plugin failed to load properly (or is still loading), but it should not be your case.

image

alk0 commented 1 month ago

@brianpetro Let's close this one maybe? So far everything is working for me on the real vault (I did full reembedding just in case - like, manually deleted all ajson's and redid them from scratch, just to be on the safe side. Just applying the recommended Refresh + Force refresh did more or less the same, anyway. The point is, well, the issue in the title is solved, safe to close, I guess.