Stuart Silvester

Yes it is! First of all though, you'll need to upgrade your PhpBB site to v3.1 or v3.2 and then you can use our converter application to complete the conversion. If you're using Invision Community 4.4 it's super simple to do (as shown in the video above).

You can find them in the `convert_link` table, they're logged as (type) 'core_attachments'.

The UI is greatly simplified so that this information isn't visible, we do however still log any issues to the database so that can be reviewed. It's important to remember that the converted counts won't always match, we mostly see this with vB where the database can contain a lot of orphaned data. Yes, any required rebuilds and processes are automatically started when the conversion is completed. Thanks for the feedback! The converter saves ids for almost everything converted, vBulletin attachment.php URLs will be redirected automatically to the relevant location. We try to redirect as many (important) URLs as possible.

Total Spent is based on transaction data, generated invoices will be included if they have been paid through Commerce.

You can find our product update about PWA (not fully-blown PWA) related changed in 4.4.

We do set the container size in content, there was a minor issue where this wasn't occurring for images inserted via Giphy. We've fixed that now (although, not yet live on here). If you insert images from any other source for example, you'll see container sizes being set.

If you have your community configured to use 'site traffic' to run tasks, it relies on the amount of traffic your community receives. For best speed and reliability, switch your task method to use CRON. (search for tasks in AdminCP).

Invision Community 4.4 will have support for PHP 7.3. Follow our product updates for further information about new features and changes in 4.4.

This topic is actually quite a good indicator of why it isn't supported (it's only supported as a legacy system for customers that upgraded from 3.x). FTP/SFTP wouldn't be be reliable at all for the kind of files you use on your community. If you were using this I would expect that you would be reporting issues that couldn't be resolved without switching to a native storage solution. A NFS/SSHFS approach would be far more reliable and quicker.

The alpha is a preview site, it isn't yet available for customers to download. When we reach the beta stage, customers will be able to download and install on their own platforms.

Whoops, I meant 'announcement screenshot' 😄

There's also a new option to have announcements just be text that doesn't link to anywhere. 🤫 This is something that's rolled out everywhere in the platform, not just on member profiles. The announcement screenshot above gives a good idea of what this looks like on the forum index, you'll note that my name is in red. Where the sidebar widgets are shown depends on how you have your sidebar configured. It's all to do with the flow of HTML (sorry for getting technical), if the sidebar is on the right then the widgets are in the HTML after the page content. If they're on the left, they are before the page content. When the page is condensed down to a single column, it is this structure that determines where those widgets are displayed. Quite simply though, if you have a widget that's important enough to display on mobile, you would check the 'mobile' option in the widget settings.

We use whatever PHP defines as the 'default' algorithm in your PHP version. At the current time, that is blowfish for all PHP versions. Argon2ID was added in PHP 7.3 and would be eligible to be the default algorithm in PHP 7.4/vNext, although there's no guarantee they'll do that. http://php.net/password_hash

We've announced the inclusion of application manifest functionality in 4.4, which lays the groundwork for future enhancements

Languages get set based on the headers the browser sends. So if you have a language installed that matches the users browser, they'll see that as their default language.