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

I cant get this to work. Is it something I'm doing wrong? #25

Closed
welpdx opened this issue Jul 4, 2021 · 10 comments
Closed

I cant get this to work. Is it something I'm doing wrong? #25

welpdx opened this issue Jul 4, 2021 · 10 comments

Comments

@welpdx
Copy link

@welpdx welpdx commented Jul 4, 2021

What I did

testing2.md:

---
type: website
---
asdf

testing1.md:
text [[testing2]] text

Links.css:

a.internal-link[data-link-type$="website"]::before{
    content: "🌐 " !important
}
a.internal-link[data-link-type]{
    color: white;  !important
    background-color: rgb(29, 29, 129); !important
    border-radius: 18px;  !important
    padding: 5px 15px; !important
}

Result (not working): img

Settings/Info

Obsidian V0.12.9
Plugin V0.2.12

Plugin Enabled? √
Target Attributes for styling: type
CSS Snippets Enabled? √
Apply Custom CSS? √
Links.css changes saved? √

Using demo attribute category also doesn't work.

@balola
Copy link

@balola balola commented Jul 7, 2021

Hi,

It is workong for me:

a.internal-link[data-link-category$="Document" i]::before{
content: "📖 "
}

The difference is only the "i".
Füles

@welpdx
Copy link
Author

@welpdx welpdx commented Jul 7, 2021

Thanks for your comment.

The "i" doesn't work for me either. In fact, the snipped in the readme included the "i". The reason I removed it is because in the video tutorial, the original coder didn't add "i" there. I thought that would fix the problem, but it didn't.

Other things I tried:

  • In my set up I also tried adding !important but that didn't do nothing either.
  • I even changed the emoji to text to see if it is something to do with the emoji thingy... Still didn't work.

One thing I do want to note is that I am using the Obsidian V0.12.9

Anyways, thanks for your comment.

Welp

@mdelobelle
Copy link
Owner

@mdelobelle mdelobelle commented Jul 7, 2021

Hello did you add "type" as a targeted attribute for styling in the settings? (see example below)
image
!important shouldn't be necessary

this is the result i get with your example
image

my css:

a.internal-link[data-link-type$="website"]::before{
    content: "🌐 "
}
a.internal-link[data-link-type]{
    color: white;
    background-color: rgb(29, 29, 129);
    border-radius: 18px;
    padding: 5px 15px;
}

@welpdx
Copy link
Author

@welpdx welpdx commented Jul 7, 2021

Replicating your post:
Settings
img
Notes
img
Settings -> Appearance
img
Links.css
img

Still doesn't work for me. 😢

Edit: Thanks guys for helping me

@mdelobelle
Copy link
Owner

@mdelobelle mdelobelle commented Jul 23, 2021

Hi, could you inspect the link (command+option+I on Mac then image on the developer tools windows, then click on the "testing2" link) and write the output?

@welpdx
Copy link
Author

@welpdx welpdx commented Jul 23, 2021

Hey @mdelobelle,
I'm on windows, and this is the output.
picture

<a data-href="testing2" href="testing2" class="internal-link" target="_blank" rel="noopener" data-link-type="website">testing2</a>

Thanks

@oojw
Copy link

@oojw oojw commented Aug 4, 2021

Hi, I am having the same issue, how can I resolve it? thank you

@mdelobelle
Copy link
Owner

@mdelobelle mdelobelle commented Aug 5, 2021

@welpdx everything seems to be properly set up.
Could you try to disable all plugins but this one and see if it's working?
If it's the case then it means there is a conflict between plugins. In this case try to enable each of your plugins one by one and see which one prevents supercharged links from working.

@welpdx
Copy link
Author

@welpdx welpdx commented Aug 6, 2021

@mdelobelle I've been diagnosing Supercharged_links on a test vault with just the basic functions on. But just in case, I've disabled the community plugins and the core plugins just now. Still nothing. Thanks for continuing helping me out with this one.

I had suspected that the problem is to do with my Windows 10 Enterprise 2016 LTSB Ver 1607 not having emoji capabilities. But after installing windows on a new computer and trying out a new obsidian setup, it still doesn't work...

This is my test obsidian vault, if you guys want to try it out and see if it works.
Or alternatively, please send me your test vault with the plugin working...

@mikkovedru
Copy link

@mikkovedru mikkovedru commented Sep 14, 2021

@welpdx
I checked your vault and I have the same problem as you. And I am sitting on Linux Mint here. The problem turns out to be that the custom css file from Settings/Appearance/CSS Snippets is not being loaded. The file is being shown and looks totally fine, but for some reason Obsidian just refuses to read and process its content. I have tried to figure out a reason for it, but I am out of ideas and don't want to waste any more time. Perhaps you or someone else could continue with the search?

If you decide to continue, I recommend adding the following text to your custom .css file, so you can easily see if at some point the content will be finally loaded.

/* Enable the official file explorer plugin. templates directory will have an emoji in front of the name*/
.nav-folder-title[data-path="templates"] .nav-folder-title-content::before {
  content: "⚙️ ";
  font-size: 1.8em;
  border-left: 2px dashed black;
}

/* How uncreated notes look like in View mode */
.is-unresolved::before {
  content: "🗋 ";
}
.is-unresolved {
  opacity: 1 !important;
  color:  red;
  background-color: #fdffcd;
}

The first will make the template directory look like this:
image

The second will show the non-created files in red in preview mode:
image

Good luck! Perhaps you should write a bug report to Obsidian forum with the link to this github issue?

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