codejp3

@fabienmahot777 – got a chance to look at it.

Both “subscribe” and “favorite” are not working.

If i right-click, “open in a new tab” they do work. But something is preventing them from reloading the page where they are displayed. It really does seem like a plugin or theme conflict.

I will try every plugin you listed to see if one of them breaks it on my test site, but my settings will not match yours so there’s no guarantee that I can replicate it.

I’m almost 100% sure it is a conflicting plugin or theme.

You can disable/delete that test user account before people start spamming your forum 😉

@fabienmahot777 – I was not able to replicate the subscription button issue. Using the following shortcodes, subscribe/unsubscribe was working fine:

[bbp-forum-index]
[bbp-single-forum id=##] (## was an actual forum ID)
[bbp-topic-index]
[bbp-single-topic id=##] (## was an actual topic ID)

I tested against default WP twenty-x themes and against the “Spice Software Dark” theme. Working fine in all cases.

One note is that with the shortcodes, the AJAX file is NOT loaded, so the page defaults to using the PHP functionality, which reloads the page to perform the actions. Not as elegant as no-page-reload AJAX, but it is functional.

It does not appear to be an issue with bbPress core. Working as expected.

Only things I can think of left to try to help you is:

1.) On the page where you’re having the issue, right-click and select “view source code”. Then within the source code hit “ctrl” and “f” keys at the same time to “find a string” and search for “engagements.js”.

If that file is not found, this simple code snippet could be added that would force-load it. It may fix your issue and should also enable AJAX functionality for subscriptions, favorites, and other bbPress actions when shortcodes are used:

/*
* Force-Load bbPress engagements.js script
*/
function force_load_engagements_script() {
    wp_enqueue_script( 'bbpress-engagements-js', WP_PLUGIN_URL . '/bbpress/templates/default/js/engagements.js', array( 'jquery' ), ( function_exists( 'bbp_get_version' ) ? bbp_get_version() : get_bloginfo( 'version' ) ), false );
}
add_action( 'wp_enqueue_scripts', 'force_load_engagements_script' );

^ That should be added to your theme functions file ONLY if you’ve setup a proper child theme for “Spice Software Dark” so that it doesn’t get lost if there are any future updates for that theme. You could also add that code snippet with one of my favorite code plugins Code Snippets. Or you could get slightly more involved and write your own plugin to hold all of your custom code snippets.

That code snippet above can be improved to target ONLY the bbPress pages you need engagements.js enqueued for, but you need to know those specific page slugs . You could wrap the wp_enqueue_script() with an additional check for those specific page slugs like this:

/*
* Force-Load bbPress engagements.js script on specific pages
*/
function force_load_engagements_script() {   
    if ( is_page( [ 'custom-forum-index-page', 'custom-topic-index-page' ] ) ) {
        wp_enqueue_script( ... ); // NOTE: '...' used to simplify example code and must be replaced with actual enqueue code!
    }
}
add_action( 'wp_enqueue_scripts', 'force_load_engagements_script' );

2.) If you send me the URL to the page where the problem exists, I can inspect it myself. You can post the link here or email it to me at [email protected]. I would need an account on your site so that the subscribe/unsubscribe button shows for me. It can be a regular user account without admin access. I would just inspect it, but not to do anything about it. Doing something about it would require admin access, and that’s not a good idea unless it’s a test/development site without anything important or any live users. Your site, your decision.

There’s something not right with your server/site environment that I can’t replicate on my test server. It will take some digging to find out the root issue.

@fabienmahot777 – I’ve been playing around with forum and topic subscriptions, and they are working fine in every scenario I’ve tried. But it did make me think of a few more possibilities/suggestions:

1.) Have you tried disabling Style Pack and confirming that Subscribe/Unsubscribe is working with bbPress itself? This plugin uses the default bbPress functions for forum/topic subscriptions. The only changes made are wording for “Subscribe/Unsubscribe”, and maybe adding a CSS class for styling reasons. It does not change any functionality. If it’s not working with bbPress, it won’t work with Style Pack. If it is working with bbPress, it should also work with Style Pack.

2.) Is your forum using any custom templates (specifically bbPress templates – wp-admin/options-general.php?page=bbpress > Forum Theme Packages)?

3.) Is your forum using any shortcode embeds to embed the forum within pages?

4.) Does your site theme offer any direct bbPress support/features/options?

5.) Is your forum doing/using anything “non-typical” or custom?

If so, let me know so I can test against those conditions to try to replicate the issue you have.

• This reply was modified 3 years, 3 months ago by codejp3. Reason: minor changes for readability

I don’t want to let it go “unresolved”, but nothing jumps out as “wrong” within the code, neither myself or @robin-w can replicate the issue, no one else is complaining about the issue, and even you say it’s fine with 2 local versions.

This may have just been a 1-time fluke. @robin-w just pushed another update – 5.3.8. Pay close attention when you upgrade to that (and all future upgrades) to see if it works properly or if this issue happens again to you.

If it does, before clicking “save” to force a regeneration, take a look at the “Plugin Information” tab (options-general.php?page=bbp-style-pack&tab=plugin-info) and copy the values it shows for “forums index styling
bsp_style_settings_f”.

That will help zero in on whether it’s an issue with the value being pulled from the DB before file generation, or an issue with the generated file.

Alright. Does sound like a generation issue, centered around font size for the forum index. Digging in now to see what I find.

@clivesmith –

You said the update “messed up your styling”. Correct me if I’m wrong, but that means all of your custom styling was not applied and the default bbPress styling was what you were seeing. Right? Or was it only fonts, like you specifically mentioned, and if so, are they custom/external font files?

The reason I’m asking is because the Cloudflare issues we’ve seen have to do with NEW settings not being applied and visible instantly when caching/CDNs are used. We modified the plugin so that everytime the files are regenerated, they get a new file version number. That SHOULD trigger all browsers and CDNs like Cloudflare to use the new file versions, and seems to have resolved that problem overall. This file versioning also happens every time the plugin is upgraded.

Several others use Cloudflare, but you’re the first to mention any new Cloudflare issues in the past 5 or 6 updates. Not convinced that it is a Cloudflare issue.

What you’re describing sounds like no files were generated, or something was not right with the files generated. Even if Cloudflare were using the old cached file versions instead of the new file versions, it shouldn’t have messed with any styling and should have showed the forum according to the OLD styling file. I wonder if something wasn’t generated correctly, Cloudflare cached that, and then it took another file regeneration or two for Cloudflare to recache new good/working style files.

Can you clear up whether ALL custom styling was lost, or just fonts, and if so, what kind of fonts and font sources you’re using?

If it was just fonts and you’re using non-standard fonts, that’s one thing to look into. If ALL custom styling was lost, that’s a whole new thing to look into.

And as @robin-w mentioned, if you do experience it again, jump on a device that has never been to your forum before and check it out there. That could help narrow down whether to include/exclude Cloudflare as a possible culprit.

• This reply was modified 3 years, 3 months ago by codejp3. Reason: Fixed some typos

@robin-w – makes perfect sense.

Perhaps checking for BOTH theme.json and /templates/index.html would narrow it down even more. By chance there may be traditional themes with one or the other, and checking for both would weed-out those false positives.