[Resolved] block element after content – spacing not working

Home Forums Support [Resolved] block element after content – spacing not working

Home Forums Support block element after content – spacing not working

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #1523556
    Carlo

    Hi there,
    I have created a block element.
    Hook: generate_after_content
    Location: post Category -> blog

    It correctly shows up but I cannot make any spacing (margin / padding) show up.
    I set them in the generatepress blocks (container, headline…), I can see them applied in my block element preview but then they don’t work in posts.

    Please see the link: in the block there are the wpshopost list and its title above it
    For testing purpose I have applied margin to the headline (above and below) and padding+margin to the parent container (that contains both the headline and the wpshowpost list) but they all are showed up at zero value.

    Thank you. Best wishes

    #1523590
    David
    Staff
    Customer Support

    Hi there,

    what happens if you Change the CSS Print Method to Inline in Dashboard > Settings > GenerateBlocks ?

    #1523613
    Carlo

    Hi David,
    yes, now it’s working correctly.

    I am working hard on optimizing performance, do you think it could be possible to fix it stickying to “external file” css option?

    I see that the note under the settings option says “Generating your CSS in external files is better for overall performance”

    Thanks

    #1523692
    David
    Staff
    Customer Support

    I wouldn’t be overly concerned about that notice. The amount of inline CSS that GB is adding in your case is minimal and the performance improvement will be unnoticeable. Also if you’re using a Cache/Optimization plugin it will be able to combine inline CSS

    #1524041
    Carlo

    ok David, thank you. Have a nice day.

    #1524045
    David
    Staff
    Customer Support

    Glad to be of help

Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.