Ibai

Hey!
Previousloy with IPS <4.5, when a user was adding images to a post, they weren't enabling lightbox feature unless the image was bigger than the post box dimensions.
Now in 4.5, the lightbox is always binding to any image even if the image is just a button such as this, let my try here:

As you can see, the Invision logo is smaller than the post size, so I think it does not make sense to enable the lightbox system.
This is a simple example, my users build posts with lots of images in a icon basis way, so it's very unconfortable to load the lightbox feature to them.
Is there a way to lock this feature with small images?
 

Yes, I also had this issue. Unfortunally it seems that the developer does not agree to release a new version. What a pity.

Here is my footer using this addon

@TDBF Hi. I read the whole discussion to understand if the plugin was waiting for an update and I understood that something happened with the submission.
Is there any possibility to have the plugin updated? It seemed so good, so I decided to leave this message... Thanks!

As noted above, it's probably best if you submit a ticket so we can take a look directly.

It's far easier for us to advise if we can get in and see your configuration. That said, the legacy handler is never "automatically" used. It was set during a 3.x upgrade in the file storage handler configuration, and if the /screenshots folder (in your case) is web accessible, it should not be necessary. You should be able to edit the storage handler and adjust the "Custom URL" option to remove the PHP loader.

ACP > Overview > Files > Storage Settings (Button at the top) > Configurations
From there, look for the file system storage configuration and you'll see a toggle with a custom URL.
 

You should open a support ticket.

For several days I've introduced another experiment to my live site.
I've created another template, preload_js with content:
{{foreach array_unique( array_filter( \IPS\Output::i()->jsFiles ), SORT_STRING ) as $js}} {{$js = \IPS\Http\Url::external( $js );}} <link rel="preload" href='{{if $js->data["host"] == parse_url( \IPS\Settings::i()->base_url, PHP_URL_HOST )}}{expression="$js->setQueryString( 'v', \IPS\CACHEBUST_KEY )"}{{else}}{expression="$js"}{{endif}}' as="script"> {{endforeach}}
and I put a template after the template preload_css in global templates.
My original template includeJS loads before closing body tag.
This improves the speed loading site, as well as time First paint and DOM loaded.

If someone wants to test on their site and share results.
 
 

You won't have access to the below linked item, but it is seemingly fixed in 4.6:
 

🥲 Appreciate that @Davyc!!

We definitely want to bring this kind of functionality to Pages. It's high on our list.

You are actually not. Create a new page template (Page Builder), e. g. with following code:
<div> <div class='ipsGrid ipsGrid_collapsePhone'> <div class='ipsGrid_span3'> {template="widgetContainer" group="pages" app="cms" params="'col1', $widgets, 'vertical'"} </div> <div class='ipsGrid_span3'> {template="widgetContainer" group="pages" app="cms" params="'col2', $widgets, 'vertical'"} </div> <div class='ipsGrid_span3'> {template="widgetContainer" group="pages" app="cms" params="'col3', $widgets, 'vertical'"} </div> <div class='ipsGrid_span3'> {template="widgetContainer" group="pages" app="cms" params="'col4', $widgets, 'vertical'"} </div> </div> <div class='ipsGrid ipsGrid_collapsePhone'> <div class='ipsGrid_span6'> {template="widgetContainer" group="pages" app="cms" params="'col5', $widgets, 'vertical'"} </div> <div class='ipsGrid_span6'> {template="widgetContainer" group="pages" app="cms" params="'col6', $widgets, 'vertical'"} </div> </div> </div> This would give you four columns in the first line and two columns in the second line. Change ipsGrid_spanX to whatever you like, and you have a flexible layout. Or play with columns instead of grid. 

In your theme, you should create a template. For example

 
Open this template core_global_analysis/preload_css, and add this code
{{foreach array_unique( \IPS\Output::i()->cssFiles, SORT_STRING ) as $file}} <link rel='preload' href='{expression="\IPS\Http\Url::external( $file )->setQueryString( 'v', \IPS\Theme::i()->cssCacheBustKey() )"}' as="style"> {{endforeach}} and Save.
Open your global template, and add before
{template="includeMeta" app="core" group="global" location="global" params=""} This
{template="preload_css" app="core" group="analysis" location="global" params=""}  

I have written a lot about this subject, incl. and i have a design to use the critical CSS to remove the Render-blocking CSS. Yes, it works, but it takes a lot of time to analyze and develop a good critical CSS.
For a few days I've been exploring another idea that came to my mind.
Code in IncludeCSS works perfectly and this code tells the browser - download all those CSS and use them to represent the site. But this code does not tell the browser when and how to use them.
The idea I'm using right now is - I created a new template that I put before closing the tag head. In my experiment, this template looks like this:
{template="preload_css" app="core" location="global" group="analysis" params=""} In this template I placed this code
{{foreach array_unique( \IPS\Output::i()->cssFiles, SORT_STRING ) as $file}} <link rel='preload' href='{expression="\IPS\Http\Url::external( $file )->setQueryString( 'v', \IPS\CACHEBUST_KEY )"}' as="style"> {{endforeach}} {{$customCss = \IPS\Theme::i()->css( 'custom.css', 'core', 'front' );}} {{foreach $customCss as $css}} <link rel='preload' href='{expression="\IPS\Http\Url::external( $css )->setQueryString( 'v', \IPS\CACHEBUST_KEY )"}' as="style"> {{endforeach}} Now, besides a browser command to download all CSS, I send the browser a command - use these CSS as a matter of priority.
And the result of over 100 my tests - no render-blocking CSS ...
There are no side effects or any other bad impact.
I've installed it on my live site and it works perfectly.
If a development team wishes, let him test it and apply it in later releases. This will speed up all sites using this really good platform.

Do you plan to make it a plugin or an application? Saving time could be interesting!

Smells like a bug. I’ll file one for you.

You don't need to enable that setting in ACP. It's enough changing the template bits adding the loading="lazy" property 🙂 

With a few simple template changes and some custom CSS I've change the way grid forums appear:

Forum name is under the image as opposed to being over the image and the last entry is shown below.  It just makes things look neater and tidier, at least it does for me 🙂
 

You don't need to enable that setting in ACP. It's enough changing the template bits adding the loading="lazy" property 🙂 

I can confirm our next release (4.6) will include lazy loading for profile photos. 🙂

Hey, I'm experiencing same behaviour.
GTmetrix reports slow execution times in this library. Is there any recommendation on how to solve this?

Hey, I'm experiencing same behaviour.
GTmetrix reports slow execution times in this library. Is there any recommendation on how to solve this?

I also hope in 4.5 that this is resolved. Particularly for mobile - for the desktop and now easily achieve results tending to 100.

I hope that version 4.5 give us a big boost on webpage speed. My community is suffering a lot on google ranking as long as low speed is now considered as fault that has to be corrected. After several changes, my community is not low speed anymore, but it’s not fast either, just moderate. We need better css and js loading structure for a high speed score on pagespeed insights.