ulihake

Hello minnoit.

I’m not able to reproduce this. Labels and placeholders work fine. Could you please tell me if you used the settings page for the billing and shipping section of WooCommerce Poor Guys Swiss Knife? Did you save any settings there?

Thanks for your feedback
uh

Ok. Checked on this and you’re right. Internal WooCommerce Fields which are not required by default, did not allow the activation of the required status.

This is fixed in version 1.6.1.

If you appreciate the work I would be glad to receive a review.

Thanks.
uh

Hello Twanneman.

Thanks for your feedback. I will check this.

uh

Hello WordniQ.
Thanks for your feedback and no problem, and my question wasn’t rhetoric at all. If you have an interesting website for a link to offer for example or if you can provide a translation to another language… we can establish some other way of “payment”.

Thanks and regards.
ulih

That’s possible with the Rich Guys Swiss Knife. I put a lot of stuff into the Poor Guys Swiss Knife.

If you want to implement item personalization for products and product variations or dispose of an additional section for all products with own header title you will have to use the Rich Guys Swiss Knife. I understand that everybody wants to have everything for free… but I have to finance support and development, at least I need some kind of compensation. What do offer if you don’t want to pay for the Rich Guys Swiss Knife?

Regards.
uh

Thanks a lot. I appreciate if you express this with a rating.

ulih

I will close this for now. If you experience problems just leave a reply and I will step into it again.

Hello ocean.

1.5.4 should fix this warning.

Regards.
ulih

OK, I’ve seen that this happens on another page as well. I will offer a solution tomorrow.

ulih

Hello ocean…

Ok, I see the message. If you’d like, we can get in contact over https://takebarcelona.com

On the bottom of the page you’ll find a chat and I can try to facilitate a version which you may test. The problem seems to be caused by your php version and php configuration. The warning message itself does not prevent your store from running nor does it prevent that you can add products to the cart.

If you disable debug mode the warning messages should not display anymore nor does the underlying context really affect your store as the affected function is not vital for the store operations at the moment.

Regards.
ulih

I cannot reproduce this behaviour without a bit more of information. Could you please post the website?

Thx.
ulih

I hope everything works now. I did some more testing on the 1.5.3 update. Nevertheless: Feedback is appreciated just to be sure that the substantial changes do not mess up things in other “realms” of WooCommerce… and testing consumes a lot of time…

Thanks for your rating.

Thanks for your rating.

If you feel like doing the dutch language file, welcome… I offer a one year license for the WooCommerce Rich Guys Swiss Knife as a little gift for the effort.

ulih

Ok, 1.5.3 is out. Hopefully this addresses all of the “backstage” (admin or logged-in customers) issues. If you find more problems, tell me as I will try to fix all issues this week to set the project “aside” for awhile afterwards.

ulih

Hello agusbagus.

Ok. I did some additional testing and you’re right. I checked on my installation with an existing customer and with this customer things worked like expected, for new customers or customers without data for the removed fields, the required validation still fired. This is fixed in 1.5.3 which I will publish this afternoon.

For the zip/postcode field we have a special situation as the zip/postcode may provoke WooCommerce to raise an error if you use the Country selection. For US/UK/CH WooCommerce runs an additional validation on the zip/postcode field. I could fake valid values for the postcode field but I’m not sure if I should implement this.

Thanks for your good feedbacks.

ulih