Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • Karunya Chavan

    (@karunyachavan84)

    Thanks for providing the steps to reproduce the issue.

    The bug was caused by the heading decoration rule in the theme’s shared post-section-dash mixin.

    It uses content: "\020" for the :before pseudo-element that draws the line above headings. In the editor, when a heading block is empty and underline decoration is active, that whitespace character can render as a visible hyphen.

    The fix is to keep the pseudo-element itself, but change its content to an empty string (content: "") in the SCSS source themes > twentynineteen > saas > mixins > _mixins_master.scss as shown below, then rebuild the theme assets:

    @mixin post-section-dash {

    &:before {
    background: $color__text-light;
    content: ""; // patch.
    display: block;
    height: 2px;
    margin: $size__spacing-unit 0;
    width: 1em;
    }

    That preserves the horizontal line above headings while preventing the stray hyphen from appearing in empty heading blocks.

    Karunya Chavan

    (@karunyachavan84)

    To make the image display full width, first select the parent Group or Row block, then set that container to Full Width alignment.
    After that, the Image or Cover block inside it will be able to expand properly.

    Try:

    1. Select the outer Group block
    2. Set Alignment → Full Width
    3. Then select the Image/Cover block and also choose Full Width if available

    This might resolve the problem. Refer below image for visual guidance:

    https://drive.google.com/file/d/1MK9b1HxWx25kza0TOiId4XGDPFbgBoee/view?usp=sharing

    Karunya Chavan

    (@karunyachavan84)

    Hello @yavman49,

    You can center the button by arranging the blocks in the same hierarchy as shown in image below:

    https://drive.google.com/file/d/166dtKINIAFMkxmAlCyr15bZ39acvV8h3/view?usp=sharing

    Ensure that you are selecting Buttons block and justifying it as center, let me know if this works for you.

    Karunya Chavan

    (@karunyachavan84)

    Also, if possible, make these changes in a child theme so they are not lost during future theme updates.

    Karunya Chavan

    (@karunyachavan84)

    The “Archives” and “Meta” sections you are seeing are default fallback widgets added by the theme when no widgets are assigned to the sidebar widget area.

    In your theme’s sidebar.php file, you’ll likely find code similar to: (You can find this file under Appearance -> Theme File Editor)

    <?php if ( ! dynamic_sidebar( 'sidebar-1' ) ) : ?>
    

    The theme uses this to display default content whenever the sidebar is empty.

    If you do not need those sections, you can either comment out or remove the fallback Archives and Meta blocks from that file. Removing the fallback entirely is usually the cleaner long-term approach as,

    <?php
    /**
    * The Sidebar containing the main widget areas.
    *
    * @package Vision Lite
    */
    ?>
    <div id="sidebar">

    <?php if ( ! dynamic_sidebar( 'sidebar-1' ) ) : ?>
    <?php endif; // end sidebar widget area ?>

    </div><!-- sidebar -->
    Karunya Chavan

    (@karunyachavan84)

    The buttons are inside a separate Buttons block, while the albums are inside a different Group block. Because of that, the editor is trying to keep everything aligned to the block grid, so the buttons cannot be freely dragged above each album.

    A better approach would be to use a 4-column layout and stack each column as:

    • the year button at the top
    • the corresponding album iframe underneath

    That way, each year label will naturally stay aligned with its album.

    Karunya Chavan

    (@karunyachavan84)

    Are you using any CDN or server-level image optimization (for example Cloudflare or a LiteSpeed-based host)?

    In a default WordPress setup, large images are scaled down to 2560px on upload, but they shouldn’t be further reduced to 1600px when accessed directly via URL. That kind of behavior is usually caused by a CDN or hosting layer that dynamically resizes images on delivery.

    If you are using one, try temporarily disabling image optimization there and check again.

Viewing 7 replies - 1 through 7 (of 7 total)