This extension isn't compatible with beta 14+. Unless someone wants to adopt this extension, or give me the exact code to patch it, I think it'll have to go to the extension graveyard 💀 . From what I've read so far I assume it is due to Mithril 2.0. More specifically due to config no longer being a lifecyle hook? I don't have the skills to update it even though it's probably relatively simple. I tried making some guesses after reading some docs, but no luck.

I feel bad because I do think there are several people that use this. But, we'll have to wait for a developer to possibly, one day, create a new hashtag extension. One that is probably way better than this one.

    010101 CommentPost.prototype.config is now CommentPost.prototype.oncreate and CommentPost.prototype.onupdate. There's no longer an isInitalized parameter, instead oncreate is called once, and onupdate is called for subsequent redraws.

    Basically

    extend(CommentPost.prototype, 'config', function (out, isInitialized, vnode) {
    // [the code]
});

    becomes

    extend(CommentPost.prototype, 'oncreate', function (out, vnode) {
    // [the code]
});
extend(CommentPost.prototype, 'onupdate', function (out, vnode) {
    // [the code]
});

    A function can be used to not repeat the code.

    Or, when isInitialized is used:

    extend(CommentPost.prototype, 'config', function (out, isInitialized, vnode) {
    if (isInitialized) return;
    // [the code]
});

    becomes

    extend(CommentPost.prototype, 'oncreate', function (out, vnode) {
    // [the code]
});

    EDIT: ignore my previous edit referencing super, it only applies if you were creating your own components.

        clarkwinkelmann Thank you for being willing to help! The problem is that this is one of those extensions done the wrong way where everything is in the extend.php file.

        This isn't working:

        <script>
flarum.core.compat.extend.extend(flarum.core.compat['components/CommentPost'].prototype, 'oncreate', function (output, context) {
    if (context.customExtLastContentHtml !== context.contentHtml) {

           // [the code]    

   context.customExtLastContentHtml = context.contentH tml;
  });
</script>

        Original code that did work until beta 14:

        <script>
  flarum.core.compat.extend.extend(flarum.core.compat['components/CommentPost'].prototype, 'config', function(output, isInitialized, context) {
    if (context.customExtLastContentHtml !== context.contentHtml) {

                    // [the code]    

   context.customExtLastContentHtml = context.contentH tml;
  });
</script>

            010101 So it will not be updated?
            Or you not sure about that?
            Maybe you could go on Discord and try ask some help on devs.

            I would help if i had knowledge for that, but i do not!
            Im sure they will find some minutes to give a hand

            Good luck

              010101 The arguments to oncreate are different than those to config. Replace the second argument with vnode. Then, where you need to access the DOM element, use vnode.dom

                Version 3.7 released

                • Updated version constraints in composer.json
                • Updated Mithril Lifecyle hook which means - now compatible with beta 14

                  010101 awesome, thank you very much for your effort and time to keep the extension 😄

                    2 months later
                    3 months later
                    • Beta 16 ready
                    • Now updates both on full page refresh and after editing a post

                    Update with:
                    composer require zerosonesfun/hashtags

                      010101 Found a serious bug. Anytime I'm trying to reply to someone, the message is created insite a code line

                          010101 I tried to disable the Rich Text extension and the bug has gone, it occurs only if I enable both 🤔

                              enricodx I haven’t tried it with the rich text editor yet but yes, there’s a high probability that it’s not compatible. Especially if the rich text editor already looks for the "#" symbol for any reason.

                                  enricodx I will review later this week probably and see if I can figure out what's happening. It can get complex. Anytime another extension does anything related to "#", there’s a conflict.

                                    The time has come to mark this extension as incompatible. Please do so moderators.

                                    It’s a little sad since this extension was downloaded pushing 2,500 times. People like hashtags. Hashtagging should be a core extension like Mentions. They go together like peas and carrots.

                                    Or, I mentioned in the rich text editor's thread that prose mirror, which it’s built upon, may have a hashtag plugin. Maybe hashtags can at least be added to that extension. And, although it would be amazing, any hashtag extension doesn’t have to track hashtags. Just turn them into a link like this extension does. It helps tie threads together in an additional way.

                                    Now, anyone who does not use the rich text editor, you could continue using this extension despite the fact that it will be marked incompatible. The main reason I’m having this marked incompatible is due to a major conflict with the rich text extension. Just know, this extension could conflict with certain other extensions too. Use at your own risk.

                                    @jordanjay29 Please tag this incompatible. Really, it’s just incompatible with a few extensions. Depending on what someone is using Flarum for this still works. But, I don’t want people to use it and wonder why certain things stop working. Thank you!