[David Morgan]

This content is restricted to Organic Themes members with an active subscription. Login here.

[David Morgan]

This content is restricted to Organic Themes members with an active subscription. Login here.

[David Morgan]

This content is restricted to Organic Themes members with an active subscription. Login here.

Attachments:

You must be logged in to view attached files.

[David Morgan]

This content is restricted to Organic Themes members with an active subscription. Login here.

[David Morgan]

Hi Diana,

We’ll be happy to help.

1. I’m not sure what you’re referring to by “post_folder” as that is not a post type or taxonomy that should be available for selection. Can you provide screenshots to illustrate this issue? As a workaround, you can use the Query Block instead of the Posts Block.

2. Do you have a link to illustrate this? This is an example of an archive page from the theme demo exhibiting the default behavior, and only displaying posts with the “Featured” category applied, https://stax.organicthemes.com/blog/category/featured/

3. You can accomplish this using the Query Block instead of the Posts Block, and arrange each element in the desired order within the editor.

4. Unfortunately, making the whole slide a link is not an option with the plugin at this time without customization.

Thanks!

[David Morgan]

This content is restricted to Organic Themes members with an active subscription. Login here.

[David Morgan]

Hi Diana,

Did you remove the previous styles affecting the menu before adding these?

Also, can you leave the provided styles active on the site for long enough for us to inspect how they have been added, and if there are any other styles overriding the provided styles?

Thanks!

[David Morgan]

This content is restricted to Organic Themes members with an active subscription. Login here.

[David Morgan]

Hi Diana,

I addressed the length menu and sub menu offset in your other forum post. However, I can help with the logo issue mentioned here. Most likely, the secondary logo that was in the header was removed, which is why the logo is not transitioning. In order to resolve this, you can clear the customizations for the header template part in order to restore the header to its original state. Or you can provide us with your WP login information in a private reply so we can add this functionality back for you.

Thanks!

[David Morgan]

Hi Alexis,

Thanks for reaching out, and we’ll be happy to help.

Can you please provide a link to the page illustrated in your screenshots so we may inspect the code?

Thanks!

[David Morgan]

Hi Diana,

Sure, we’ll be happy to help.

1. Regarding the lengthy menu, I think the easiest fix here is to decrease the font size slightly:

.wp-block-navigation__container .wp-block-navigation-item .wp-block-navigation-item a {
    font-size: 75%;
}

2. In regards to previously provided CSS, try this instead:

@media (min-width: 782px) {
    .wp-block-navigation .has-child .wp-block-navigation__submenu-container .wp-block-navigation__submenu-container {
        right: 100%;
        left: auto;
    }
}
.wp-block-navigation__responsive-container:not(.is-menu-open) .wp-block-navigation__container .wp-block-navigation__submenu-container::before {
    position: absolute;
    top: 0;
    left: 0;
    width: 100%;
    height: 100%;
    content: '';
    padding: 0;
}

I hope this helps.

Thanks!

[David Morgan]

Hi Diana,

No problem. We’ll be happy to help:

1. Within the Additional CSS section of the Customizer or Editor, add the following style:

@media (min-width: 782px) {
    .wp-block-navigation .has-child .wp-block-navigation__submenu-container .wp-block-navigation__submenu-container {
        left: -240px !important;
        max-width: 200px;
    }
}

2. I would recommend using the Navigation Block within the Appearance > Editor. You can import menus into the Navigation Block that have been created using the Appearance > Menus. You can learn more about using the block here, https://wordpress.org/documentation/article/navigation-block/

3. Unfortunately, not yet. This is a core WordPress block and functionality, and not controlled by the theme. WordPress intends to add more mobile options to the navigation block in the future. In the meantime, breakpoints need to be forced via CSS, https://stackoverflow.com/questions/74956603/wordpress-navigation-block-how-to-change-mobile-breaking-point

I hope this helps.

Thanks!

[David Morgan]

Hi Diana,

The Organic Blocks plugin should be used with STAX — NOT the Builder Widgets plugin. The Builder Widgets plugin is designed for older PHP based WordPress Themes. Since STAX is a block theme, it’s designed to work with blocks, not widgets. The Organic Blocks plugin retains most the functionality of the Builder Widgets, but using blocks instead of widgets. The exception is the toggle widget. However, you can download this plugin for adding a toggle block, https://wordpress.org/plugins/toggles/

Builder Widgets will override the customizability of the STAX theme, rendering the power of the STAX theme useless. Adding Builder Widgets to STAX is kinda like buying a new electric car and replacing the engine with an old diesel engine. Builder Widgets are still useful for people using older themes, but it’s not a plugin I would recommend for block themes like STAX. I hope this helps clarify the issue.

Thanks!

[David Morgan]

No prob, let’s try a minor adjustment:

.wp-block-navigation__container .wp-block-navigation-item:not(.button) a::after {
    background: red !important;
}

That should do the trick!

[David Morgan]

Thanks for reaching out, and I’m sorry to hear of your issues!

For clarification, the Organic Blocks plugin should be used with STAX, NOT the Builder Widgets plugin. While the Builder Widgets plugin is technically compatible with STAX given a couple prerequisites (you will also need the Classic Editor and Classic Widgets plugins installed), using Builder Widgets with STAX kind of defeats the whole purpose of using the STAX Theme. Since the STAX Theme is a block theme, it’s designed to work with blocks in the latest editor — not widgets.

The Builder Widgets plugin was developed for older PHP based themes that do not utilize the benefits of the new modern WordPress editor. The plugin is still useful for older themes, but it’s unnecessary for STAX. In fact, I wouldn’t recommend Builder Widgets plugin for any block-based theme. The Organic Blocks plugin adds all the functionality of the Builder Widgets plugin, but within the form of blocks instead of widgets. Additionally, the blocks are much more flexible and user friendly when working with a block theme.

I hope this helps clarify things. Let us know if there is anything else.

[Author]

Posts