Grey empty blocks (and one square) displays in the very top header area

Hi there,

Any chance you can disable all plugins except GP Premium to eliminate conflicts from other plugins first?

This wouldn't be a GP issue :)

Let me know :)

Thanks Leo,

Plugins were not the issue it seems.

This happens in every GeneratePress site I've loaded - When using the site library option named "Marketer", here: https://generatepress.com/site-library/

I cannot catch it in the page source, I cannot catch it in web tools (inspect element).
I only noticed this after there were some GeneratPress updates.

Any ideas?

When used, it adds the below CSS to "Additional CSS" in the Customize panel:

/* GeneratePress Site CSS */
.inside-article,
.sidebar .widget,
.comments-area {
	border-right: 2px solid rgba(0, 0, 0, 0.07);
	border-bottom: 2px solid rgba(0, 0, 0, 0.07);
	box-shadow: 0 0 10px rgba(232, 234, 237, 0.5);
}
/* Featured widget */
.sidebar .widget:first-child,
.sidebar .widget:first-child .widget-title{
	background-color: #ffffff;
}
.sidebar .widget:first-child a,
.sidebar .widget:first-child a:hover {
	color: #000000;
}
.separate-containers .page-header {
	background: transparent;
	padding-top: 20px;
	padding-bottom: 20px;
}
.page-header h1 {
	font-size: 1.5em;
}
.button, .wp-block-button .wp-block-button__link {
	padding: 15px 25px;
}
@media (max-width: 768px) {
	.post-image img {
		max-width: 100%;
	}
} /* End GeneratePress Site CSS */

I'm not too sure how that's effecting the display of those areas (the 5 grey areas in the screen shot), so maybe it's something else in it?

Is anyone else seeing the same thing when using "Marketer" from the site library?
Again, those areas appear, the disappear - And yeah... It's starting to drive me nutty :D

Any help appreciated.
Much thanks!
Roger

We've not had any reports on this so I don't believe it's actually a bug from our end.

Does the same issue occur if you use a incognito/private mode?

Does it happen on every browser?

Thanks Leo!

It was the result of a plugin. After deactivating, clearing the cache, then reactivating, the issue went away.
(Strange that it did not do this earlier).

Nevertheless... Thanks! :)

No problem :)