LiamMcArthur

I spoke too soon! If you check the website now we’re still getting 404’s. Is there anything obvious that would cause this?

I’ve changed the distribution method from “Apache mod_rewrite+mod_headers” to “PHP” and it appears to have resolved the issue!

But my plugin is using the wp_mail function. I’m not using a custom mail function.

• This reply was modified 7 years, 1 month ago by LiamMcArthur.

Yes! You’re absolutely right, it falls under “order” and setting the value to 2,000 made the additional content show. Many thanks for your help with this!

• This reply was modified 7 years, 2 months ago by LiamMcArthur. Reason: marking as resolved

I’ve just tried the following:

add_filter( 'woocommerce_checkout_fields' , 'custom_override_checkout_fields', 99 );

function custom_override_checkout_fields( $fields ) {
    var_dump($fields);
}

This dumps all billing and shipping data, but it doesn’t contain any fields within additional. Is it possible that add_filter( 'woocommerce_checkout_fields', 'name_here' ); is only able to retrieve WooCommerce core checkout data? The only way I’ve managed to get it working at the minute is to hack checkout-form-designer.php with the following:

if(!in_array($_SERVER['REMOTE_ADDR'], $allowed_ips)) {
    unset($fields['order']['sales_person']);
}

… but that’s the last thing I wanted to do!

That looks like a very suspicious file and it certainly isn’t part of the WordPress core. I’d get this file removed, make sure that all of your file permissions are correct (not 777 recursively, for example) and remove any potentially vulnerable plugins and code.

UPDATE: I replicated my entire website over to testing subdomain and the issue still remained. I disabled each plugin for my website one-by-one and eventually found the culprit – Wordfence. This is why I couldn’t replicate the issue locally (because I didn’t have Wordfence configured on my local machine).

I’m attempted to delete and reinstall but the problem still arises, so I’ve submitted a ticket to them:

https://www.ads-software.com/support/topic/dashboard-mixed-content-error/

Thanks for helping me look into this Otto. Next time I’ll remember to test each plugin first before submitting on here!

Kind Regards,

Liam

Correct, both the site address and WordPress address are pointing to the https version of the website – I’ve double checked this.

Sometimes it takes the developers some time to catch up and get a compatible release out. I’d say upgrading to 4.9 is safe for your plugins, as well as most minor releases – just be mindful if you’re ever upgrading to a major version (such as 5.0), as core functions may be deprecated and cause problems with your incompatible plugins.

It’s nowhere to be seen in the source either. In fact, the only occurrences of http at all are the WordPress xmlns attributes.

Was there a particular error message you were getting?

It turns out I didn’t get the plugin from the WordPress plugin libary. I got it from CodeCanyon (https://codecanyon.net/item/woocommerce-multistep-checkout-wizard/8125187/comments).

The problem is that the most recent update for the plugin creates a new Javascript file called thwcfd-checkout-field-editor-frontend.js. This file contains the following script:

jQuery(document).ready(function($) {
  $('select.thwcfd-enhanced-select').select2({
    minimumResultsForSearch: 10,
    allowClear : true,
    placeholder: $(this).data('placeholder')
  }).addClass('enhanced');
});

Simply commenting out this code fixed everything for me!

• This reply was modified 7 years, 6 months ago by LiamMcArthur.
• This reply was modified 7 years, 6 months ago by LiamMcArthur.

I’ve managed to narrow down the problem. It appears that the plugin isn’t compatible with WooCommerce MultiStep Checkout. I was going to provide you with a WordPress link to the plugin, but it looks like the developer has removed it.

I’ll try and work out what is causing the problem and see if I can make it compatible myself. Many thanks!

UPDATE: Functionality to add up to 5 phone number shortcodes has now been added.

Good morning. I certainly will be continuing to support this plugin for the foreseeable, as well as extending the functionality of it. I will update this ticket once the new functionality has been completed.

Kind Regards,

Liam