the emoji in twitter style don't work, i have many errors in the logs

Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.

 

This is a temporary error due to server unavailability https://twemoji.maxcdn.com

Edited January 9, 20232 yr by SeNioR-

 

This is a temporary error due to server unavailability https://twemoji.maxcdn.com

I hope it's temporary but this sort of post makes me think it may not: https://www.phpbb.com/community/viewtopic.php?p=15917676

 

Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.

ok, i'm wait your fix thanks

 

I hope it's temporary but this sort of post makes me think it may not:

Yes you are right, sorry for the mistake. It's not a server. MaxCDN is now StackPath so the sub-domain will no longer work.

Edited January 10, 20232 yr by SeNioR-

This has been fixed in 4.7.6, StackPath is apparently not continuing the free CDN for OSS projects (such as Twitter Emoji). We've switched it over to a different CDN (JSDelivr).

 

This has been fixed in 4.7.6, StackPath is apparently not continuing the free CDN for OSS projects (such as Twitter Emoji). We've switched it over to a different CDN (JSDelivr).

Is there a temp solution I could use?

@Stuart Silvester curious - any reason why you went with @14.0.2 instead of @latest in the CDN URL? I would have thought that going with @latest would be better going forward, considering the files being retrieved are only images (as opposed to CSS/JS)

 

This has been fixed in 4.7.6, StackPath is apparently not continuing the free CDN for OSS projects (such as Twitter Emoji). We've switched it over to a different CDN (JSDelivr).

When will the fix be applied to my forum? Seems some of my users are experiencing the problem (including me), but not others?

 

When will the fix be applied to my forum? Seems some of my users are experiencing the problem (including me), but not others?

You would upgrade your site to the latest release to get the fix there 🙂 

Thanks. I hunted it out and have applied it. Thanks for the fix.

No problem. Glad to hear that worked for you 🙂 

 

This has been fixed in 4.7.6, StackPath is apparently not continuing the free CDN for OSS projects (such as Twitter Emoji). We've switched it over to a different CDN (JSDelivr).

updated to 4.7.6 and problem solved thanks

 

When will the fix be applied to my forum? Seems some of my users are experiencing the problem (including me), but not others?

I also don't have the issue but some of my users have. What is happening is that my browser have the emojis in cache, so they are working. If i enter my site in private mode, i will also have the issue.

 

I also don't have the issue but some of my users have. What is happening is that my browser have the emojis in cache, so they are working. If i enter my site in private mode, i will also have the issue.

As mentioned above, please upgrade to the latest release where the CDN URL has been updated.

 

We've switched it over to a different CDN (JSDelivr).

but what if this domain also becomes unavailable someday? Isn't it better to add emoji to own server, like FB or Twitter did? I ask out of curiosity, thanks 😛

 

As mentioned above, please upgrade to the latest release where the CDN URL has been updated.

Yes, i will do that once i get home 😉

 

@Stuart Silvester curious - any reason why you went with @14.0.2 instead of @latest in the CDN URL? I would have thought that going with @latest would be better going forward, considering the files being retrieved are only images (as opposed to CSS/JS)

It doesn't greatly matter, there's nothing stopping us changing it in the future. At least we know what we're getting with this specific version. We'll likely add Unicode 14 to the Emoji soon too, then they'll match up nicely.

 

Is there a temp solution I could use?

The solution is to upgrade I'm afraid. The last 3 releases have been more minor in nature due to the holidays so there aren't any huge changes.

 

but what if this domain also becomes unavailable someday? Isn't it better to add emoji to own server, like FB or Twitter did? I ask out of curiosity, thanks 😛

If there's a CDN available it's better to use that for this kind of thing, plusses are potentially more performance for your end-users if they use another community/site/Twitter that also use the same CDN and you're not having to store and serve an extra 3,660 images on your server.

 

We'll likely add Unicode 14 to the Emoji soon too, then they'll match up nicely.

That would be super helpful! Much appreciated! 

I still see an error after the upgrade on twitter style:

Edited January 10, 20232 yr by AlexJ

 

That would be super helpful! Much appreciated! 

I still see an error after the upgrade on twitter style:

Have you cleared your browser and system caches?

 

Have you cleared your browser and system caches?

Yes  - did browser cache removal, purged ACP cache .. let me try clearing cloudflare cache and report back. 

Update: Clearing Cloudflare cache did the trick! @Jim M - Thanks!

Glad to hear things are functioning!

I still have an issue... is it coming from ChatBox? I am unable to figure out why we still have maxcdn calls.. on website:

 

I still have an issue... is it coming from ChatBox? I am unable to figure out why we still have maxcdn calls.. on website:

Yes, it looks like Chatbox is hardcoded to use the old CDN.

            text = (text = (text = self._parseForContent(text)).replace(this.lmn11, function(callback) {
                return 0 > self.lmn12.indexOf(callback) ? "twemoji" != ips.getSetting("emoji_style") ? "<span class='chatboxEmoji'>" + callback + "</span>" : "<img class='chatboxEmoji' src='" + ("https://twemoji.maxcdn.com/2/72x72/" + self._emojiUnicode(callback) + ".png") + "'>" : callback;
            })).replace("!", "&#33;");