You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 11, 2024. It is now read-only.
The pagetable section seems to not show a small thumbnail but the original image instead. Can this be? It occurred to me in 2 completely separate installations, both running the current Kirby and current plugin version. This makes the backend very slow. It happens on my Apache web host and locally, while the thumbnails for the regular page sections get delivered as usual.
Came here to post the same issue! Looks like this issue came up before (looking at commit logs) but I can confirm that a fresh install of the latest version of pagetable is still loading original images.
s3ththompson
added a commit
to s3ththompson/kirby-pagetable
that referenced
this issue
Feb 11, 2021
The pagetable section seems to not show a small thumbnail but the original image instead. Can this be? It occurred to me in 2 completely separate installations, both running the current Kirby and current plugin version. This makes the backend very slow. It happens on my Apache web host and locally, while the thumbnails for the regular page sections get delivered as usual.
It looks like the thumbnail image gets selected here:
https://github.com/sylvainjule/kirby-pagetable/blob/master/lib/pagetable.php#L200
using the
panelImage()
method:When I look at the definition of that method
https://github.com/getkirby/kirby/blob/3.5.1/src/Cms/ModelWithContent.php#L388
it apparently takes only one argument:
Can this somehow cause for the section to show not the usual 72x72 thumbnail, but the original image instead?
I played a little bit to try different inputs in that
$settings
-thing, but I couldn’t manage to get the desired result.Can someone reproduce the problem? Or am I the only one? ;)
The text was updated successfully, but these errors were encountered: