Nick

Like the others, im stuck in an update loop. Ive updated numerous times and it keeps telling me there’s an update available

Hi @elliotvs, sorry to tag you directly but I’m hoping you can provide some guidance on this. I’d be happy to do all the code implementation if it is possible. Thanks!

sorry, we don’t have experience with avada so don’t have much to recommend.

Try using the Health Check and troubleshooter plugin to temporarily disable plugins til you find which is causing the conflict.

Also turn on the debug log and check for any errors.

Beyond that you’d need to do real debugging, inspecting the code during a page load. Xdebug is the tool for that job.

good luck!

• This reply was modified 1 year, 2 months ago by Nick.

Good idea on the rename.

I actually use Buddyboss, as well as strongly recommend it to anyone, in comparison to buddypress/bbpress. My involvement here came when I wanted to make sure the plugin was compatible with Buddyboss – a few minor tweaks were necessary.

To confirm, the issue you reported here has gone away when switching to buddyboss? If so, please close the ticket – someone can open a new one if the find the same problem.

Can you provide a link to the site, or at least screen recording that demonstrates it?

sorry for the late reply. No, this isn’t possible with this plugin but you could surely add it with custom code

Ah, whatever. Easier to just replace that line with the following than to create a repo and then you merge all the changes.

$blocked_plugins = @join('###',isset($_POST['block_plugin_updates']) ? $_POST['block_plugin_updates'] : array());

The issue is when you submit with all boxes unchecked – it doesn’t pass an array, which means that the join() has nothing to join. So, this change just checks if it is set, and if not, it joins an empty array.

But, it would be cleaner if you just got rid of all of the ###, join, explode etc… and simply stored the array in the options table. It would look like this, which is standard practice (you’ll see that wp_options is full of such serialized arrays)

a:2:{i:0;s:66:"block-specific-plugin-updates-bk/block-specific-plugin-updates.php";i:1;s:23:"gutenberg/gutenberg.php";}

• This reply was modified 1 year, 8 months ago by Nick.

Upon digging deeper, that’s not it at all. The problem occurred when I was going from >0 to 0 blocked plugins.

Anyway, I’ve made some changes to the code – I don’t see any need to use the join(), explode(), and “###” at all. You can just store the $_POST[‘block_plugin_updates’] array in the option to begin with.

I’ll share a link to a modified repo when I’m done tidying up

To clarify, what you would like is when a new post is created, if that post has any postmeta custom fields, those custom fields will be duplicated for the forum topic that is created for the comments?

Im not sure what you’re asking for.

Do you want help with your custom code or are you requesting a change to this plugin’s code?

Either way, im not really sure what the problem is/what you’re trying to achieve.

Friend, you’re in the wrong place. This is the support forum for the “Post Comments as bbPress Topics” plugin.

The second screenshot suggests the error is coming from a “Reviewx” plugin. I suggest you look/ask there. It has nothing to do with our plugin.

This is still not something we can help you with as we dont have any info related to this plugin.

But since you suspect it is a hosting issue, I suggest you move to vps hosting. It will be far cheaper, more powerful and more flexible than shared or managed hosting.

Take a look at Runcloud with Vultr HF servers. Or gridpane’s free plan with vultr.

Thanks for the clarity, that’s very helpful.

No, there isn’t any such option right now. I’ll try to look at the code in the next few days and see if it is something that can be easily added.

In the meantime, please try out one of the older versions. All that the newer ones added was various “escaping” mechanisms that removes any html tags from text that is presented on the front-end. This has caused a major nuisance for some users because they were displaying formatted text in a few places. We plan to try to figure out a way around this that satisfies the plugin moderators concerns – it only serves to prevent site admins from displaying text/html that only they can create. You can check out some recent support tickets to see what I’m talking about

• This reply was modified 2 years, 1 month ago by Nick.

The “security” updates are not meaningful. You’ll be perfectly fine at least trying out the older version to see if it fixes or narrows down the problem. That would be my first recommendation for you.

If that doesn’t work, then I hate to seem rude/unhelpful, but could you please rewrite the rest of your message more concisely? It was a headache to try to make sense of it.