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 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.

        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 🙂

            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.

              🥳 Version 1.5 released! 🥳

              Changelog

              1. 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)
              2. Adjust CSS and structure to add signature to the end of the post body. (Reported by @Gorm)
              3. Remove additional line break in favour of allowing users to add their own with markdown if preferred.
              4. Improve support with third party extensions by rectifying CSS issues that broke the alignment of post components.
              5. 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

                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.

                    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?

                        katos need to click for detailed viewing:

                        Gif will be available for 2 days.

                            Gorm Peculiar, I cannot replicate this issue at all 🤔

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

                                  🥳 Version 1.6 released! 🥳

                                  Changelog

                                  1. Use same markup as core for LinkButton on the users page: katosdev/signature26 ( @davetodave178 )
                                  2. Implement setting for "If Inline editing is allowed": katosdev/signature27 ( @davetodave178 )
                                  3. 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!

                                    20 days later
                                    7 months later

                                    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 😭

                                    a month later
                                    8 days later

                                    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 🙂