david

Update – looks like the maps are fixed now but I haven’t seen any official word so leaving this open for now.

Hi, thanks for responding. After I submitted this comment I found the bulk image optimization tool. I initiated it and it’s still in progress. It appears to be reducing image sizes successfully. I don’t want to stop it though, but when it’s done do you still want the debugging report or now that I kind of manually started it, do you think I’m good to go? Thanks.

I just updated to the new version and my settings too were changed. For example, I had hide backend turned on with a different login URL. I went to the login URL and was getting a 404 page not found. I went to the iThemes plugin and found that my hide backend featured was turned off (disabled)! To my surprise, now I’m going through all my custom settings. But this is very worrying that the update would change all settings like this totally screwing up the site.

Contacting Namecheap to disable mod_security worked for me too when I had this issue. Would be nice if Disqus had an FAQ or something on this instead of everyone having to search for answers.

bump, just seeing if this can be done?

@retrosmack, sure, it’s just a three step process. Not sure if it will work for you like it did for me but, worth a try.

1) Deactivate the plugin from your plugins Dashboard. Reactivate it, but don’t click on the “install latest settings” link on the top.

2) Then go to the Checkout Manager plugin Settings page and click on the Billing tab and mark all the address fields as not required. Save your changes.

3) Go to wherever you put your custom CSS for your site and paste this code in there, probably toward the top somewhere.

#billing_country_field, #billing_first_name_field, #billing_last_name_field, #billing_company_field, #billing_address_1_field, #billing_address_2_field, #billing_city_field, #billing_state_field, #billing_postcode_field, #billing_phone_field {display:none !important;}

That’s it. Go back to your Checkout page on your site as if you’re a regular user and see if the changes worked.

I was able to resolve this issue by deactivating the plugin, reactivating it, and going back to the Settings>>Billing section and the extra billing fields showed up. I wasn’t able to remove them, I was able to mark them as NOT required though.

I then added this code to my CSS file to hide the address fields which are now not required.

#billing_country_field, #billing_first_name_field, #billing_last_name_field, #billing_company_field, #billing_address_1_field, #billing_address_2_field, #billing_city_field, #billing_state_field, #billing_postcode_field, #billing_phone_field {display:none !important;}

Note: After reactivating the plugin I get this message again at the top of the Settings page:

Almost done! Install latest settings. Click Here

I did NOT click and install the latest settings this time around. I’m not sure if that was part of the success of the overall solution, but I’m not going to click it as everything is working fine now (hidden address fields, not required).

I was able to resolve this issue by deactivating the plugin, reactivating it, and going back to the Settings>>Billing section and the extra billing fields showed up. I wasn’t able to remove them, I was able to mark them as NOT required though.

I then added this code to my CSS file to hide the address fields which are now not required.

#billing_country_field, #billing_first_name_field, #billing_last_name_field, #billing_company_field, #billing_address_1_field, #billing_address_2_field, #billing_city_field, #billing_state_field, #billing_postcode_field, #billing_phone_field {display:none !important;}

Note: After reactivating the plugin I get this message again at the top of the Settings page:

Almost done! Install latest settings. Click Here

I did NOT click and install the latest settings this time around. I’m not sure if that was part of the success of the overall solution, but I’m not going to click it as everything is working fine now (hidden address fields, not required).

I was able to resolve this issue by deactivating the plugin, reactivating it, and going back to the Settings>>Billing section and the extra billing fields showed up. I wasn’t able to remove them, I was able to mark them as NOT required though.

I then added this code to my CSS file to hide the address fields which are now not required.

#billing_country_field, #billing_first_name_field, #billing_last_name_field, #billing_company_field, #billing_address_1_field, #billing_address_2_field, #billing_city_field, #billing_state_field, #billing_postcode_field, #billing_phone_field {display:none !important;}

Note: After reactivating the plugin I get this message again at the top of the Settings page:

Almost done! Install latest settings. Click Here

I did NOT click and install the latest settings this time around. I’m not sure if that was part of the success of the overall solution, but I’m not going to click it as everything is working fine now (hidden address fields, not required).

Ugh, does anyone know how to remove the required address fields? That’s all I need. The new update really screwed up my settings and the new way to hide address settings does NOT work!

I’m getting the same thing. Why did address fields on the Checkout page all of a sudden become required? I never use them (I sell virtual products) and now all of a sudden on my Woo Checkout page all address fields are showing and are required and I can’t get rid of them!

I’m getting the same config errors as everyone else:

From [your-email] <[your-email]>
This email address does not belong to the same domain as the site.

This doesn’t make much sense to me since the FROM email address is the sender’s email, so it should not be my domain/my email address. Someone above suggested a no-reply email, but in theory it should be the sender’s email.

We’ll consider this but I am not sure if we can force users to use Recaptcha, because this wasn’t the case by now, and it would not be ok for a user that doesn’t want recaptcha to suddenly have it on the site, in the next update.

Hey there, no problem, glad I am able to help in some way. My recommendation would be to only require it for new users going forward, not for those who already downloaded it. If you can’t, then maybe some sort of warning/recommendation message saying to avoid spam you highly encourage users to turn on Recaptcha.

Hi Rodica, sorry for the delay. And for everyone else – after setting up Recaptcha and letting it run for a couple of days, the spam has completely stopped. This is good, so the Recaptcha is working and the forms continue to work. The downside is if you don’t setup Recaptcha, you’re basically going to get spammed to death.

I would suggest the plugin makers force users to setup Recaptcha by making it a requirement. Plugin users can opt-out of it if they want by turning it off, but I would recommend it’s on by default. There is too much risk with the spam that someone could phish their information or send malware links, etc. Thanks.

What version of IE is it? I’ll have to have a colleague text as I’m on mac.

I’m using IE-11