IQComputing

@dpkonofa Thank you again for both your patience and debugging regarding this matter.

We have found that this is a legitimate issue with individual packages not returning shipping requests back to the shipping method and have pushed v1.0.1 early to resolve this issue.

Could you please update to the latest version of this plugin and let us know if you continue to run into issues?

Hello,

Thank you for giving our plugin a try! We apologize that you’re running into issues with it and will do our best to assist.

The (manual) flag should denote Shipping Carriers that were manually connected to ShipStation, which are not the ShipStation core carriers. That being said, we have found some issues with the returned API flags that could mark core ShipStation Carriers as (manual) in some cases, which will be patched in version 1.0.1 scheduled for next week.

One of the features on our roadmap is a better log/error system outside just the WooCommerce logs. In the meantime, you can enable WooCommerce debug logs by following the below instructions:

1. Log in your WordPress Admin Panel.
2. Using the left-hand navigation, navigate to WooCommerce > Settings > Integration > ShipStation
3. Toward the bottom of the settings page is a checkbox labeled “Enable Logging”, please check this checkbox and save the settings on this page.

This will log API requests and errors. These logs can get quite lengthy, we do not recommend leaving them on for extended periods of time and to clear them out whenever you’re done. You can review these logs by visiting the following page:

1. Through the WordPress Admin Panel, navigate to WooCommerce > Status > Logs

Here you should see a list of WooCommerce logs. The specific logs you want to look for are going to be labeled live-rates-for-shipstation – Within these logs you should see a number of Info tags with an Additional Context accordion that you can click to see the JSON behind the request / data.

Could you please enable logging as described above, go through the cart/checkout process, and then check those logs for any Debug flags? Otherwise, if you expand the Info tags, does it show any errors / error messages?

Hello,

We were able to test this with a Magnific Popup implementation which worked as expected – but the popup is inline content, not dymaically loaded via ajax.

The google-recaptcha script is enqueued whenever Contact Form 7 calls the tag handler. If you don’t see this in the footer of your website you will need to manually enqueue it using the code from our previous reply – it is a key ingredient.

Next, if you can find a JavaScript event that corresponds with your popup opening, you can call the recaptcha render method and pass in the params associated with the recaptcha container. All the reCaptcha settings are held as data attributes to the container. This means they will be available in JavaScript to use during the render method as seen in the example below:

document.addEventListener( 'yourPopupOpenEvent', ( e ) => {
	
	/* This querySelector may need to be specific to your popup ID or class */
	let reCaptchaAll = document.querySelectorAll( '.wpcf7-recaptcha' );
	if( reCaptchaAll.length ) {
		
		let reCaptcha = reCaptchaAll[0];
		grecaptcha.render( reCaptcha, {
			'sitekey': reCaptcha.getAttribute( 'data-sitekey' ),
			'type': reCaptcha.getAttribute( 'data-type' ),
			'size': reCaptcha.getAttribute( 'data-size' ),
			'theme': reCaptcha.getAttribute( 'data-theme' ),
			'align': reCaptcha.getAttribute( 'data-align' ),
			'badge': reCaptcha.getAttribute( 'data-badge' ),
			'tabindex': reCaptcha.getAttribute( 'data-tabindex' )
		} );
		
	}
} );

Hopefully you’re able to get this solution working for your usecase. Have a wonderful rest of your week!

Hello,

It appears there was a misunderstanding. The original description appeared to be regarding a 3rd party plugin and did not appear to have to do with Contact Form 7.

Without seeing the page in question, or knowing the plugin which drives the popup, it’s difficult to address this kind of question. This plugin uses the recommend wp_enqueue_script which may load scripts into the header or footer depending. This means that if the popup is loading the content dynamically, via AJAX, that the ReCaptcha Script will not trigger.

If the popup is loading inline, you can check the source to see if the google-recaptcha has been added. If you don’t see that in the source then it may indicate that the popup is incompatible with this plugin. If you’re familiar with PHP you may be able to use the following code to enqueue the script globally (or conditionally). We strongly recommend not doing the following if you’re unfamiliar with WordPress development.

/**
 * Enqueue ReCaptcha Globally
 */
function wpcf7_enqueue_recaptcha1748634272() {
	wp_enqueue_script( 'google-recaptcha' );
}
add_action( 'wp_enqueue_scripts', 'wpcf7_enqueue_recaptcha1748634272', 55 );

The priority of 55 is important since this plugin does it’s enqueue at priority 50. Hopefully you’re able to resolve this issue with your popup but if there’s anything else we can help with please reply back to this thread with more information.

@cmd4400 In our settings via Contact > reCaptcha version you’re able to select the Default (v3) or v2, but again I don’t think you can run both at the same time.

One mistake I see many websites make is that they’ll have a Contact Form, but then also in the body of their content, header, or footer they will display their contact email address. Spam bots will usually scrape website content and parse out the email addresses to spam.

It’s also worth noting that because of how ReCaptcha v3 works it does need to be functioning on the website for a certain amount of time before it can “hone in” on spam/bot like behavior.

Finally, you could also give hCaptcha a try as an alternative to Google ReCaptcha.

Hopefully, you’re able to find a solution to your spam issues, best of luck!

Hello @joaopcos

Whenever you edit a Contact Form, there’s a Messages tab. Toward the bottom of this list should be a couple “reCaptcha” inputs to change the error messages. If you’re developer-savvy, you could use the wpcf7_messages hook to update these messages throughout.

You can view the codebase to see how we implement these messages via the same filter hook. These are the messages Contact Form 7 uses in the validation $_POST callback.

Hopefully, using the above you’re able to resolve your issue. If not, please reply back and we can investigate this issue further.

Hello,

Looking at your posted URL and the Browser JavaScript Console, it looks like the API keys may be incorrect. Please review the Installation Guide and verify that your website domain is listed under the API key, that the Site Key and Secret Key are correct, and that you’ve set the ReCpatcha to be v2 under Contact > ReCaptcha Version. If you’ve verified all these settings and are still running into issues, try to change the ReCaptcha Source from google to recaptcha.net. This can be done under Contact > ReCaptcha Version.

Hopefully with the above instructions you’re able to resolve your issue. Otherwise, you may reply back to this thread and we can assist further. Have a wonderful rest of your week!