I just tested 5.6.3 on my development server and intentionally lowered the available PHP memory to the bare minimum 32Mb WP default (looks like you have about 128Mb allocated for WP). I ran a script to open 100 browser tabs for logged out users, and no issues.
I cannot replicate the issue, and a generic “memory exhausted” error for “class-wpdb.php” doesn’t help diagnose it any. NOTHING related to the DB was changed in 5.6.3. The only changes made were for BuddyPress visibility handling, better handling of Style Pack shortcodes, and a new Arabic translation. Nothing else was changed, and certainly not any changes related to the DB in any way.
I’m not trying to avoid or deflect the issue you’re having, but I’m pretty certain that nothing changed in Style Pack that would directly cause the issue.
I just checked the stats of the plugin, an we’ve had about 2,500 sites update to version 5.6.3 and no one has reported this issue. You’re the first. That indicates that it’s something unique/different about your specific setup, not the plugin itself.
Let’s start with some basics to try to resolve this issue for you:
Are you using BuddyPress or any of the Style Pack shortcodes?
Did you update any other plugins at the same time as Style Pack?
Are you getting any other errors or warnings in your debug log besides generic “memory exhausted” errors for “class-wpdb.php”?
@scarlettr8 – version 5.6.3 was just released and included changes to BuddyPress integration. Now the profile visibility settings setup in the Style Pack “Profiles” tab only affects actual profiles, but not any other part of BuddyPress. That means your BuddyPress-specific groups/forums/blogs/etc will load as expected regardless of what you have setup in the Style Pack “Profiles” tab. Check it out and let us know if you have any other issues with BuddyPress profiles and Style Pack.
@charityanna – version 5.6.3 was just released and includes better handling of shortcode optional values, and a MAJOR Shortcodes settings tab overhaul. Check it out and let us know if you have any other issues with shortcodes.
I see the code snippet I provided fixed the role alignment when hitting the 480px width and smaller responsive display.
I also still see responsive single column display for the 480px width break-point which seemed like the main thing you wanted to change in the first place.
I see the responsive functionality still happening at 480px break point:
One thing I do see is that the role is not aligning with the rest of user profile info when displaying responsively. It’s working fine on my development server, but not on your site (again, something weird with the template styling or theme?).
To get the user role to align with the rest of the user profile info, you can add this CSS snippet to your Custom CSS tab in Style Pack:
/* profile role alignment fix for responsive display */
@media only screen and (max-width:480px), @media only screen and (max-width:320px), @media only screen and (max-width:240px) {
#bbpress-forums div.bbp-forum-author .bbp-author-role > *, #bbpress-forums div.bbp-topic-author .bbp-author-role > *, #bbpress-forums div.bbp-reply-author .bbp-author-role > * {
text-align: left;
}
}
If you do end up removing responsive display for the 480px width, just remove “@media only screen and (max-width:480px),” from the code above.
What you’re asking for is not an issue with Style Pack, and will take many hours to re-write CSS code to accomplish what you want properly. Far beyond the scope of free plugin support for Style Pack.
I think the better question is: what’s breaking the default responsive styling in the first place?
Figure that out, and you may be able to replicate it without having to write hundreds of lines of CSS code.
If you can’t figure out what’s breaking the responsive functionality and then replicate that, a quick and easy solution would be to find all media queries and change them from this:
@media only screen and (max-width:480px)
@media only screen and (max-width:320px)
@media only screen and (max-width:240px)
NOTE: This will make your site look really bad and hard to read on mobile devices, especially with small display screens. But that seems to be what you want. Maybe you could just make that 1px change to the 480px media query, but allow responsive functionality for 320px and 240px. Your site, your choice.
NOTE: You will lose those changes any time you update your theme or the bbPress plugin! You will have to reapply them any time you update the theme or bbPress. You may want to look into using a child theme so that your changes get preserved after theme updates. Not much you can do about bbPress overwriting your changes, so you’ll have to do them again to bbPress after updates. Good new is that bbPress updates are spread out, sometimes years apart so you won’t have to reapply that code change often.
This reply was modified 2 years, 9 months ago by codejp3. Reason: updated file paths to edit
The second picture is the correct one. That’s default bbPress behavior.
It’s called “responsive” display. bbPress does this by default so that the forum content looks good on mobile displays as well as desktop displays. If your site is not doing that even with Style Pack deactivated, then you have something wrong with the default bbPress template, or your theme, or a conflicting plugin.
The CSS code responsible for doing that is located in /wp-content/plugins/bbpress/template/default/bbpress.min.css
It uses a break point of 480px wide. Larger than that and it displays 2 columns. Smaller than that, it displays 1 column. There’s also “@media” breakpoints for 320px and 240px, with even more changes for smaller displays.
Your only real option is to write a lot of custom CSS to override the responsive functionality.
Take a look at: /wp-content/plugins/bbpress/template/default/bbpress.css (lines 1408-1704) & /wp-content/themes/sahifa/css/bbpress.css (all throughout the whole file)
Those 2 files handle everything related to responsive display functionality. Whatever is in those 2 files wrapped in a “@media” query wrapper is what you will need to override with the CSS values “unset !important;” or “revert !important;” in order to prevent the default bbPress from being responsive.
Next, remove the inline style you have for .bbp-user-section in the profile template page. It should NOT have a top margin of -2000px. It should have no top-margin value at all.
If you are not able to remove the inline styling, then also add this to the Custom CSS tab in Style Pack:
.bbp-user-section {
margin-top: 0px !important;
}
End result:
Marking as resolved, but feel free to ask questions if you still have issues.
I was wrong about the @abdurhman location. For the profile page, that is the correct position. It’s within the foum where it is under the profile picture.
I am not able to replicate the issue you’re experiencing.
It is displaying fine on my dev server:
I am looking at the source code on the link you provided to see if I can find where your site is breaking that layout. Possibly a theme issue, or custom CSS issue. I’ll update this topic if I find the source of your issue.
A side note – it probably has nothing to do with this issue, but you do have plenty of errors showing on that forum index page in dev tool. Most of them relate to font files not loading. They are incorrectly using (sanitized for security reasons):
You may have a “wp_content_dir” being used where it should be “wp_content_url” somewhere in your code related to font files.
Other issues relate to CloudFlare. Probably not causing issues with the forum index freshness, but certainly slowing your site, filling error logs, and not fully/properly utilizing CloudFlare:
The update will not address anything related to your issue. It only includes some minor enhancements to shortcodes and BuddyPress integration. The plugin is already compatible with the latest version of WP as-is. I’m just simply updating the plugin readme file to reflect that.
Like I said, I’m pretty sure your issue has to do with the recent speed-up/caching tweaks you added.
Put your site in maintenance mode, disable Style Pack, and refresh the forum index and see if it displays the last topic freshness info properly. If so, then there may be a compatibility issue with Style Pack and one of those recent changes you did. If the forum index freshness still shows incorrectly, then your issue has nothing to do with Style Pack.
The main forum index shows that the subforum “Website Updates” was last updated 1 month ago.
When you go to that actual subforum, it shows an update you just posted today.
That new post explains a bunch of caching and speedup tweaks performed on your site. My hunch is that the forum index not updating has something to do with one or more of those website speedup tweaks. I know you said you’ve tried playing with them/clearing them, but that’s still my hunch and the only “known” thing that has changed on your site recently.
I can confirm on my test site that Style Pack is compatible with the latest release of WordPress and will be updating compatibility with the next release (any day now after I finalize a few things).
I do still think the issue is going to be linked to those recent changes….but you can try this:
Go to WP Admin > Tools > Forums ( /wp-admin/tools.php?page=bbp-repair )
Run the “Recalculate last activity in each topic and forum” repair action.
Let’s see if that makes a difference before getting more involved.
This reply was modified 2 years, 10 months ago by codejp3. Reason: fixed minor typos
Viewing 15 replies - 91 through 105 (of 407 total)
