Rick Hellewell

Actually – it was a “PBDAC” (Problem Between Desk And Chair). The results box is a scrolling box (which wasn’t obvious when I first looked at it). Scrolling down shows more results, and the ‘more results’ button works to get more results into the scroll box.

Thanks. I suspected that was the answer, but hadn’t dug deeply into the code. It appears that the issue is somewhere else.

Closed.

This particular plugin is built to block automated comment spam – any comment entered via the WP post/page comment form.

But I have other things that will block contact page form. Take a look at my FormSpammerTrap solution. It’s built as a standalone, but can be integrated with WordPress by creating a new template from your current theme’s page.php file. Full instructions on how to do that in the free code.

It’s all available at https://www.FormSpammerTrap.com . The process has been around for about 10 years, with improvements added all the time. Quite versatile, and quite effective. In all the years that I’ve had the FormSpammerTrap running on sites, I have never gotten any spambot contact form submissions.

And it is free. You can get it via the Contact form on the site (which is all done with the program, including automated sending of the files, the response, saving data, and more.)

Thanks for the kind comments – and the 5-star rating ! Huzzah !!

Glad that the plugin was able to block your comment spam problem. It’s all done by bots, who don’t even have to view your site.

Note that I have a couple of other plugins that might be helpful. Links are on this plugin’s settings page.

Thanks for the kind words – and the report of how effective it is.

I’d noticed the same thing on the sites I managed – especially the one that has many comments. Immediate positive effect. The nice thing is that the spam comments never ‘hit’ the database, like other solutions (like “Akismet”). They are just blocked.

Thanks again!

There’s a whole bunch of code involved; some CKEditor5 JS code, and other stuff. The basics for creating an ‘edit box’ is here https://ckeditor.com/docs/ckeditor5/latest/builds/guides/predefined-builds/quick-start.html#classic-editor .

You have to register and enqueue the JS codes using the usual WP commands. Then use a script in the area that the comment box is displayed to change the $comment_field in the Comment object. That is enabled with the appropriate filter to change the arguments for the Comment object.

The comment.php file is used to display the existing comments, and the comment box. That’s what should be used to display this plugin’s comment edit box.

Maybe add some code to the ‘edit’ button to disable the right-click/open in new tab. Probably some JS code to change the DOM element of the button.

Maybe something like this (not tested, and I’m not a DOM guru):

link.addEventListener("contextmenu", (event) => {
    event.preventDefault();

Perhaps there should be some way to intercept that ‘open in new tab’ function that is done by a clueless user. Who has complained about the effect. Don’t know if there is a way to determine that a new window was opened. But got a complaint from a regular commenter today about the issue.

I changed Settings to enable ‘live’ view. The PayPal button does not display. And it’s not a theme or conflicting plugin.

Inspecting the code for the popup box shows that the code that displays the button has CSS ‘display’ set to ‘none’.

.wp-ppec-overlay {
z-index: 10000;
display: none;
background-color: #fff;
width: 100%;
opacity: .7;
height: 100%;
position: absolute;
top: 0;
left: 0;
text-align: center;
-webkit-box-pack: center;
-ms-flex-pack: center;
justify-content: center;
-webkit-box-align: center;
-ms-flex-align: center;
align-items: center;
}

That CSS, if display:none is disabled, shows the spinner. This code line is what enables the name/etc field: (the ‘billing contianer’)

<div id="wpec_billing_paypal_button_2" class="wpec_billing_container" style="display: none;">

If I force that display:none disabled, I see the form, but not the PayPal ‘buy’ button . That button is disabled (source code shows this):

<div id="place-order-paypal_button_2" style="display:none;">

If I disable “display:none” there, the button will appear.

So there seems to be something in your code – or improper JS processing – that is disabling the display of the form data and the associated buy button.

The result is that clicking the ‘buy’ button displays the popup box, but there is no way to complete the order process via the popup.

If I disable the ‘popup’ setting, there is not a ‘buy’ button shown on the product page.

Do you see the ‘buy’ button on the text page in the popup that is shown when clicking on the ‘buy’ button?

Standard shortcode, created it via the Add New Product page. [wp_express_checkout product_id=”1640″]

Test page is here: https://www.richardhellewell.com/ppec-products/the-rv-park-redemption/

Noticed error in the console:

the-rv-park-redemption:1199:1

Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://www.sandbox.paypal.com/xoplatform/logger/api/logger?disableSetCookie=true. (Reason: CORS request did not succeed). Status code: (null).

Settings currently set for sandbox. PayPal credentials are valid and correct. Browser is Firefox (latest version). WordPress 6.31, PHP 8.x.

Thanks again. Version 3.02 with this minor fix is now available.

That particular issue resolved.

Urk. Fixed in version 3.01. Thanks for the catch!

I have just uploaded/released version 3.00, which fixes a lot of things (see the readme file), including the warning error messages because of using PHP version 8.x.

This update also resolves your issues. Thanks for your patience.

@robghen – do you want to beta test the updated version? The updated version seems to be working OK on my test site, but testing elsewhere is always a good idea.

If so, contact me via the contact form at my cellarweb (dot) com site. Let me know either way.