Picture Crop issues

Home Forums Jevelin Theme Picture Crop issues

Home Forums Jevelin Theme Picture Crop issues

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
  • pixlus
    Participant

    Please for the next update of Jevelin WP Template

     

    1. Please use the same Blog style “Masonry Style” image placement code, and apply it to the all the other image placements in “Blog post” page it’s self and in the “Latest Posts” and “Released Posts” images as well on the Blog page. See link:https://jevelin.shufflehound.com/blog1/2016/11/23/first-steps-in-the-right-direction/
    2. The ask is to use the same fixed (locked) aspect ratio applied to the image. Then use auto sizing CSS or code to not allow any cropping to occur in the three image place holders as above. This will place all the images in their appropriate sizes with no cropping. No matter the size or shape or resolution.

     

    This has been an on going issue and there is no real way around it. You have developed quite nicely this exact same code in the Masonry Style Blog lists on the main pages here:

    https://jevelin.shufflehound.com/blog1/masonry_sidebar/

    Just apply this code to the other three places, please…  🙂

    You will make all the customers very happy and avoid many support tickets.

    Thank you

    • This topic was modified 4 months ago by pixlus.

    Hi @pixlus,

     

    I hope you are well today and thank you for your suggestions.

     

    We will consider this to be implemented in the future version of the theme.

     

    Best regards,
    Shufflehound team

    Hello,

    Any progress on the picture crop bug? I saw several code releases but no fix?

    thx!

    The suggested enhancements are not implemented yet but will be developed ASAP.

    pixlus
    Participant

    Thank you for your reply. Appreciate your willingness to get the fixes in. Will check back in a week or two.

    thx!

    You are most welcome here 🙂

    Have you had to time to work on this bug yet? It has been a couple months since the request was put in.

    Thx

    We are considering this as an enhancement and not a bug.

     

    We are working on it to implement it.

Viewing 8 posts - 1 through 8 (of 8 total)