Limited Support
Our team is currently on holiday, so support will be limited during this period. Response times may be slower than usual, and some inquiries may be delayed.
We appreciate your patience and understanding, and we’ll resume our usual support by the end of August.
When the avatar is missing or lazy load, the username and profile is going up : https://imgur.com/a/PcSWgG8
It was occurred on the desktop view either a few weeks ago, but it seems fine here. Did you fix it?
Please fix the layout. Thanks.
There is not such an issue (see screenshot below).
Just open incognito ode and check it. Probably it's just a cache issue.
After a user is deleted and avatar is missing, the username field is going up due to missing an avatar in mobile view.
We did a lot of test. There is no such issue. This maybe only when the page is not fully loaded and some CSS code are still on the way. This is a preloading situation.
@robert Thank you for your reply.
It happens in case that avatar is missing
If admin delete user from database or turn off using avatar,
mobile view is broken because of
margin-top: -180px; }
Thank you.
That issue comes from autoptimize plugin, if you use autoptimize somehow it delays the css or affect it and you see that problem. wpForo itself doesn't have such issue.
I suggest you use this CSS code. We may add it in the core as well:
@media screen and (max-width: 800px){
#wpforo #wpforo-wrap .wpfl-4 .wpf-parent-post .wpf-left .wpf-author-avatar {
height: 60px;
}
}
@robert Your site is using autoptimzie plugin, that's not mine. If an avatar is missing for somehow(ex. Deleted user), the wpf-content-head-top is going up due to margin-top: -180px;
---------------------------------------------------------------------------------------------------
Thanks for your supports and code, I appreciate it!
Ok @youzer2020,
We fixed this issue. Here are the changes we did in wp-content/plugins/wpforo/wpf-themes/classic/style.css file:
This was changed. So I don't recommend add any custom CSS related to this issue. Just remove all custom CSS's related to this problem and wait for the update. We're currently preparing the new version, it comes very soon.
