• Members 564 posts
    June 7, 2024, 6:55 p.m.

    Currently there is a redundancy in the camera information in the display of EXIF data.

    For instance:

    NIKON D750/NIKON CORPORATION 120mm 1/13s f/1.7 is displayed for a recent image.

    It would look better to omit manufacturer information "NIKON CORPORATION" as the name "NIKON" is sufficient and the extra text is just "clumsy."

    It would also look better to stop using ALL CAPs, just capitalize the first letter of the camera name, and please, use a smaller font under the image for all this information. The size of the font currently really "screams."

    Thanks,

    Rich

  • June 7, 2024, 9:11 p.m.

    I'll pass this on to the developer. But it may not get fixed until the next version is out (unless it's an easy fix).

    regards

    Alan

  • Members 2426 posts
    June 7, 2024, 11:01 p.m.

    As admin you should be able to adjust the font size by adjusting the CSS font size setting to whatever font size you like.

    The HTML element containing the exif to display probably already has a class name. If not, give it one. Then find the class name in the CSS and set the font size for it to whatever you like.

    That should be a very quick and simple fix.

  • Members 564 posts
    June 8, 2024, 12:07 a.m.

    Thanks,

    Actually the EXIF information reads:

    "Camera: NIKON D750/NIKON CORPORATION 120mm 1/13s f/1.7"

    "Camera:" is completely unnecessary in the text display.

    Rich

  • Members 2426 posts
    June 8, 2024, 3:22 a.m.

    I think Misago is written in Python but whether it's Python, PHP or any other similar backend language, capitalising the first letter of words is a very simple task.

    This is a site specific customisation and not a platform adjustment, so someone in admin should be able to make these simple customisations.

  • June 8, 2024, 8:03 a.m.

    I'm not touching CSS code. All that would do is get lost in the next update. It's not the most important thing in the world to worry about.

    Alan

  • Members 2426 posts
    June 8, 2024, 9:34 a.m.

    No, it won't get lost if done properly.

    This is a site specific customisation and so you should put those customisations in a separate css file and then copy it into the appropriate folder/directory after an update.

    github.com/rafalp/misago_docker and scroll down to "Customising Site".

    This is very quick and easy. If it's not important as you say or you don’t want to make the change as requested in the op just say so but you shouldn't fob off the op with nonsense saying the developer will do it.

    Surely you're not saying that administrators can't make site specific customisations to their Misago driven websites without the customisations being lost in a subsequent update, are you? That would be total nonsense.

    How do you think other website administrators manage site specific customisations on their Misago driven websites?

  • June 8, 2024, 2:43 p.m.

    Danno,

    I don't touch code - Martin does. I've passed the relevant information on to him and it's up to him how he does it.

    Alan

  • Members 564 posts
    June 8, 2024, 3:13 p.m.

    Alan,

    Thanks. I hope the change gets implemented at the appropriate point.

    Let's just leave it at that, for now.

    Rich

  • Members 2426 posts
    June 8, 2024, 10:09 p.m.

    It seems to me Martin is hardly involved anymore, if at all, otherwise you would have said that in the first place instead of referring to a "developer" and later assuming it was you I referred to when I said "someone in admin".

    If Martin was still actively involved and it was up to him how he implemented customisations, as you say, then there was no reason for you to say customisations would be lost in a subsequent upgrade.

    This thread explains why "development", including quick and simple adjustments, occurs at glacial speed, if at all.