Bricks Version: 1.3.1 Browser: Chrome 90 OS: macOS / Windows / Linux / etc. URL: (a link to a page that illustrates the issue would be really helpful)
[Please describe in as much detail as possible how we can replicate this bug]
I have been testing Bricks and I couldnāt make any WP plugin work with Bricks. Thatās because Bricks comments widget is hijacking the WP native comments functionality, so no other WP comments plugins can be used.
Disqus would work because it doesnāt rely on the native WP comments, but I need to use plugins based on the native WP comments.
The problem with Bricks is that is forcing their own commentsā element by replacing the native WP comments. The result is that when you use one plugin that uses the existent WP comments code like (WP Discuz, Deeper Comments, Thrive Commentsā¦) Bricks comments element still comes on top anything that is āWP commentsā even if you use any of those others plugins as a āskinā.
The result is that no other WP Plugin for comments can be used. Itās an issue that is causing the design from Bricks by messing with the WP native code that generates that kind of incompatibilities with plugins.
No code should be forced in WP, but used for accomplish the objective. The bricks comments cannot do a 10% of what other specialized plugins can do. I hope you can fix this or maybe just create a regular WP comments widget that display the native WP comments so the rest of the plugins.
Well, Itās funny to me because, causing incompatibilities of plugins because of āunnaturalā modifications/workflows with the WP code is not what I would consider an idea, but a way of developing incompatibilities. This is a situation that needs a fix, but well, I add this incompatibility with any WP comment plugins to the ideas board if thatās the procedure. The comments you have created are more beautiful than the WP native ones yes, but you have to understand that they are pretty reduced in features compared with a specialized plugin (not even a 10% of what those plugins offer). Thatās why having the native comments from WP as an option is a must.
My 2 cents: Kindly note that Iām trying not to sound rude with this matter, but Why not to use the code that is already there? I would stop forcing the code that WP already has. If you just rely on it, you will avoid multiple issues. The rest of the plugins that everyone is using are relying on that code, so every modification means unnecessary incompatibilities.
You have a nice project here, donāt mess with the code that already exists in WP and WooCommerce, use it on your benefit.
I sort of agree with @jotace here. This shouldnāt be handled as a feature request/idea, but rather a bug/incompatibility and should be prioritized as such.
Iād been having the same issues with Discuz - Happily Iāve found a hack around:
I placed <?php comments_template() ?> is a code widget at the end of the page in the Bricks page builder and now the posts display the Discuz comment system.
(Update: Note, thereās a flaw in this approach, but it too can be hacked around - see below )
Iāve now discovered there is a fly in the ointment with my injecting-code-to-show-comment approach.
Bricks also still displays its own comments, lower down the page - so you end up with the comments being displayed twice on the page - not ideal.
As a short term hack (as I really need to have wpDiscuz comments displaying), in CSS, Iāve set the Bricks comments to display: none. This has the page-load speed downside of the postās comments being loaded twice to display, but at least theyāre not being shown twice now.
I must have thought myself into knots on this one. The fix of stopping the Bricks Comments showing was simple - Remove the Bricks Comments element that Iād already placed in the template! (I was sure Iād tried this obvious solutions before and it didnāt fix it, but there we are - works fine with no comment duplication).
Iāll amend my post above to reflect this to avoid confusion.
