Are you a GenerateCustomer?

Do you have an active GP Premium or GenerateBlocks Pro license key?

Create a GenerateSupport account for GeneratePress and GenerateBlocks support in one dedicated place.

Create an account
Already have a GenerateSupport account? Login

Just browsing?

Feel free to browse the forums. Support for our free versions is provided on WordPress.org (GeneratePress, GenerateBlocks).

Want to become a premium user? Learn more below.

Moved Meta To Bottom, Now Wrong Order …

  • This is an odd one that I just can’t figure out …

    I moved my posted and updated dates to the bottom of the post using:

    add_filter( ‘generate_header_entry_meta_items’, ‘__return_empty_array’ );

    add_filter( ‘generate_footer_entry_meta_items’, function( $items ) {
    return array(
    ‘date’,
    ‘author’,
    ‘categories’,
    ‘tags’,
    ‘comments-link’,
    ‘post-navigation’,
    );
    } );

    … in the functions.php.

    When I had them above the post, they displayed in the order posted date then updated date. Oddly, now that they are below the post, they display updated then posted. I want posted date to be first on the line like it was at the top but I just can’t get it there πŸ˜‰

  • Hi there,

    try replacing this CSS:

    .posted-on .published::before {
        content: " | Posted: ";
    }
    

    for this:

    
    .posted-on .updated::before {
        content: " | Posted: ";
    }
    footer.entry-meta .posted-on {
        display: flex !important;
        flex-direction: row-reverse;
        justify-content: flex-end;
    }
  • Such an odd one … that switched them into the correct order, but now they are centered instead of left justified with the rest of the meta and I can’t seem to create a “space | space” between the the 2 … πŸ˜‰

  • Ahh, they are right justified for somoe reason, not centered. Maybe because of the row-reverse command?

  • I edited the CSS above – should fix that

  • That did it … thanks David πŸ˜‰

  • Glad to hear that!

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