ulihake

Ich schliesse dies hier, da dies kein spezifisches Problem von WooCommerce Poor Guys Swiss Knife ist.

Wenn Sie weitere Probleme mit WPML haben, kontaktieren Sie gerne noch einmal. Allerdings sollten Sie zuerst versuchen, die Zeichenketten über WPML zu registrieren und diese dann auch übersetzen. Das Stichwort hierfür ist “Autoregister Strings”.

Hallo.

WPML sollte funktionieren. Meinerseits habe ich für Englisch und Spanisch gestestet, mit Englisch als Hauptsprache. WPML empfiehlt immer auf Englisch vorzugeben und über “String Translation” andere Sprachen wie Deutsch einzupflegen.

Notwendig ist es zudem immer, die übersetzung selbst über das WPML-Modul zu leisten. Hierfür kann es notwendig sein, dass die “Strings” (Zeichenketten) zuerst registriert werden müssen, was über die Verwaltung von WPML gesteuert wird.

Da dies kein Problem von WooCommerce Poor Guys Swiss Knife ist, schliesse ich dies hier.

Grüsse.
ulih

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

But: I have to admit that I do not know what the benefits of photon are, – if it works -, maybe it’s worth to have photon activated and to fix the problems which could be related to some special conditions on my server and maybe there’s no need for the photon files in the modules directory. If you indicate that the problem has to be on my side, I will try to find additional problems in my instance but before losing time I’m in need of a short reply from your side that your implementation is correct and operational.
Thanks.
ulih

Impact is that tiled galleries show messed up in size and layout, it’s not a tiled gallery anymore, it resembles what I would call a “messed up gallery”… It’s reproducable: if I comment out the two lines, everything works fine, if I uncomment the lines (original state) tiled gallery stops working as expected on all browsers and platforms.

Was there a reason to change this? In 2.5 photon class and functions are not loaded, in 2.7 you load them again. But moreover your photon plugin directory is empty in 2.7 whereas in 2.5 you find two files in the photon directory in modules.

I did not make any further analysis of the problem. I just wanted to know why my tiled galleries stopped working after the update from 2.5 to 2.7 and that’s what I’ve found.

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

For sure, some brain-storming related with Point 4 is highly appreciated… If I get you right, agusbagus, you want to take a customer directly to the payment gateway, bypassing the checkout form… Am I right?

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

Hello again.

Point 1.: is a major upgrade because I have to do a lot of testing for this and I will have to handle special and problematic cases because changing core field types is not just about assuming risks. A “good plugin” has to minimize the risks of breaking things and I don’t want to have one support ticket after the other ??

Point 2.: OK. I will try to have something operational at the end of next week…

Point 3. Totally up to you. I really tried to put some valid and useful stuff into the Poor Guys Swiss Knife and I’m glad if the plugin is of some help.

Point 4.: Like point 1., this is a major upgrade and this will have some limitations that may not suite your needs as every order needs to have billing information, that’s a WooCommerce prerequisite. There are ways to implement something like this, but one way or the other the customer has to be a “returning” customer, I believe.

ulih

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

Hello @hankey71.

You should have received an email with a .pot and a .po file.

Thanks.

ulih

Hello @daltx

Could you open a new thread for this elaborating on what you need? If you need a box that allows for more free text you can use a textarea. Right now a normal text field won’t expand automatically, whereas many browsers allow to expand textareas…

Regards.
ulih

Hello @Hankey.

Sorry for the late reply. Yeah, you can use poedit, perfect. The plugin includes a basic .pot file to generate a french file for the plugin. Let’s do it like this. You provide me with a french translation file for the Poor Guy and I will give you a license for the Rich Guy. If you deliver the french translation file for the Rich Guy I will change your license.

You can contact with me over the https://takebarcelona.com

uli

Hello agusbagus. Hello everybody.

Thanks again for your feedback. I appreciate this.

@all: Feel free to make your comments and suggestions too. I will mark this as resolved for now as we don’t discuss bugs and problems here.

As of

1. Ability to change the form type for default fields

I could do this as the layout of WooCommerce Poor Guys Swiss Knife allows me to redefine all fields not only the custom fields added but there are some limitations as some of the standard WooCommerce fields are vital for the operation of WooCommerce itself and the documentation of WooCommerce states that this implies risks. Without extensive testing I will not push this further for now as you can disable / remove WooCommerce fields and add your own fields and place these custom fields whereever you want. This allows everybody to “substitute” or introduce fields with the desired behaviour. I’m not saying never but I would need some more feedback on this with use cases (examples) which allow me to estimate that there’s a real demand for this.

2. Text type for new field (not a text box)

I don’t know if I got this right. Do you want to be able to add text instead of a field? I could do this, if this is what you mean. I could allow small text chunks to be placed inside the checkout forms. Please elaborate a bit on this point, if I got it right or, if not, what you feature you request here.

3. Ability to edit/rename ADDITIONAL INFORMATION & Order Notes…

Both of these things are available within the WooCommerce Rich Guys Swiss Knife already. I may include an update to allow to edit the Order Comment field and the Order section title, so, to make the Poor Guys Swiss Knife a bit more attractive and versatile but I have to ponder this question a bit as there are three or four commercial plugins, one from WooThemes itself and I feel some responsibility for the works of others, too, especially WooThemes as they provide the basis for the Poor and the Rich Guys Swiss Knife.

4. Remove completely billing section!, shipping section! or additional information…

I will check on this. Seems a good point as I’ve seen some requests in other contexts for this.

Regards and thanks.
ulih

Hello agusbagus.

Could you please test the version 1.5.1. This should solve the problem for customers who wish to edit their billing or shipping address without producing inconsistencies with the desired configuration for address fields.

I would appreciate a short reply and if 1.5.1 solves the problem I would be glad to receive a positive review or rating.

Thanks.
ulih