codejp3

It has been a very busy time in my life lately. Give me a little bit to get to a good stopping point when I have access to my server and I’ll post some CSS snippets for you. One for site-wide and one for forum-only. Should be within a few hours at most.

Let’s start even easier than that.

Deactivate Style Pack and see if the issue still exists. I’m pretty sure breadcrumbs will still not be displayed.

There’s a 99.9% chance your issue is with the theme you’re using or the Elementor shortcode you’re using. If breadcrumbs still do not display after deactivating Style Pack, look at your theme settings, and Elementor shortcode settings.

You can try switching to a default WP theme to see if it’s your theme.

To determine whether it’s Elementor, you can use the default bbPress slug /forums/ without any shortcode and disable Elementor. If you absolutley have to use a shortcode, try using the default bbpress shortcode ( [bbp-forum-index] ) instead of Elementor.

@danwassink – you’ve got mail!

Since this issue is not exclusively a Style Pack issue, but an overall issue with the WP Engine plugin being used on a local dev environment, I’m going to close the topic as resolved. Feel free to post back here if you have any additional questions.

It was working fine on my dev server, but I do see why you are getting those warnings, and the fatal error they lead to. I revised the code to address that.

Re-download and replace those 2 files to test it out again.

1.) /wp-content/plugins/bbp-style-pack/blocks/bsp-latest-activity-widget.php

2.) /wp-content/plugins/bbp-style-pack/includes/widgets.php

https://codejp3.com/wp-content/uploads/la_widget/bsp_la_widget_update.zip

You can see about 10 different examples running on one of my dev sites (bottom widget area). Each widget is a unique variation of Latest Activity:
https://wp-singlesite.local-dev.codejp3.com/test-subforum/

BTW, cool site! If I still had a workshop and more free time I’d probably be a regular active member ??

WP does things with formatting text here. CODE blocks preserve the right formatting. This is what you should be putting in your child theme functions.php file, or the Code Snippets plugin (run on frontend only):

add_filter( 'bbp_after_get_the_content_parse_args', 'rew_enable_visual_editor', 50, 1 );

function rew_enable_visual_editor( $args ) {
		$args['teeny'] = false;
		return $args;
}

And if you allow guest posting and want to enable the advanced editor for guests as well, also add this:

add_filter( 'user_can_richedit', '__return_true' );

For more control over what buttons are displayed in the advanced rich editor, check out the Advanced Editor Tools plugin.

The default for Style Pack is empty (no custom directory), and Style Pack makes no changes to custom values set there. Perhaps another admin set it at some point.

This will be patched in an upcoming release of Style Pack. I’m going to go ahead and mark as resolved.

Also, it appears as though you’re embedding the forum through an Elementor shortcode instead of the default bbPress functionality. That could also be the cause.

Can you go to Style Pack > Plugin Information (wp-admin/options-general.php?page=bbp-style-pack&tab=plugin_info) and scroll down towards the bottom and copy/paste the settings you have for Breadcrumbs
bsp_breadcrumb.

It looks like you’re using The7 theme:
https://themeforest.net/item/the7-responsive-multipurpose-wordpress-theme/5556590?ref=mbalkhi

Perhaps there’s a conflict with that theme. Breadcrumbs should be shown by default. Let’s see what settings you have set for Style Pack first.

I was able to replicate this on my test server. A fix will be released in the near future.

In the meantime, an immediate workaround is to not use a custom CSS location in the CSS Location tab (wp-admin/options-general.php?page=bbp-style-pack&tab=css_location).

Sorry for the inconvenience. We will have this fixed soon.

I will look into this

Question – do you currently have the stylesheet directory (Style Pack > CSS Location) set to /wp-content/uploads/ ?

If so, is this admin CSS file the only one giving 404 errors?

@ahillmortons –
I have a version ready for you to test.

The query for Latest Activity has to be run in order to get the info in the first place. There’s really no good way around that.

With that said:
1.) the query that gets run has been optimized and minimized any way possible
2.) it no longer runs every page load for every user
3.) it only runs when there’s a new topic/reply added to the site, and only the widgets affected by the new topic or reply are re-queried
4.) it now loads from fast/small site transients by default every page load
5.) obsolete transients (widgets no longer used) are automatically removed from the DB after 1 month of not being used
6.) the code-base related to the widget and the query have been slimmed down and optimized

I setup over 100 various combinations of widgets to test it out on my dev site. Here’s a sample of what the transients look like in wp_options:

While there are a lot of changes, they all take place in 2 files.

You can use FTP or the File Manager Advanced plugin to update the following 2 files:

1.) /wp-content/plugins/bbp-style-pack/blocks/bsp-latest-activity-widget.php

2.) /wp-content/plugins/bbp-style-pack/includes/widgets.php

https://codejp3.com/wp-content/uploads/la_widget/bsp_la_widget_update.zip

If this takes care of the underlying issue like I expect it to, it will be included in the next release of Style Pack.

Awaiting your feedback.

• This reply was modified 1 year, 5 months ago by codejp3. Reason: updated download link

@robin-w – If you’re not actively working this, I believe I have a suitable fix for this. It involves:

1.) Saving the query results for Latest Activity Widget as site transients, and separate transients per activity type (freshness, newness, popular). Then every page load, the quick/light data from the transient is used instead of performing the query every page load.
2.) Adding a few other query parameters to prevent WP from doing a few extra and unnecessary sub-queries when the query is actually run.
3.) Minor tweaks to how the query values are built in the first place for code execution speedup.
4.) Only returning the ‘ids’ field to slim down the query results data since all other displayed values are derived from the ID in the first place.

It’s not quite that straight-forward, but that’s the gist of it.

I’m working on these revision right now. I should have something to test later today or tomorrow. @ahillmortons – are you able to replace a single file or two in the bbp_style_pack plugin directory (the File Manager Advanced plugin may be of use)? If so, are you willing to test out these revisions prior to us releasing an official update to address this?

I haven’t forgotten about you. I’m right in the middle of a move and have very limited time, plus my dev server is not fully up and running again yet.

I’ve played around with moderation a little earlier today and can see that it’s not behaving as intuitively as it could/should. Ideally there should be a single interface for reported topics/replies, regardless of the report reason/status.

Like I said previously, I’ve had plans to overhaul the whole moderated posts interface, which would take care of this. I just haven’t found the time to do so yet.

I’ll see if there are any minor tweaks that can be done for now until I find time to overhaul the interface like I want to do.

Yeah, WPMU isn’t to blame. That notice could absolutely be helpful with diagnosing bad site performance or misbehaving plugins.

Style Pack clears cache intentionally, every time you change settings that affect the site front-end visually.

Once you have Style Pack setup according to your preferences and no longer changing settings, it will NOT clear cache.

If you look at the support topics in Style Pack for 2022 and before, you’ll find tons of “it’s not working” topics with the magic solution was to clear browser cache and/or site cache. Since implementing auto cache clearing, I don’t think there’s been a single cache-related “it’s not working” topic.