aph5

I’m not sure what changed (plugin or otherwise) – but this issue appears to be resolved at my end.

So good to have it working again – thanks all who were involved in the fix ????

@azaozz – thanks for the great plugin! ??

Am getting the same issue in Firefox. I see issue #52046 looks like a potential fix, but hasn’t been merged into an update yet?

That’s great news about the CSS and fontsawesome files being smaller.

Thanks for the reply and the good news ?? Your hard work is appreciated.

If you check my comment history, it shows the 3 or so prior posts I’ve written on your support page have contained the phrase “thanks”.

I don’t think there’s any need to be snarky about not saying it a fourth time. However, for clarity, I will say thanks once again for the plugin. Thank you.

With regards to v7 bringing complexities/problems, I will elucidate further:

– New features were turned on by default, meaning that it couldn’t be updated easily. Essentially you had to install it in staging, figure out how to get it back to a state that you enjoyed previously. Then deploy it live and make those adjustments.

– The CSS files now add extra size to the plugin – last time I checked it was around 200KB.

– Whilst you may not consider the exposure of a private wp-admin login page as “critical” – for me this is nevertheless a security hole that I don’t want exposed.

Just wanted to add that this is a concern from my end also.

Version 7 of wpDiscuz brought with it a number of complexities/problems, and I was willing to overlook those.

However, creating a security hole, declaring it would be patched “tomorrow” – and then almost 2 weeks later, still no update, is worrying from my perspective as a user.

Trust is important for users. I want a better WordPress comments experience on all my sites. I’m happy to pay money for it. However, if I can’t trust the plugin to be secure and not break stuff, that’s a deal breaker.

I would request that in future, security updates are prioritized and pushed live ASAP. Rather than bundled in with non-security updates, which delays the release.

For now I’ve had to stop running wpDiscuz.

Hi Jeroen, thanks for the reply!

That helped me get to the answer. After deleting, that section you refer to was showing blank (nothing), in place of where a name was before.

So need to got to “Search Appearance”, and scroll down to Personal Info > Name – and then select a new person.

After that, all worked!

Thanks for the technical suggestions MegaZ. Big fan of the wpDiscuz plugin, and speeding it up would be great.

I know the plugin needs shrinking on the front end, but wasn’t sure the best method.

+1 to MegaZ’s suggestions:

– Separate CSS files based on the options chosen
– Swap FontAwesome for inline SVG
– Split functions into separate files and load based on usage

Thanks for the comprehensive list of possible options.

Will explore those! Thank you.

Thanks for the reply Scott!

As LogoLogics suggested above, it should be possible to use CSS rules to stop it displaying.

The code they linked above would work, except perhaps a theme update has changed the div ID targeted.

At the time of writing, the current div ID is

#site-header-cart{

display:none

}

This can be added to the ‘Additional CSS’ under ‘Customize’ for the theme.

You may also want to remove the bar on mobile that displays the cart. Some info for doing that is here:
https://docs.woocommerce.com/document/customize-the-links-in-the-handheld-footer-bar/

When making those changes, its suggested to use this theme customisation plugin. Such that if woocommerce updates, you don’t lose the code you added.