Hi Andrew,
This is how the system work:
1) Primary download file field type: can be any type of file limits: subject to restrictions by the selected category, license and your quota limit shows-as: "Choose a file..." used-in: download button and full-view button (for images)
2) Rendering file field type: raster images only size: resized to 780x600 or smaller upon upload. shows-as: "Choose visible image..." generated: It will be generated from the download field should the download field be an image and none user specified. We currently don't render svg files though. used-in: item view page, if not available thumbnail is used on the page.
3) Thumbnail file field type: raster images only size: resized to 190x190 or smaller upon generation show-as: NOT SHOWN TO USER in the upload field generated: Always generated from the 'rendering field' after the rendering field is possibly generated from the download field. used-in: gallery listings, if not available a mime-type icon is used in it's place.
The upload form is configured to give errors ranging from image-size, file-size and many other such errors. If there's a situation where you upload a rendering and it only appears as a 190x190 thumbnail and the original image seems to have been eaten by a gru, let me know, this is a bug.
Best Regards, Martin Owens WEBSITE.info
On Sun, 2018-07-08 at 23:13 -0700, Andrew Kurn wrote:
When I upload an /extension/ first I see a page with 2 upload icons, box and a big white arrow. After I upload the extension the lefthand one becomes a cardboard box. The righthand one is for a picture to go with it. It appears in the gallery of extensions.
For the picture, if I upload just any old picture, the cardboard box is what appears in the gallery, not what I uploaded. The pic has to be 190 x 190 before it will appear.
So /that's/ what I'm talking about when I say an error msg would help
then, when I'm uploading the pic, it would be good to know it's too big to work.