Stuart Silvester

If you have a MySQL socket path defined in your conf_global.php, it's worth checking that the path is still correct for your new server.

This looks like the same report as this topic:

Your server does not meet the minimum requirements to use Invision Community, you can get our requirement checker here: Remember, to comply with our license, you should change your test site to be inaccessible to the internet and use the test license key

I would recommend submitting a support ticket so we can take a look. (go to 'Client Area' above and then click on 'Support').

It isn't purely Apple users, it's down to what software you have installed on your PC. For example if a Windows user had Quicktime or the Quicktime Codec installed (via VLC player etc) they would also be able to render the video in the web browser. This is correct, transcoding video is quite an intensive process that most web hosts won't have the required server software installed to do (yes, we know customers that run their own server can install ffmpeg, but generally it isn't on the majority of customer systems, so yes a 3rd party API would be the ideal solution). You cannot however easily transcode a video in a web browser with HTML5/Javascript. I would recommend reading a post Matt made recently 🙂

Video attachments only appear inline when the device viewing the page can natively play it (.mov is originally an Apple format, which is why it automatically embeds on Mac/iOS, MP4 is generally the most compatible over multiple devices). Our blog entry where we introduced this feature has more details - https://invisioncommunity.com/news/product-updates/43-videos-r1071 Youtube for example transcodes uploads into various formats for streaming. If you access a just published video on Youtube, you may see that it's only available in 360p since the higher quality versions haven't yet finished processing).

You may also want to consider using a profile field and then reading the value of that field in your application.

You can also upload this file (and access it via your web browser) to check that your server meets the minimum requirements for Invision Community. I suspect that your PHP version may be too old.

Hello, I would recommend submitting a ticket so we can look closer (click client area above, and then support).

You will need to upgrade manually from such an old version by downloading the files from the client area and uploading them to your server.

This is an option in our upcoming 4.5 release - https://invisioncommunity.com/news/product-updates/45-user-interface-improvements-r1182/ The administrator can define a default and the end-user can also select which method they prefer.

Both of your tickets (you only need to submit one by the way!) are currently assigned to management so they can look into the issue. They will respond as soon as they can.

If you're having issues with payments, I would suggest submitting a ticket so we can take a look. It's also worth noting that we've seen this reported where a third party payment gateway has been used that incorrectly gave payments a 'waiting' status. A 'waiting' status is one that needs administrator attention.

We currently have this message showing regardless of license status for communities that may be affected (it looks like the OP's screenshot was taken after the patch was applied, so it wasn't visible).. This isn't a 'backlog' as such, it's an error log showing emails that have failed to send.. These emails will not be sent unless you manually click the resend button on the right. The error log records are pruned after a period of time (30 days by default). You can safely leave those record if you wish and they will remove themselves.

'to' must be an array (as defined in the API Reference). Your request is passing a comma-delimited string instead.

Your ticket is assigned to management and they will reply as soon as they can (please bear with us, but you will get a response). If a plugin/application has been deprecated the author needs to let us know by submitting a ticket, I haven't personally seen any requests from @InvisionHQ asking for us to prevent purchases of the plugin but we've just made that change.

That was directly in response to the customer specifically asking about paying via PayPal. Account credit is always used to pay any pending invoices, this is how our Commerce platform works. Your ticket is currently assigned to a manager, they will respond as soon as possible.

The 'author' element in RSS2 is an email address. For obvious privacy reasons we cannot include an email address of who created a post. https://validator.w3.org/feed/docs/rss2.html#ltauthorgtSubelementOfLtitemgt

Yes, it is included in our 'Converter' application (to get it, check the box when downloading from the client area).

Sounds like an oversight to me, I have committed a change for this. Upon review from the rest of the development team the change should be included in an upcoming release.

You should have used our converter for this (It supports merging Invision Community sites), there is much more to the process changing IDs etc.

That is correct, your license will expire at the end of the period unless you manually pay the renewal invoice that will be sent to you. [For anyone else reading this in future: if you opt-in to storing credit card details for future purchases, you will be automatically billed when the renewal period comes around]

There are changes that encompass both the front-end code and the back-end code, you will be able to profile this when we start the beta process. Lighthouse is explicitly pointing out that framework.css has unused CSS, which is expected with how we currently use and structure CSS. There are rules that won't get used on an index page for example, but will get used on a content page and of course this greatly varies depending on which widgets you have on the page, whether you use a Pages page with your own customisations, whether you use 3rd party plugins or applications etc. It isn't always feasible in this kind of (customisable) software package to thin out things as much as possible depending on what we're expecting. If we did, it may end up that each page has a different CSS requirement resulting in more HTTP requests being sent (which also isn't good for performance). Rest assured, we're always looking at and implementing performance improvements and we'll continue to do so.

You're welcome to submit a ticket if you think there's a platform performance issue that's causing problems for you. However, I would also recommend seeing if you can reproduce the issue without any 3rd party themes, plugins or applications to rule those out as causing the issue. I did take a brief look at your site, which was loading fairly quickly (and complete) as a guest, your custom theme was adding more overhead with the effects. One thing that you can implement quickly to improve performance is a cache policy for your static files (such as images, javascript, css). This is something that is controlled at the server level, you can (if you're using Apache) use a .htaccess file with mod_expires rules to control this. There's a good example of relevant rules here: https://invisioncommunity.com/forums/topic/449164-how-to-speed-up-ipb-sites/?do=findComment&comment=2766078 However, since this is moving more from 'feedback' to technical support, I would recommend either submitting a ticket if there's a reproducable issue we can look at otherwise you may want to post in the peer-to-peer section of our community and other members (@adlago!) can give you some tips

We profile and refine our code for major releases, 4.5 is no exception and does contain performance related changes.