Yeah…I get it…but then why do this?
We feel rather strongly as an organization that signatures must be 1) an optional plugin and 2) per user opt-in. Those who want it, can turn it on.
Another way to handle them is have them inserted when the post is rendered so that they aren’t in the post. That would keep the signatures from getting copied into quotes, I think. (?)
A plugin I wrote allows members of a certain group to have a signature, but if they are removed from the group the signatures no longer display. One could similarly make it so that members signatures show only for themselves.
Ruby newb here.
If I wanted the signature to display the contents of the user’s bio field, is there an easy way to do this?
Apologies in advance for my ignorance!
That is totally doable with minimal changes.
I figured as much, but my knowledge of Ruby/Discourse is not so hot. How do I access the bio variable? (If there’s a tutorial or some other documentation to help with this that would be great!)
The user attribute in this case is
First thing is getting that shipped together with every post.
Here in this block:
You will need to add that attribute instead of the custom signature to the serializer.
You need to use this new
bio_cooked instead of the signature.
After that is working, you can delete a lot of code that was there to handle the extra field for a custom signature.
We had a large number of core users in our community who demanded signatures, and were content with the image solution. I think we found a good middle ground between serving our most loyal users while not interfering with the ux of the majority
Thanks so much, got it working just fine.
Question – signatures don’t seem to get attached to post notifications sent by email, is there any possibility of adding this?
Agree that they would better be “an optional plugin” and “opy-in”. Signatures are important as one who use one, put their name/reputation/brand and they could be scrutinized. At the same time many use them as a marketing tool, so I believe they if there are any links there, they must be nofollow.
Is it possible to limit Discourse Signature for just a certain user level or let’s say above a level?
It will be a handy tool for spammers to take advantage of it.
It will be great if we can limit it to trust levels. Its like the users should work their way through to earn it.
That’s not planned but I can accept a PR that implements it.
Is there a way to authorize signatures, and allow users who don’t want to see them to disable them?
Yes, users can hide signatures by unchecking the “
See user signatures below posts” in their preferences.