Arno Welzel

I just checked the possible support for AVIF in the backend and it works as expected. Version 5.5.2 of Lightbox with PhotoSwipe will now support AVIF as well. Just keep in mind that you should use a decent version of PHP and at least WordPress 6.5 to be sure.

The plugin has an internal list of supported image types based on the extension, since the backend also needs to be able to determine the width and height of the image.

So just adding .avif and .avifs to the list is not enough, but I have to check, if the backend code can reliably read the width/height of the images. If this is possible, I will add these types as well in the backend.

Yes, I think this should be possible since there is already a view for the subscriptions. I just can’t tell you, how long this may take since I am quite busy with other projects at the moment.

However I created an issue in the GitHub repository and try to implement this for the next update.

They are created by the plugin to cache the meta data of the images (for example width, height and EXIF data), so the images don’t have to be read all the time and the website is not slowed down too much.

Depending on the possibilities of your hosting environment you may also consider using Redis Object Cache (https://www.ads-software.com/plugins/redis-cache/), which will move the transients to a Redis database which is much faster than using the database table in MySQL/MariaDB.

French translation follows – however I am not a native French speaker, so it may contain errors:

Elles sont créées par le plugin pour mettre en cache les métadonnées des images (par exemple la largeur, la hauteur et les données EXIF), afin que les images n’aient pas à être lues en permanence et que le site Web ne soit pas trop ralenti.

Selon les possibilités de votre environnement d’hébergement, vous pouvez également envisager d’utiliser Redis Object Cache (https://www.ads-software.com/plugins/redis-cache/), qui déplacera les transitoires vers une base de données Redis, ce qui est beaucoup plus rapide que l’utilisation de la table de base de données dans MySQL/MariaDB.

Depending on what gallery you are using, you can enable the option “Show WordPress galleries and Gutenberg gallery blocks in separate lightboxes” in the “General” tab to use separate lightbox collections for each gallery.

However this is only possible, if the gallery uses the default shortcut or if you use the default Gutenberg gallery block. For other galleries this is not supported, since there is no standard way to add the neccessary meta data in the gallery output for the frontend. On the other hand, if you tell me what gallery plugin you are using, it may be possible to add the same handling there as well – it just have to check that, but I can’t promise anything.

About your sample at https://www.ciprianicomunicazione.com/archiviocapitolaredipistoia.it/museum/silent-gallery/:

The referred image is 2932×4138 pixels. If you have a screen with less than 2932 px width (which is either 2932 pixels at 100% scaling or even more on a scaled display), then zooming in will show the image to fill a viewport horizontally – for example 1920px wide – and you can scroll up and down. This is the default behaviour of PhotoSwipe and makes sense in many cases. But for the same reason you can always manually zoom in further using [Ctrl]+[mousewheel up] or similar gestures.

The zoom levels for the zoom icon can be adjusted according to Adjusting Zoom Level | PhotoSwipe – and one of the previous updates of my plugin included a change to adjust the zoom level because users complained that images are getting bigger than the viewport horizontally and they don’t want to scroll in two directions.

I will include a setting for the zoom levels for PhotoSwipe 5 in a future update.

The point of the “deep zoom” plugin is not to allow enlarging smaller images when clicking them, but to support zooming using tiled images. And tiling makes sense, if you have very large images (for example 30000×20000 pixels big). However creating the tiles for different zoom levels needs additional tools (like https://github.com/nfabre/deepzoom.php or similar) and is out of scope for this plugin. That’s why I asked how you want to provide the URL pattern for the generated tiles.

Edit: and even the example at https://dimsemenov.github.io/photoswipe-deep-zoom-plugin/ shows, that the non-tiled image can not be zoomed further. Only the tiled images can, because the provide the required image tiles for different zoom levels.

Maybe there is a misunderstanding. What you ask for, already works exactly this way – without the “deep zoom” plugin. You can already click on a larger images to zoom in. However the image needs to be bigger than the current viewport.

Example – see the image in the section “Mainboard and RAM” here – on most devices this image can be zoomed since it is bigger than the viewport when opening it in the lightbox. So when you first click it, it will fill the viewport, but you can click on the image, to zoom in further: https://arnowelzel.de/en/pc-with-amd-ryzen-7

Only for SVG images you can define a custom maximum zoom factor in the settings, because these can be enlarged without any loss of quality. But for bitmap images like JPEG, PNG etc. it makes no sense to offer zooming in more than 100% since then only pixels will get bigger but you won’t see more details. On my website I have SVG images which zoom up to 200% of the original viewbox size.

Example – see the “final schematic” image here: https://arnowelzel.de/en/alphaclock-old-meets-new

And in general: if the image is already zoomed in or there is no zoom button visible in the lightbox, but you still want to enlarge it further, you can use the “zoom in” gesture of your browser (Control+Mousewheel or Cmd+Mousewheel and of course pinch to zoom on touch devices).

• This reply was modified 2 weeks, 4 days ago by Arno Welzel.

Ok, thanks for the feedback. Hopefully, it can be sorted out. For now I’ll close this as “resolved” since I am not aware of any change in WordPress which could cause this error and Timed Content works fine on thousands of other websites (including a few I run myself).

The technical challenge is to provide the image tiles for the plugin. Also see the documentation at https://github.com/dimsemenov/photoswipe-deep-zoom-plugin which shows how to provide the URL for the tiles at different zoom levels:

data-pswp-tile-type="deepzoom" data-pswp-tile-url="path/to/tiles/{z}/{x}_{y}.jpeg"

Where {z} is the zoom level, {x} and {y} are the tile numbers within the image.

However, WordPress images are usually just single images and not a collection of tiles in multiple folders. Do you have a specific example how to provide the image tiles? And how should PhotoSwipe be integrated for this? As shortcode with parameters?

That’s strange.

wp_timezone_string() is a function documented here: https://developer.www.ads-software.com/reference/functions/wp_timezone_string/

I am not aware that this got removed with any WordPress update. So I assume, there may be something wrong with your WordPress setup.

What version do you use exactly and what PHP version?

The issue is not as simple as it looks at a first glance.

The rule does not offer fifth for the ordinal but last – because it is exactly was it says! It is only the last occurance of day, regardless how often that day will repeat in the month.

So in November 2024, the date 2024-11-25 is correct for “last Monday of November” since this is the last Monday. Even when November has only 4 Mondays – it is still correct, since the ordinal is last and not fifth. And there may be people out there using exactly this meaning of the ordinal – so I can not just change this behaviour.

What you really want is a an additional ordinal “fifth” which will be used like this: use the fifth Monday and if the month does no have five Mondays, then skip to the next month until there is a month again with five Mondays.

But this is clearly a different behaviour. I may add this with a future update.

• This reply was modified 3 weeks, 4 days ago by Arno Welzel.

In addition: the plugin is open source too – so anyone can have a look at the code and fix errors, if there are one: https://github.com/arnowelzel/timed-content

Pull requests are welcome and credits will also added if anyone contributes code.

Maybe I made myself not clear enough:

The plugin is for free. Use it or let it be. But since it is for free and I don’t get paid anything, it is just an offer. But this does not mean that I am obliged to fulfil anything at all.

I understand, that you need a solution for your commercial site to sell stuff since you also use WooCommerce. So if this free(!) plugin does not fulfil your expectations, you may have to hire someone to develop a custom solution for you.

Sorry – but as I already said: I can not help you with that. I also can not reproduce the problem. For me it works fine.

Sorry, I can not help you with that. Please ask someone to develop a custom plugin for you which solves this.

Edit: there is also no “team” – it is just me, maintaining this plugin in my free time.

• This reply was modified 3 weeks, 5 days ago by Arno Welzel.

Your problem is not the HTML code. You use some kind of “JavaScript optimizer”. Don’t do this – or if possible exclude Lightbox with PhotoSwipe from it.

Modular JavaScript (which PhotoSwipe uses for good reasons) will usually get damaged by “optimizers” and using these optimizers nowadays is mostly useless, since HTTP/2 (which your website uses as well) uses methods to avoid additional turnarounds when requesting many single resources. So it makes no big difference if you have 1 or 20 JavaScript files to load since all will be loaded with only one single connection which gets reused until all resources got loaded for the current URL.

And for the future: if you experience any problems – disable ALL caching and ALL “optimizer” first! Only then you will see, if there is any issue with your code and not just a side effect caused by any caching or optimizing plugins.

• This reply was modified 1 month ago by Arno Welzel.