Stuart Silvester

This bulletin is for versions older than 4.7.0, it should self-dismiss soon since you've recently upgraded.

Yes 👍🏻

When you upgrade from a version older than 4.5, you'll get prompted to complete a Marketplace set up process.
You should see an AdminCP notification for that, follow the instructions to match up your existing third party resources.

As you posted with your IPS account, can we assume that this will be a feature soon?

This is why I dislike not having it 😅
Not sure if I can list a better example on purpose.

It would be nice if Invision would stop blocking it. It is something I pay for to help with my messy grammar.
 

This issue will be fixed in a future release. Specifically it's related to being prompted for a large database update when you're self-hosted. As Marc notes, a manual upgrade at this time is the best solution.

@dutchsnowden Try it now, you shouldn't see the warning page now. You will still need to run a manual query during the upgrade though.

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;");  

Yes, that would generally be quite fast.

Here's a link to the guide, just look at the Manual Upgrade section:
 
 

bless you. thank you for this!!
I will do everything I can to make this happen!  I promise I’m trying. I really want to get there
 
Thank you so much!!

SMTP is slow, we see it time and time again.
You could then use the SES app on the Marketplace to send your email via HTTP requests instead, which is much much faster.
You could, at your own risk - create a backup etc... remove the queue items with the following query (you may need to add your table prefix if you use one)
DELETE FROM `core_queue` WHERE `app`='core' AND `key`='Follow'; But please try and get upgraded as soon as you can, we no longer support the version you're using.

In answer to your question:
There isn't one - you can only download the current available release.
My advice would be...
Put PHP 8.0.x in place now. Iron out any existing PHP related issues (theme/3rd party resource related) Upgrade to 4.7.6 (direct, there are no incrementals) Put PHP 8.1.x in place.

I would need to look back to an old version to confirm (you should really find some time to upgrade to the latest release!) but I believe the notification task from back then does both emails and inline notifications. 
Using SMTP is naturally going to cause these kinds of tasks to be slow (it's really not a fast protocol). You may be able to temporary switch to PHP processing to let them clear up.

Yes. As long as the conversion is already complete deleting the XF folder shouldn't be a problem.
The background tasks only need to rebuild/resync everything but they won't need anything from the XF folder itself.

Have a look in the 'datastore' folder, the upgrader may have already generated some caches. If you see any PHP files in there, delete them and then try again.

The datastore folder is completely unrelated to the UTF8 converter, but since it's working now that's good. After deleting the table you would have needed to restart the UTF8 conversion.

+Update,
the datastore is a 'drive me crazy' element.
The UTF convert process stopped at 14%, because it had an issue with converting Tapatalk tables.
As I dont need TT, I decided to remove all tables. Started the coverting processes again. Same problem after 14% was reached, Tapatalk was mentioned again as reason.
I followed Stuarts recommendation and cleaned the datastore - hey and voila, It worked as well

This issue will be fixed in a future release. Specifically it's related to being prompted for a large database update when you're self-hosted. As Marc notes, a manual upgrade at this time is the best solution.

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

OS's periodically update which Emoji/Unicode standard they support. You're using something older than Windows 10 21H2 so you won't see and cannot use any Emoji that was added in version 13 of the standard. Upgrading to the latest Windows 10 release will give you more emoji. 🪟🥷🏻🥸
It does look like we're missing a check to see if the emoji can be rendered in your browser, so we'll get that addressed and also take a look at the duplicate results.

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

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