askvortsov OK perfect! Maybe a clue regarding the ^ accent problem inside a list: I can't reproduce the issue on the prosemirror official demo. Concerning the second issue with the back tick, I haven't been able to test as they don't seem to have the in-line code feature

    askvortsov very useful, give a better experience.
    I will definitively use it!

    Thank you, you are amazing as always. I feel lucky to see you in Flarum.

      010101 New small bug. This ones super weird. SoundCloud links will not turn into a music player (embed) with this extension. Other URLs do. YouTube works and Twitter works. Just not SoundCloud. I know it is this extension since deactivating and clearing cache makes the SoundCloud URLs convert. And, SoundCloud URLs work here at discuss.

      @askvortsov

      In case you haven't noticed this. I just saw that the SoundCloud embed won't work if the URL is included in a regular paragraph, but if you quote the URL, then the player shows. Super strange. See:

        How to remove this extension? Is it like this:
        composer remove askvortsov/flarum-rich-text:*

          almalino

          composer remove askvortsov/flarum-rich-text

              Kulga thanks! Thatv was the correct way to remove
              composer remove askvortsov/flarum-rich-text

                5 days later

                giter Would like to add text/image "center" buttons

                I don't believe this is supported by litedown so I'm not currently planning on adding it. You might be able to accomplish this via bbcode tags.

                  ornanovitch askvortsov

                  A small update on those accent issues: the backtick issue is definitely a layout issue, nothing to do with WYSIWYG, nonetheless the circumflex issue inside lists is definitly a WYSIWYG issue (it happens regardless layout).

                  And since I'm there, another little misbehavior I have on my instance: when I press @something, if I press enter to validate a suggestion, it puts a new paragraph instead a space. Could you reproduce?

                  Thanks again, my community is absolutely happy 😀

                        ornanovitch when I press @something, if I press enter to validate a suggestion, it puts a new paragraph instead a space. Could you reproduce?

                        Noticed the same issue

                          I have a couple issues / questions 🙂

                          1. Clicking on the emoji button inserts a colon : and then new line.
                          2. With Show rich text mode toggle on editor? enabled, there are now two preview buttons. They both have a valid function, but maybe one deserves a different label? Perhaps it could be "Rich Text"... or something of that nature just to differentiate the two. Or instead it could be inversed and have "Markdown Mode". Or maybe the flarum preview button should be changed?
                          3. Is it possible for other extensions to plug into this? I'd love to be able to use @clarkwinkelmann emojione with this rich text editor.
                            Edit: number 3 seems to work afterall. Maybe a cache clear or something fixed it because it wasn't initially
                          21 days later

                          askvortsov It's working only with normal discussions, not with blogs. Hope in the future we will get it done. 😃

                          • ctml replied to this.

                              User24

                              I think for new blog posts, that extension implements its own or a modified composer/editor. For replying to existing blog posts, I think the normal composer is used so the WYSIWYG editor works there - perhaps you could verify?

                              To change that behavior so that this editor is available while composing new blog posts I think V17 team would need to update their extension, not this one.

                                  ctml I think for new blog posts, that extension implements its own or a modified composer/editor. For replying to existing blog posts, I think the normal composer is used so the WYSIWYG editor works there - perhaps you could verify?

                                  It's now working for composing new blogs... it's so much weird 🥴

                                  • ctml replied to this.

                                      User24 doesn't it depend where you are composing from?

                                      There is the "write article" option on the blog page. You can also compose directly from all discussions using the normal composer. Maybe I am wrong, I haven't updated to beta 16 so that could be new.

                                          ctml doesn't it depend on where you are composing from?

                                          I enabled Toggle between old and rich text editor in the admin page, suddenly rich text editor started working in all places 😅

                                          ctml You can also compose directly from all discussions using the normal composer.

                                          Yes, but we will get features like the SEO summary and all only when we compose blogs through that "write article" thing.