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

Insert as Link option missing? #71

Closed
ashishbhateja opened this issue Nov 29, 2021 · 13 comments
Closed

Insert as Link option missing? #71

ashishbhateja opened this issue Nov 29, 2021 · 13 comments

Comments

@ashishbhateja
Copy link

@ashishbhateja ashishbhateja commented Nov 29, 2021

I can no longer find the insert as link option in the plugin settings

CleanShot 2021-11-29 at 10 04 16@2x

Appreciate any help in troubleshooting this

@1muggle
Copy link

@1muggle 1muggle commented Dec 5, 2021

@ashishbhateja I don't understand what the reason is, I'm having the same problem as you.
My OS is macOS 12.0.1 and Obsidian version is 0.12.19.
Maybe you can try the following (it works for me)

  1. Press Command (probably Ctrl on Windows) + p to open the command panel
  2. Type "Date picker" and press enter
  3. You should see the following pop-up window, check "Add as link" and click on "Insert Data".

image

4. At this point you should have a wiki link when you type `@Today` or other phrase in your notes

Good luck!

@stouf
Copy link

@stouf stouf commented Dec 9, 2021

Same thing for me, the Add as link? configuration option has disappeared 😞

@ashishbhateja
Copy link
Author

@ashishbhateja ashishbhateja commented Dec 9, 2021

@stouf
Copy link

@stouf stouf commented Dec 9, 2021

The Ctrl+P trick works. You may want to try it.

ctrl + p thing itself works but it doesn’t fix the @ shortcut afterwards for me 😞

@ashishbhateja
Copy link
Author

@ashishbhateja ashishbhateja commented Dec 9, 2021

@jiri
Copy link

@jiri jiri commented Dec 9, 2021

It seems that the community plugin store installs version 0.5.0 while clearly being aware of version 0.6.0. The option is present in 0.6.0 -- could this be your issue?

@stouf
Copy link

@stouf stouf commented Dec 9, 2021

It seems that the community plugin store installs version 0.5.0 while clearly being aware of version 0.6.0. The option is present in 0.6.0 -- could this be your issue?

Ah! Good catch, that's probably it 👍
It's strange though. When I open the page of the plugin in Obsidian, it tells me v0.6.0 is available, I can click on the update button and I get a message telling me the plugin has been successfully updated, but the plugin is stuck on v0.5.0 🤔 I'll have to dig into that.
Any idea where that could come from by any chance?

@jiri
Copy link

@jiri jiri commented Dec 9, 2021

I've got no clue, sorry 😞 I've got no clue how obsidian handles the community plugin support, but if I had to guess, it fetches the releases XML stream from github, looks for the latest one and fetches the files that way, which would suggest the issue might be with obsidian rather than this plugin. Maybe an edge case in manifest.json or something?

@stouf
Copy link

@stouf stouf commented Dec 9, 2021

Some more data:

  • I have another vault where v0.5.2 was installed; I manually updated it and Obsidian downgraded it to v0.5.0 😮
  • I have the same vault synchronized on my iPhone; I updated the plugin and it successfully upgraded it to v0.6.0

That on top of Jiri’s hypothesis there, it indeed looks like a bug in Obsidian 🤔
I’ll fill in a bug report on Obsidian’s forum.

@stouf
Copy link

@stouf stouf commented Dec 10, 2021

I’ll fill in a bug report on Obsidian’s forum.

Just for reference: https://forum.obsidian.md/t/community-plugin-wrong-version-when-installing-and-updating/28339

@stouf
Copy link

@stouf stouf commented Dec 12, 2021

The issue should now be fixed (#74).

@ashishbhateja Shall we close this issue? 🙂

@ashishbhateja
Copy link
Author

@ashishbhateja ashishbhateja commented Dec 13, 2021

Thank you. Here's what I see after updating:
image
image

The @ key seems to work ok on desktop now

@liamcain
Copy link
Collaborator

@liamcain liamcain commented Dec 29, 2021

Closing this since it should be fixed in v0.6.0.

@liamcain liamcain closed this Dec 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants