Tag in widgets not displaying properly

  • Unknown's avatar
    optimisticna13 · Member ·

    I want to have my tags displayed in different sizes, as per my view in the widget settings, but whatever I do, they are displayed as the same size. What is the reason for this?

    WP.com: Yes
    Jetpack: No
    Correct account: Yes

    The blog I need help with is: (visible only to logged in users)

  • Unknown's avatar
    optimisticna13 · Member ·

    What I want:

    What I get:

  • aleone89 · Staff ·

    Hey there,

    Happy to help you with this.

    It’s possible to make this change, but this would need the Custom CSS Add-on or the WordPress.com Premium plan.

    This is because the theme is currently dictating the style of how the tag cloud displays.

    The CSS below should held change that: 

    /* Style tag cloud AL FR */

.widget_tag_cloud a {
    display: inline;
    margin-right: 0;
    }

.widget_tag_cloud a:before, .widget_tag_cloud a:after {
border-width: 0px;
}

.wp-block-tag-cloud span {
    display: none;
}

    This would be added via Appearance > Customize > Additional CSS, if either of those plans are in place.

    Are there designs or themes our there that you’re looking to emulate? Perhaps I can offer some advice on what to do next.

    Speak soon!

  • Unknown's avatar
    optimisticna13 · Member ·

    I know that a lot of stuff can be done with custom css, but this is a completly free theme, and on its own page is shown that the tags should be shown like this without the custom css.

    https://wordpress.com/theme/button-2/

  • aleone89 · Staff ·

    Hey there,

    Thanks for responding – you’re absolutely right.

    This theme relies on legacy widgets (i.e. non-block based widgets) in places, it looks like there was a legacy tag widget in place on in the inactive widget section. I’ve added this to the sidebar to show the difference between the two.

    Thank you for pointing that out! I appreciate it! :)

    I hope this helps!

  • The topic ‘Tag in widgets not displaying properly’ is closed to new replies.