Flarum Signature

katos

Gorm do you have a screenshot of what you’re seeing please because I’ll be honest I’m not able to replicate what you’re describing

Gorm

GreXXL Sure!

katos images bellow clickable.

Problem area:
Problem area with description:
Lets add Like..
Lets add answer..
So, my conclusion.. If users wants, they can add hr-like line by self:

There is some text. It is bold.

Did you see this line? Its just Markdown and this sample works in signature.

---------

**There is some text. It is bold.**

So delimeter-line by default is totally unneeded. If you still think about delimeter it can be something much more shorten like several dashes (and users can do it manually too), but just 1-2-3 empty lines as delimeter much more suitable.

Experiments with lines and without poll:
Signature must be right after main text in post. Not like a support footer. It must be a part of text message.

It's very tricky to add empty lines in new editor. I have a success with

` `  
` `

With 1-2 empty lines its looking a little better, but it cant be done for all users by default.

PS. Last available Flarum with all updates. I am using fof-polls. It's the only poll-solution.
My Custom CSS related to Flarum Categories:

.TagCategory .TagCategory-content {
	padding: 4px 20px !important;

}

.TagCategory .TagCategory-content .TagCategory-main .TagCategory-name {
	display: block;
	margin: 0;
	font-size: 19px !important;
}

.TagCategory.SubCategory .TagCategory-content .TagCategory-icon .CategoryIcon {
	color: #000 !important;
}

.TagCategoryList > .TagCategory {
  margin-bottom: 11px !important;
}

I am using last available firefox and my resolution is 3000*2000 (serial Huawei laptop). Very specific, I know, but most of described is conceptual errors.

katos

Gorm Thanks for this - I will see what I can develop and rectify this for you.

HarMan - Strange, I am able to replicate this too - Will review this as a matter of urgency.

katos

Gorm This is now fixed in my staging environment:
Fixed CSS

I am just working through a few issues with the permissions as @HarMan pointed out. This is now fixed on the frontend but there is a potential backend issue that @IanM is very kindly assisting with. Will report back ASAP 🙂

HarMan

Added permission to allow restriction of who can use a signature on your forum.

I have set it so that admins and moderators can only use the signature, but regular users can still use it

Gorm

katos of course, it's a big work. But I think that you lost main for now:

block with Reply and Like must be most bottom. Bellow polls, signature, everything. Because users didnt find Reply/Like buttons in the middle of the post (if signature is big - its real possible, that reply/like near the middle). It is wrong. You change the position of standard elements with awaited standard functions. So, main problem - position of output for signature.
signature must follow right the writable content. Not bellow polls. Signature must be upper then poll. Just bellow user-text + delimeter (some empty space - most applicable).

I am hope that your staging screenshot showing us just current progress (or some hotfixes) and not final revision.

katos

🥳 Version 1.5 released! 🥳

Changelog

Rectify issues with permissions which inadvertently allowed a user to create a signature when they shouldn't have been allowed to do so (Reported by @HarMan)
Adjust CSS and structure to add signature to the end of the post body. (Reported by @Gorm)
Remove additional line break in favour of allowing users to add their own with markdown if preferred.
Improve support with third party extensions by rectifying CSS issues that broke the alignment of post components.
Extend and improve support for code tests.

🤝 Credits 🤝

This release would not have been possible without the continued support of @IanM - If you would like to show your support for Ian, you can do so using his donation link here: https://www.buymeacoffee.com/ianm1

Gorm

katos, @IanM It's a great work!!!

For now I can detect only one glitch. Sometimes when I press Edit - its activate both edit area - for post and for signature. Seems it call similiar function or react on the same event/action.

How to reproduce: open discussion in new tab (page loading needed), just select text in signature (several clicks on text), then try to edit post (press Edit).
You will see 2 editors in the same time (am I hacker?). You can close/collapse main post-editor, but you cant close signature-editor without saving.

katos

Gorm Thanks for the report, I'm afraid I can't seem to replicate this on my end. Do you perhaps have a video of this in action by any chance please?

Gorm

katos need to click for detailed viewing:

Gif will be available for 2 days.

katos

Gorm Peculiar, I cannot replicate this issue at all 🤔

katos

katos And of course, as I post this - I manage to replicate it .....
Thanks @Gorm - Let me dig into this one!

katos

🥳 Version 1.6 released! 🥳

Changelog

Use same markup as core for LinkButton on the users page: katosdev/signature26 ( @davetodave178 )
Implement setting for "If Inline editing is allowed": katosdev/signature27 ( @davetodave178 )
Use slug for routing to ensure greater compatibility regardless of if slug is default or ID. katosdev/signature28 ( @davetodave178 )

🤝 Credits 🤝

Many thanks to @davetodave178 for the assistance with the PRs in this request!

Gorm

katos seems it perfect and very stable for now.

I am using it with Flarum 1.8.5 and all updates.

BrodyStone21

I'm having an issue installing.

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - katosdev/signature 1.3 requires symfony/css-selector ^6.0.2 -> found symfony/css-selector[v6.0.2, ..., v6.4.8] but the package is fixed to v7.0.3 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - katosdev/signature[1.4, ..., 1.6] require symfony/css-selector ^5.0 || ^6.0.2 -> found symfony/css-selector[v5.0.0, ..., v5.4.40, v6.0.2, ..., v6.4.8] but the package is fixed to v7.0.3 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - Root composer.json requires katosdev/signature * -> satisfiable by katosdev/signature[1.3, 1.4, 1.5, 1.6].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require katosdev/signature:*" to figure out if any version is installable, or "composer require katosdev/signature:^2.1" if you know which you need.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

EDIT: Oh no, @katos hasn't been online in 23 days, please come back 😭

forever

Already processed

Gorm

forever seems dotted line can be reached only CSS using. In normal way you can use --, __, and **, but all of them suitable only for hr-line. And using CSS you can make it dotted.

It will be easier if you show HTML-view of this. Maybe you can just copy-paste this symbol. But I think, that symbol in signature is just a pic uploaded to any and showing like just a regular img in svg format.

Unfortunatelly, img tag seems unreachable here and I cant provide width and height using Markdown here, but image will include correctly.

So the answer for you case will be: svg-image + some CSS. You can easily repeat this trick in your signature on the same forum 🙂

« Previous Page