matteocontrini sorry I forgot about that. Yes, it's better if you contact me privately. I can't give a price without discussing the requirements you need.

    a month later

    Rejoice! The emoji picker is now compatible with beta 8!

    This upgrade was commissioned by @matteocontrini for the FibraClick Forum

    Install on your beta 8 forums:

    composer require clarkwinkelmann/flarum-ext-emojionearea

    See first post for the new settings and a notice about the emoji set.

    I also want to remind you to consider the performance impact of extensions, and in particular this one. As we bundle the emojione and emojioneArea libraries, the javascript for this extension is > 650ko ⚠️ It's up to you to decide if it's worth it 😉

      clarkwinkelmann Beta 8 no longer uses EmojiOne, it now uses Twitter's Twemoji... shouldn't the extension have been updated to switch to twemoji instead ?

          datitisev that's true, and that's one of the reasons I initially didn't plan to update this extension.

          This extension adds emojioneArea to Flarum, which is a picker based on Emojione. Nothing can be done to easily convert it to a Twemoji picker.

          I still plan to work on a new Flarum-native picker in the future, but it will require more work.

            8 months later

            Because the internal server of the company is forbidden to transfer the external network, and the expression cannot be displayed, what can i do?
            @clarkwinkelmann

              samtto I don't understand. Are you reporting an error you are experiencing ? What's the exact error message ?

                  • [deleted]

                  • Post #109

                  clarkwinkelmann what I think @samtto means here is that the URL for the emojis is probably blocked in China, and is there a way of obtaining a local library ?

                    I think emojioneArea has a setting for an alternate CDN url, but the extension doesn't make it customizable. I also know there's some things that are hard-coded, because when I tried to make the extension use the same CDN that Flarum was using, there were still some stylesheets being loaded from another CDN.

                    I won't be making any change to this extension unless it's commissioned.

                      clarkwinkelmann
                      eg.😁
                      this img fromhttps://twemoji.maxcdn.com/v/12.1.2/72x72/1f601.png
                      not from ./img/601.png(localhost)
                      My company's network is not allowed to connect to the outside network
                      Why not make the emoticon file local?
                      How to localize pictures of emoticons?Make it possible to use without connecting to the external network.

                          samtto It's not made local by default probably because these files takes several GB of space on the server (because you have to store every single Emoji possible in case it gets used) not every Flarum admin is going to want to use all of that extra space just to have local emoji, also generally speaking it's better to serve things like emoji via a CDN because it's very possible that the emoji is already cached by the browser if you visited another site that used them.

                          As far as localizing the emoji for your use case it would require a number of modifications to this extension and the flarum-emoji extension. You would also then need to download the emoji images from the Twemoji Github to a local path.

                              All this extension does is embed the EmojioneArea library (the picker) into Flarum. We are limited to the feature they offer.

                              For any additional emoji feature a new and more advanced extension would have to be created.

                              a month later

                              I have tried install this extension via BAZAR but after installing I have got this error:
                              and the flarum is not accessible !

                              This page isn’t working64.227.80.250 is currently unable to handle this request.
                              HTTP ERROR 500

                                hamedkouhfallah did you get up to the point of enabling the extension ?

                                If you didn't get that far, it's most likely a Bazaar issue unrelated to this extension.

                                You can check your webserver logs to find what the 500 error really is.

                                  20 days later
                                  4 months later

                                  clarkwinkelmann As we bundle the emojione and emojioneArea libraries, the javascript for this extension is > 650kB, which can easily double or triple your assets size ⚠️ It's up to you to decide if it's worth it.

                                  Hi there 😀

                                  Is there any plan to reduce the load time ? Or to load the library after the composer box ? This is my only problem with this extension, particularly on mobile...