[rene.appeldoorn]

Thanks Melanie, I’ll dive into it.

[rene.appeldoorn]

Thanks Ed! By the way: 40/60 was a very good guess 😉

[rene.appeldoorn]

You’re right, it’s a plugin. Sorry, but thanks for looking. Pop-up still looks ugly though, that’s because of the translated text.

[rene.appeldoorn]

Last reply for today: it looks like the text ‘Subscribe to our newsletter‘ is not listed in the .po file too. This text is visible in the popup dialog when creating an account.

That popup by the way looks a bit ugly when the translated text is wider than the original English text (see attachment).

[rene.appeldoorn]

A bit off-topic, but yes, it would be nice to look over Ed’s shoulder to see what he is currently working on (roadmap). But on the other hand, that takes time too and people should learn to use the search option to find out whether an issue is already discussed. Also I’m afraid too many sticky topics won’t help either.

[rene.appeldoorn]

Great news indeed! Although I like the tabbed ‘wizard style’. If possible it would be very nice to trigger the required field validation when a user clicks on the ‘next’ button. That’s in fact the only confusing thing for a customer.

Another usability enhancement would be nice too. I don’t know exactly how to design this, but I’m sure Ed will have a good idea. When a customer enters step 3 in the checkout process, the payment method selection is on the very bottom of the page. That’s confusing, because the customer only sees the shopping bag and has to scroll down for payment. It is confusing, because the customer thought he entered the ‘payment’ procedure and now he has to ‘search for it’.

So Ed: please fix this today 😉 (I’m pretty sure you read my comments in another topic, so you’ll see the joke)

[rene.appeldoorn]

Oh, by the way: As Ed says, a new bugfix will be released soon and this issue will be solved with this release. That’s within two weeks after reporting the issue. That’s not too bad?!

[rene.appeldoorn]

@Ultraschall2d: First of all: I’m not hired by Ed to say this. I’m just trying to make life a bit easier for you – and possibly others too. It worked for me.

I really do understand your frustration, but you have to think about this: It’s impossible for Ed to read all forum topics. That’s what the other support girls and guys do. I’m pretty sure they do their very best to scan al topics for serious issues and pass them through to Ed if it’s a serious issue.

I think that’s a good thing, because you should be aware of the fact that every single person is convinced his issue is a serious bug and should be fixed by the developer immediately. I’m not a developer, but I’m pretty sure this is not true in 80% of the cases.

So please give Ed some space to do things he does best and try to live with the fact that it sometimes takes a few extra replies to convince everyone it’s really an issue that should be solved by Ed.

[rene.appeldoorn]

Well Melanie, because the topic I’m referring to, is about the same thing. And Ed wrote:

“This is actually standard WooCommerce functionality, we don’t change how the form works. We will add this to the wishlist for possible improvement.”

[rene.appeldoorn]

You’re a genius Tahir, thanks! Does Ed add this code to future updates?

[rene.appeldoorn]

I have recorded a 30 seconds screen capture. Any help would be appreciated.

[rene.appeldoorn]

Update: also hovering the two buttons on the bottom of the shopping bag brings the shopping bag back to front.

[rene.appeldoorn]

Check this

[rene.appeldoorn]

Sorry Melanie, partially true. Two of the ‘missing strings’ are indeed translatable with the .po file:

1) Button ‘Write a review’ in single product page
2) Text ‘Review’ next to the stars on top of a reviewed single product page

But here’s the surprise: the translations are ‘nog being used’ by the theme. So instead of showing the translated text, the theme is ignoring it and showing the original English text.

Finally, the third translation string I mentioned in this topic:

3) Text ‘There are no reviews yet, would you like to submit yours?’ in a not-yet-reviewed single product page

The .po file really doesn’t contain this string. So if you have a .po file containing this string I am really nuts or we have different files.

[rene.appeldoorn]

No, sorry, doesn’t work. Hovering the mouse over the shopping bag icon in the header, shows a strange behavior. The entire shopping bag ‘pops up’ on top of the screen (as it is supposed to do), but then the product image underneath the shopping bag ‘pushes’ the shopping bag to a ‘lower level’ and the product image then shows on the upper layer. Maybe this has nothing to do with z-index, but with the Product Overlay Transition effect (which I turned off by the way).

When I turn on the Product Overlay Transition effect, and hover a product image, the product featured image will appear. And here we go: when moving away the mouse pointer, the ‘original’ product image will of course re-appear, but when quickly moving the mouse over the shopping bag icon in the header (during the transition effect), the shopping bag IS on top of the page.

So, probably the (Javascript?) Product Overlay Transition causes this shopping bag behavior. Disabling the Product Overlay Transition effect does not solve this problem, but that is probably because the effect script is loaded anyway?