You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The user said they didn’t change anything, so I checked for theme and CSS changes, and nothing should have affected that. But when I check their theme, Geologist, I found that the preview screenshot shows as they said it was. When checking posts about the launching of this theme, it also shows the header as the user mentioned, and it shows correctly on the WordPress.org theme showcase, and on its preview there (I also installed it on a WordPress.org site and it worked as expected).
It seems to have changed only on WordPress.com sites.
Workaround details
At the moment, we don't have a CSS to fix this for now.
The text was updated successfully, but these errors were encountered:
Quick summary
User reported that the positioning of elements in the header recently changed.
Steps to reproduce
What you expected to happen
For the site's title and tagline to be shown on the same line, as it shows on the theme page here: https://wordpress.com/theme/geologist
What actually happened
The tagline shows on a new line, as it's now showing on the theme's demonstration page here: https://geologistdemo.wordpress.com/
Context
Reported here: 4415469-zd-woothemes
The user said they didn’t change anything, so I checked for theme and CSS changes, and nothing should have affected that. But when I check their theme, Geologist, I found that the preview screenshot shows as they said it was. When checking posts about the launching of this theme, it also shows the header as the user mentioned, and it shows correctly on the WordPress.org theme showcase, and on its preview there (I also installed it on a WordPress.org site and it worked as expected).
It seems to have changed only on WordPress.com sites.
Workaround details
At the moment, we don't have a CSS to fix this for now.
The text was updated successfully, but these errors were encountered: