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
It is going to be really hard to manage sponsor images with the current model using an image URL under the current design.
Problems:
Sponsors will provide us URLs, but will be all different shapes and widths
When displayed on the sponsor page, they don't fit and format as expected since the size is crucial
To fix the size and format, one will need to download the image and tweak it to work. Then upload again to another location and reference the URL.
It would be better to add an upload capability on the add sponsor page, that automatically resizes the image for the user. I've done this before on another project, and used a great plugin that takes care of this.
A few easy work arounds may be to specify the required image dimensions in help text on the add sponsor page. Or to you inline styles css to size the image x&y on the image tag of the sponsor listing page.
The text was updated successfully, but these errors were encountered:
Note: as a stop gap I have updated the CSS to have a maximum width and height but since that won't work in order browsers we need a better solution. See: c191d6a
The design assumption was that logos would be uploaded in the webroot of the main app so the manager would have full control over the image sizes already.
It is going to be really hard to manage sponsor images with the current model using an image URL under the current design.
Problems:
It would be better to add an upload capability on the add sponsor page, that automatically resizes the image for the user. I've done this before on another project, and used a great plugin that takes care of this.
A few easy work arounds may be to specify the required image dimensions in help text on the add sponsor page. Or to you inline styles css to size the image x&y on the image tag of the sponsor listing page.
The text was updated successfully, but these errors were encountered: