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
as always: great plugin, I like it very much so far! One thing bothers me though: it's kind of hard to determine how to override blueprints that deal with files - this is interesting to me since I'm using custom upload folders, using query, parent and upload keys in my files fields / sections. How would I override the plugin's image fields (logo, og-image etc) and section (= file upload)? Looking at the (PHP) blueprints, I guess this isn't exactly straight-forward 😅
Thanks for considering this!
The text was updated successfully, but these errors were encountered:
@CHE1RON Sorry, the plugin was not designed to deal with custom folders. We could always add another option for doing that, but I am not sure if this affects enough users.
Just spotted this: I could do this
image:
back: white
to prevent this
(but one should not use transparent PNG logos, right 😁)
Please consider open a bug in the Kirby repo for updating the pattern … this has also caused a lot of trouble for me in other projects. Setting the background to white will will cause problems with very light images, so it is not really an option.
For me it would suffice for the README saying that meta-logo (or what's it called?), og-image and files section are loaded as meta/path/to/blueprint so one could override if needed, leaving customizations (if need be) to the users!
Hey there,
as always: great plugin, I like it very much so far! One thing bothers me though: it's kind of hard to determine how to override blueprints that deal with files - this is interesting to me since I'm using custom upload folders, using
query
,parent
andupload
keys in myfiles
fields / sections. How would I override the plugin's image fields (logo, og-image etc) and section (= file upload)? Looking at the (PHP) blueprints, I guess this isn't exactly straight-forward 😅Thanks for considering this!
The text was updated successfully, but these errors were encountered: