Forum Replies Created

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • in reply to: Post/Portfolio Item Tag Showing in Masonry #439461

    That’s fine, I don’t need it to be clickable. I simply want it to show which tags relate to that project.

    in reply to: Masonry – Column Issue #434963

    Cheers Josue, that worked well.

    One more thing – is there a way to ensure empty areas are filled in the masonry, regardless of the sort method? Basically to fill all spaces as a first priority, then by date or whatever other sort method?

    I’m using the ‘portrait’ and ‘landscape’ tags in order to force larger/wider/taller images.

    in reply to: Masonry – Column Issue #433851

    Hi, is there any solution to this?

    In a nutshell, the problem:

    – In a 1/1 container and selecting specific number of columns forces the boxes to be very small when the window is shrunk. It stays the same number of columns rather than reducing to a fewer number of columns.

    When not restricted to a container and selecting ‘Automatic, based on screen width’, the number of columns is dynamic. E.g. when the window is shrunk to 800px wide, it reduces to 3 columns without shrinking the box sizes. This is how I want it to behave but in a 1/1 container.

    in reply to: Masonry – Styling of Different Post Types or Tags #432604

    Works, thanks very much.

    in reply to: Masonry – Column Issue #432550

    In fact when NOT using a 1/1 container and setting it to ‘Automatic, based on screen width’, the number of columns ARE adjusted rather than the block size.

    The setting functions correctly there, but NOT when in a 1/1 container!

    Any reason why the 1/1 container is breaking this behaviour?

    in reply to: Masonry – Column Issue #432546

    Thanks. I’ve tried that previously, I think it still doesn’t work correctly…

    The problem with this is that if you reduce the width of the page to simulate smaller screen resolutions, it stays at 5 columns forcing the blocks to become very very small.

    See example below of how it should work:

    http://www.teague.com

    if you keep reducing the page size, the blocks remain the same size but the number of columns are reduced.

    So the setting I think should be the one to behave like this:

    This suggests the number of columns will reduce/increase depending on screen width, just like the teague.com example?

    Ideally it would be something like this:

    IF screen width >1650px
    columns = 5
    IF screen width > 1000px AND < 1650px
    columns = 4
    IF screen width > 700px AND < 1000px
    columns = 3
    IF screen width < 700px
    columns = 2
    END

    in reply to: Masonry – Column Issue #432527
    This reply has been marked as private.
    in reply to: Masonry – Styling of Different Post Types or Tags #431692

    That code doesn’t work unfortunately. It prevents the post from showing completely. I want the post to show, but to hide the featured image only.

    Also – CSS that works on specific post IDs is not ideal as I would need to manually add new code for every post ID. Is there no way to do it per post tag? Say I tag my news posts ‘News’, can I not use CSS to hide the featured image based on that?

    IF Post_Tag == ‘News’
    Hide Featured Image
    END

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