Title: Renamed Fields & Required fields issue Last modified: August 21, 2016 --- # Renamed Fields & Required fields issue * Resolved [agusbagus](https://wordpress.org/support/users/agusbagus/) * (@agusbagus) * [12 years, 5 months ago](https://wordpress.org/support/topic/renamed-fields-required-fields-issue/) * Hello again Uli, * Sorry I just realized that in my account – edit address. 1. Renamed fields still show as default (unrenamed) fields. 2. Required fields still default woocommerce so the fields that we hide and marked as optional in setting still required in my account – edit address. I believe you can fix it easily 🙂 Thanks for your support. * Best Regards, Agus * [http://wordpress.org/plugins/woocommerce-poor-guys-swiss-knife/](http://wordpress.org/plugins/woocommerce-poor-guys-swiss-knife/) Viewing 9 replies - 1 through 9 (of 9 total) * Plugin Author [ulihake](https://wordpress.org/support/users/ulih/) * (@ulih) * [12 years, 5 months ago](https://wordpress.org/support/topic/renamed-fields-required-fields-issue/#post-4478345) * Hello agusbagus. * You refer to labels and placeholders, I guess. * Yeah, I can fix this easily. In fact, the plugin is anounced to do the stuff for the checkout forms… WooCommerce is a huge package… * It could be that you have to wait till next week for the update. I will try to have it available on Thursday, but I cannot guarentee this. Hope this is ok for you. * ulih * Thread Starter [agusbagus](https://wordpress.org/support/users/agusbagus/) * (@agusbagus) * [12 years, 5 months ago](https://wordpress.org/support/topic/renamed-fields-required-fields-issue/#post-4478348) * Hi Uli, I am talking about the labels & required fields (not place holder). Placeholder also has a bug. But that’s still acceptable because I don’t want to bug you too much since this is only a free plugin 🙂 I am waiting for your further enhancement. Appreciate your assistance. 🙂 Thanks. * Plugin Author [ulihake](https://wordpress.org/support/users/ulih/) * (@ulih) * [12 years, 5 months ago](https://wordpress.org/support/topic/renamed-fields-required-fields-issue/#post-4478356) * Your help and information is appreciated. When you first stated that logged-in customers see the unaltered core fields, I wasn’t aware of this problem, because I never had tested this feature of WooCommerce. In the implementation process for one of my clients there was no need for this and as the plugin derives from this work… * What I did to “please” you with the 1.5.1 update was to put a “convenience” solution for the urgent problem you communicated. This solution still needs a revision as it only addresses the problem of core fields marked with “remove”, but as stated, I will try to have the full revision out on Thursday for this, if not on Tuesday night. * uli * Plugin Author [ulihake](https://wordpress.org/support/users/ulih/) * (@ulih) * [12 years, 5 months ago](https://wordpress.org/support/topic/renamed-fields-required-fields-issue/#post-4478364) * I close this for now, as this does not affect anounced core features nor the checkout forms itself. This problem only affects returning customers which edit their billing and shipping address after logging in. I will keep you informed and place a notice here when the update is available. ulih * Plugin Author [ulihake](https://wordpress.org/support/users/ulih/) * (@ulih) * [12 years, 5 months ago](https://wordpress.org/support/topic/renamed-fields-required-fields-issue/#post-4478508) * Hello agusbagus. * With version 1.5.2 most of the issues with “Edit my address” for logged-in customers should disappear. The “Edit my address” forms include now better support for the custom fields like on the checkout page itself, they respect the established order, show labels and placeholders correctly, etc. * Things that don’t work on the “Edit my address”: * * Repeater fields * left and right orientation of fields as the form expects all fields to be wide fields and WooCommerce Poor Guys Swiss Knife assigns for this reason the wide row class automatically to all fields * Everything else should work like on the checkout forms. * uli * Thread Starter [agusbagus](https://wordpress.org/support/users/agusbagus/) * (@agusbagus) * [12 years, 5 months ago](https://wordpress.org/support/topic/renamed-fields-required-fields-issue/#post-4478524) * Hi Uli, I’ve checked it works amazingly 🙂 Thanks for your hard work, I deeply appreciate it. Wide row class for all makes the appearance even better. However the required fields still have problem. Default required fields for woocommerce include post code and last name. I disabled them and hide them using poor-guys- swiss-knife plugin. When customer edits the address from my account – edit address, it can’t be saved and shows the error: those fields are required. it’s possible to fix it? again thanks and sorry for the inconvenience. * Plugin Author [ulihake](https://wordpress.org/support/users/ulih/) * (@ulih) * [12 years, 4 months ago](https://wordpress.org/support/topic/renamed-fields-required-fields-issue/#post-4478530) * 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 * Plugin Author [ulihake](https://wordpress.org/support/users/ulih/) * (@ulih) * [12 years, 4 months ago](https://wordpress.org/support/topic/renamed-fields-required-fields-issue/#post-4478542) * 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 * Thread Starter [agusbagus](https://wordpress.org/support/users/agusbagus/) * (@agusbagus) * [12 years, 4 months ago](https://wordpress.org/support/topic/renamed-fields-required-fields-issue/#post-4478545) * Awesome, have tested and it’s working flawlessly now. I don’t see anymore any issue right now and don’t expect to see more, as I want to put the store online ASAP 🙂 Thanks for your amazing work. If you need a tester I will always welcome to help you. Viewing 9 replies - 1 through 9 (of 9 total) The topic ‘Renamed Fields & Required fields issue’ is closed to new replies. * ![](https://s.w.org/plugins/geopattern-icon/woocommerce-poor-guys-swiss-knife_ffffff. svg) * [WooCommerce Poor Guys Swiss Knife](https://wordpress.org/plugins/woocommerce-poor-guys-swiss-knife/) * [Frequently Asked Questions](https://wordpress.org/plugins/woocommerce-poor-guys-swiss-knife/#faq) * [Support Threads](https://wordpress.org/support/plugin/woocommerce-poor-guys-swiss-knife/) * [Active Topics](https://wordpress.org/support/plugin/woocommerce-poor-guys-swiss-knife/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/woocommerce-poor-guys-swiss-knife/unresolved/) * [Reviews](https://wordpress.org/support/plugin/woocommerce-poor-guys-swiss-knife/reviews/) * 9 replies * 2 participants * Last reply from: [agusbagus](https://wordpress.org/support/users/agusbagus/) * Last activity: [12 years, 4 months ago](https://wordpress.org/support/topic/renamed-fields-required-fields-issue/#post-4478545) * Status: resolved