Kjell Reigstad

Hi there, it looks like your site has some non-standard CSS that is hiding the date, categories, tags, and authors:

.post-date, .entry-categories, .post-tags, .post-author {
	clip: rect(1px, 1px, 1px, 1px);
	height: 1px;
	position: absolute;
	overflow: hidden;
	width: 1px;
}

From what I can tell, I think that’s been added via the Customizer > Additional CSS screen —?if you can find it in there and remove the .post-date, part of that code, it should show up again.

?? Try placing your <a> tags inside of the <div> wrappers instead. For example:

<div class="tag"><a href="https://www.universitaeuropeadiroma.it/test/">VAI AL TEST</a></div>

This works fine in my testing. I’m not 100% sure, but I imagine WordPress is stripping out the parent a since it’s an inline element with a block element child.

?? I’m not personally familiar with GTmetrix, but someone else here might be able to chime in to answer that part of your question.

Your code there looks a bit better, but when I visit your site I’m still seeing the old (404 Error) preloads.

Hi there! It sounds like you’re looking for a 360/panorama viewer? If so, there are a number of plugins available that are built for that sort of functionality:

https://www.ads-software.com/plugins/search/panorama/

Let me know if that’s helpful!

?? Hi there. It looks like you’d also want to adjust the bottom-margin for the h2 that lives inside that .title element. Something like this should help:

li.title h2 {
    margin-bottom: 8px
}

Hi there! It looks like your code isn’t pointing to the right location for each of those files. For example, the code above tells the browser to look for the fa-regular-400.woff2 file at the following URL:

https://sundaystyleblog.com/fa-regular-400.woff2

But that results in a 404 error, since the file is actually located here:

https://sundaystyleblog.com/wp-content/themes/stunning/assets/webfonts/fa-regular-400.woff2

To fix this, you’ll need to determine where your files are all being loaded from, and change the href value to the correct one. In this example, the code would be something like:

<link rel=”preload” href=”https://sundaystyleblog.com/wp-content/themes/stunning/assets/webfonts/fa-regular-400.woff2″ as=”font” type=”font/woff2″ crossorigin=”anonymous”>

To find the correct location for each file, you can use your browser’s inspector functionality.

• This reply was modified 3 years, 10 months ago by Kjell Reigstad.

Hi there! Themes tend to each handle this slightly differently. In the case of the NanoSpace theme, its description mentions “header builder” functionality, so it’s possible that it includes that option already. You may have luck asking in their forum here:

https://www.ads-software.com/support/theme/nanospace/

Hi there! Do the controls show up at all? Or are they just not sticking to the top of the screen?

By default, the block toolbar controls will only show up contextually, alongside each selected block. To pin them to the top of the page, there’s an optional “Top Toolbar” mode.

To activate that, open up the ellipsis (…) menu in the upper right side of the post editor. There should be a “Top Toolbar” option that you can select.

Let me know if that helps!

The simplest — but perhaps least ideal — solution to this would be to create a new “Search” page, and place a Search block inside of it. Then, you’d just need to include that page in the menu. You could even style it with CSS to show up as a search icon.

To get a full search form, the process outlined in this post seems to work, though it seems like a bit of a hack to me:

https://divinotes.com/add-the-wordpress-search-field-into-your-primary-bar/

A better approach would be to modify the theme’s template-parts/header/site-nav.php file to include get_search_form() somewhere, and then to add styles to support it.

Thanks for the heads up. This does appear to be a theme bug, and I’ve filed a ticket here to track it:

https://core.trac.www.ads-software.com/ticket/52083

The easiest way to adjust the font size of all global elements would be to adjust the root font size on small screens. For example, CSS like this would make all text on the site smaller on screens that are less than 652px wide:

@media screen and (max-width: 652px) {
	html { font-size: 0.5rem }
}

Changing the root font size is typically not a great thing to do for accessibility reasons though (users who use zoom features expect this to be a standard value). A preferable alternative would be to change the rem values of each of the theme’s font-size CSS variables:

@media screen and (max-width: 652px) {
	:root {
		--global--font-size-base: 1.25rem;
		--global--font-size-xs: 1rem;
		--global--font-size-sm: 1.125rem;
		--global--font-size-md: 1.25rem;
		--global--font-size-lg: 1.5rem;
		--global--font-size-xl: 2.25rem;
		--global--font-size-xxl: 4rem;
		--global--font-size-xxxl: 5rem;
	}
}

This also gives you more fine-tuned control, if that’s what you’re looking for. You may need to adjust values for larger screens too though, since some of these variables are used there.

The images are more complicated —?those would probably need to be adjusted on a case-by-case basis.

• This reply was modified 3 years, 10 months ago by Kjell Reigstad.
• This reply was modified 3 years, 10 months ago by Kjell Reigstad.

Hi @pflanzenoma. Twenty Twenty-One applies its button styles to any item that uses a button class.

If the theme itself is broken, you may need to delete and re-install the theme.

Ah, ok! In that case, this CSS should help. It hides the site title and tagline visually, and adjusts the site navigation so that it’s centered:

.site-branding {
    text-indent: -99999px;
    height: 0;
    width: 0;
}

nav#site-navigation {
    margin-left: auto;
    margin-right: auto;
}

Add that to Customize > Additional CSS.

From what I can see on the link you provided, it looks like Twenty Twenty-One is still the active theme:

https://www.ads-software.com/themes/twentytwentyone/

If you activate your original theme, and it still doesn’t look like you’d intended, it’s possible that any theme customizations you had made before the update were removed for some reason. I’m not sure why that might be, but someone else here may have a better idea.