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

How to set multiple rel="me" links in blog verification? #819

Open
Moonbase59 opened this issue Nov 5, 2023 · 3 comments
Open

How to set multiple rel="me" links in blog verification? #819

Moonbase59 opened this issue Nov 5, 2023 · 3 comments

Comments

@Moonbase59
Copy link

Moonbase59 commented Nov 5, 2023

Describe the bug

I think the new Verification function in Blog/Customize is very useful, but can’t find out how to set the 2nd, 3rd, etc. Maybe I overlooked something?

Rationale: Multiple <link rel="me"… are allowed, and one often has more than one account to verify, say the mastodon.social and your local Nextcloud address.

Steps to reproduce (if necessary)

Steps to reproduce the behavior:

  1. Go to 'Blog/Customize', enter verification link.
  2. No 2nd input field appears.

Expected behavior

Would be nice to be able to add/delete multiple profiles.

Application configuration

  • Single mode or Multi-user mode? Multi
  • Database? [mysql/sqlite] (Doesn’t show in Admin Monitor)
  • Open registration? [yes/no] no
  • Federation enabled? [yes/no] yes

Version or last commit: v0.14.0

@thebaer
Copy link
Member

thebaer commented Feb 2, 2024

Thanks for reporting this! Unfortunately it's not supported, but I'm sure we could do that somehow. If anyone wants to chime in or take on this issue, please feel free!

@glyn
Copy link

glyn commented May 8, 2024

I would also value this feature in order to support indielogin while also having my blog verified in my mastodon profile.

Note that a possible workaround would be to allow <link rel="me"…/> in the Post Signature configuration, but when I try this, writefreely appears to strip out the whole tag. Similarly, if I include <a rel="me"...>xxx</a> in the Post Signature, writefreely appears to strip out the rel="me".

@glyn
Copy link

glyn commented May 26, 2024

There is a nasty workaround: setting custom CSS in the configuration to, for example:

</style>
<link rel="https://example.org/xxx" href="https://example.org"/>
<style>

introduces the link. This works for rel="me" links too. Of course, if the custom CSS is ever validated, this workaround would cease to function.

See here for the original source of the workaround, which would also be broken by custom CSS validation.

Maybe @thebaer would care to comment? For instance, it would be charitable to allow this workaround to be used until such time as there was proper support for multiple links (and not just rel="me" links, please).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants