Ibai

It would be perfect if we could pay with marketplace credit automatic, something like a button in Account Credit page and bum… it’s paid. I would jump right away!

Also, isn’t Downloads missing in this listing?

So now I pay $150 at every 6 months. With the new model, will I pay $199 per year? Is that right?

What about current customers?

Thanks, Charles. This is a serious change that should be described on a blog or in a dedicated topic.
For me and for many clients it is breaking news 😬

The ajax-based menu manager isn’t 100% reliable. I was making some changes to the menu and ended up loosing a parent entry for no apparent reason. And because all the child-entries were set for “one-time use only”, I lost the ability to add forums, gallery and downloads. 
It would be good to add some “self-healing” capabilities. For example, when the ACP menu manager is opened, check each entry and if necessary, reset them if they link to a non-existing parent. 

I think the issue is Pages pages without Pages databases put on them. 

The Record Image field in a Pages database provides the correct og image for external linking.
Just make sure the field is enabled in your Database (AdminCP > Pages > Your Database > Fields and then the ‘Record Image’ field under “Publish Fields”). Then, for each Page record, you just select Edit, find the image field, upload up it desired image to the field and then save. 🙂

Hi, I found that extension where someone created it for a different platform. @aXenDev said he was working on an app for IPS, Hopefully, it will be released soon.

I know it was announced depreciated for v5 but will this be fixed in 4.x with update to Twitter API v2.0? 

The above is correct, but if you are struggling with anything else, there is a full guide here
 
Its worth noting however, they will be asking you to update analytic to analytics 4, not your adsense

I think it would be a good solution if the V5 version had URL Replacements built into the engine not with external plugins. Something like WoltLab Suite has. Please think about it, because a lot of forums are foreign and have diacritics in links.

Hi IPS,
Can you add in upcoming updates ability to modify sidebar width per device type (under theme/settings)? Current layout design does not allow to override that particular CSS. Read why 
 

Because downloading it all is still going to block something else from loading. So by moving all the CSS to be pre-loaded, it's actually going to block things that should and would have downloaded first. Browsers are actually quite good at prioritising these days, so you can do more harm than good by messing with the order and preloading potentially large files that don't actually need to be pre-loaded.
In an ideal world the key CSS (eg the CSS needed to render the visible part of the page) would be pre-loaded or hard coded into the html. Just not all of it. 

Also think about this - if instead of this code
{{foreach array_unique( array_filter( \IPS\Output::i()->jsFiles ), SORT_STRING ) as $js}} {{$js = \IPS\Http\Url::external( $js );}} <script src='{{if $js->data['host'] == parse_url( \IPS\Settings::i()->base_url, PHP_URL_HOST )}}{expression="$js->setQueryString( 'v', \IPS\Output\Javascript::javascriptCacheBustKey() )"}{{else}}{expression="$js"}{{endif}}' data-ips></script> <{endforeach}} put this in include JS
{{foreach array_unique( array_filter( \IPS\Output::i()->jsFiles ), SORT_STRING ) as $js}} {{$js = \IPS\Http\Url::external( $js );}} <script src='{{if $js->data['host'] == parse_url( \IPS\Settings::i()->base_url, PHP_URL_HOST )}}{expression="$js->setQueryString( 'v', \IPS\Output\Javascript::javascriptCacheBustKey() )"}{{else}}{expression="$js"}{{endif}}' data-ips></script> <link rel="prefetch" href='{{if $js->data['host'] == parse_url( \IPS\Settings::i()->base_url, PHP_URL_HOST )}}{expression="$js->setQueryString( 'v', \IPS\Output\Javascript::javascriptCacheBustKey() )"}{{else}}{expression="$js"}{{endif}}'> {{endforeach}} speed indicators are improving sharply ...

I confess to myself - I have forgotten this topic... But there is one accidental, or not quite solution that I have found.
And here I am sharing it with you.
Open the Include CSS template
Find it
{{foreach array_unique( \IPS\Output::i()->cssFiles, SORT_STRING ) as $file}} <link rel='stylesheet' href='{expression="\IPS\Http\Url::external( $file )->setQueryString( 'v', \IPS\Theme::i()->cssCacheBustKey() )"}' media='all'> {{endforeach}} {{if \IPS\Dispatcher::i()->controllerLocation == 'front'}} {{$customCss = \IPS\Theme::i()->css( 'custom.css', 'core', 'front' );}} {{foreach $customCss as $css}} <link rel='stylesheet' href='{expression="\IPS\Http\Url::external( $css )->setQueryString( 'v', \IPS\Theme::i()->cssCacheBustKey() )"}' media='all'> {{endforeach}} {{endif}}
And replace code with
{{foreach array_unique( \IPS\Output::i()->cssFiles, SORT_STRING ) as $file}} <link rel='preload stylesheet' href='{expression="\IPS\Http\Url::external( $file )->setQueryString( 'v', \IPS\Theme::i()->cssCacheBustKey() )"}' as="style" media='all'> {{endforeach}} {{if \IPS\Dispatcher::i()->controllerLocation == 'front'}} {{$customCss = \IPS\Theme::i()->css( 'custom.css', 'core', 'front' );}} {{foreach $customCss as $css}} <link rel='preload stylesheet' href='{expression="\IPS\Http\Url::external( $css )->setQueryString( 'v', \IPS\Theme::i()->cssCacheBustKey() )"}' as="style" media='all'> {{endforeach}} {{endif}}
You will eliminate render blоcking CSS without much effort...
Of course, there are other little (hard to do) tricks for even better performance, but the above will also make you smile…

You just need to set up your server correctly, it's not just CSS/JS size. 
We have optimised our cloud platform to ensure CSS/JS is served via gzip and cached correctly and Google is more than happy with it.


Invision Community 5 is removing a lot of redundant JS and CSS, and eventually we want to remove things like jQuery, but it will be a process, so it won't be done for 5.0.0 (or we wouldn't release for another year!). Likewise, user generated content generates a lot of DOM elements and a broad platform such as a forum needs a lot of CSS and JS. 

But just setting up your server correctly will get you passing core web vitals and fetching a solid score on Page Speed tests.

Us too! 🙂 

We are aware of some issues with Twitter at present. Keep an eye on our guides for any updates to those. I have it on my list to take a look at. We do not however link with v2 at all currently. Only v1

Close but still not this which is really needed
 

Now this service worker cache refresh is associated with  "Cache sidebar, header and footer blocks". This is probably the easiest solution for you, but think and find another service worker cache solution.
Cache sidebar, header and footer blocks is important for many sites with little cache time, as well as this site of yours, which uses 15 minutes. For blocks, this is fine, but every 15 minutes, a cache refresh service worker causes a site loading delay of more than 20 times the usual time.
Why, you might ask. Well here is the principle of loading a site.

This is how your site loads normally - I show the first byte time with a cache service worker

 
Usual time between 25-30 milliseconds which is very good...
But here's what happens when the cache is refreshed - every 15 minutes.
 

 
Over 20x delay on first byte.
Please consider and bind cache refresh for service worker to another task... Still a web application is not as important as loading directly to a site...
 
 

☀️ Welcome to this week's Invision Community Insight! ☀️ 
Thank you for checking out this weekly round up post. I hope you have had a lovely week and are looking forward to the weekend! 
During the summer, we slow down a bit on releasing new things and the releases will come a bit later in the months. We use this time to step away and take those much needed breaks. Also, this year, we are working on Invision Community version 5. We look forward to sharing more about version 5 in the coming weeks and months. 🎉
 
This week's updates from the Invision Community team are below. 🙂 
 
Current Happenings
Our June beta is being prepped for release next week. The June release will be available a bit later in the month.
 
New Privacy and PII Data features will be included in our June release. 
 
On Deck
Statistics and Reporting will be included in a release this summer. 
 
Finally, for those that like to see what we are up to line by line, here is the changelog for the week for version 4. Changes are limited for now as we focus attention on version 5. More information will be shared about version 5 at a future date. 
Changelog
 

Allow a meta image to be uploaded per topic. Currently it just uses the default share photo so every shared topic looks the same if shared on social media (means less clicks and interest).
This is something I’ve needed for years which I’ve not even been able to get a working mod for.

IPS is not "detecting" anything.  It's being notified of bounces and they're taking action based on that notification of a bounce or email marked as spam.  
In the IPB cloud, IPS gets notices via an API call when emails are bounced or marked as spam from AWS.  (This is because all email is sent from "noreply@invisioncommunity.com".)  When a message then bounces, it goes to AWS and AWS sends the notification to IPS to take action on it.  
In a self-hosted environment, most email providers don't provide a way of pushing bounces to an API endpoint for IPS to process.  That means nothing ever reaches the software for them to potentially take action on.  

No.  This is not an IPB limitation, but one from the mobile device itself.
Per https://web.dev/learn/pwa/progressive-web-apps/:
On iOS and iPadOS, PWAs are only installable if the user is using Safari. That means that users won't install PWAs if they use different browser apps, such as Google Chrome, Firefox, or Microsoft Edge. On both Android and iOS, users can't install PWAs from many in-app browsers, such as Facebook Mobile Browser, Instagram, Google Search App, or Gmail.