Repository Manager - thumb settings

Greetings everyone,

Does anyone know the location of the folder/file that contains ? I do know it has CSS format.

The Default is:

.ifm-thumb {
height: 30px;
width: 30px;

I want to change it to

.ifm-thumb {
height: 100px;
width: min-content;

Thank to anyone for looking into this. :smiley:

It would be a good idea to RM have these setting built-in. @Jannis

I think those conflict as you are defining a fixed height. If you want to keep the image ratio, use width: auto;

Min or max-content is better used on a parent container than an element itself. Although you can do that.

I haven’t checked with repository manager where the CSS file is for it, but I wouldn’t edit it there, as an update will likely restore what you edit. Create an override, but then there is probably a practical reason, the thumbnail is fixed width and height, I haven’t used it for a while and can’t recall the interface. But I’m sure @jannis can clarify.

1 Like

Greetings my friend,

Somewhere a CSS (not this one (all.css) because I did change it and it did nothing )

.ifm-thumb {
    height: 100px;
    width: auto;
}

After some long examination the index.php had the incorrect settings. The ones below are the correct ones.

data-display-thumbs=“1”
IFM::init ,0,2000,2000,1

My thoughts are Repository Managers may be exported the incorrect settings. Yes, the produce Thumb is check in the Bric.

What makes you think that?

What’s your actual goal? Because I suspect this requires backend and front end modifications.


By the way, big plug for Repository Manager, it’s an excellent bric. I’ve used it on a client site that saved me a ton of time.

I could edit json files to make daily updates for event information.

1 Like

Hey Pete because I changed them to what they ought to be and I can now see the thumbnail images. I could be wrong but I think the export for RM is keeping its settings.
You ask why is because both of those settings were 0 when they should have been 1

Try to remove RM from the page and add it again.

You’ve had issues with it in the past, and it was always a user issue.