decarvalhoaa

Hi Anton,

happy New Year!

I have the same issue as Chris but with the Storefront theme from WooThemes.
I have added the class .avatar in the exclusion list in Smush Lazy Load module as you suggested.

I have seen that a couple of maintenance releases have been released since your last reply but this issue is not resolved.

Do you have a ETA for the fix? Thanks in advance.

Cheers,
A

• This reply was modified 4 years, 11 months ago by decarvalhoaa.

Hi there,

apologies for not responding back. I know that it is now near 4 month later but the issue persists. Let me know if you prefer that I open a new issue.

The suggestion to use free SSL certificate like Let’s Encrypt doesn’t help since the issue is on my development station (without a public domain name – it’s just localhost) and Industry rules completely forbid publicly trusted CAs like Let’s Encrypt from issuing certificates for internal domain names.
I can’t also make use of the following filter to disable ssl verification:

add_filter( 'backwpup_cacert_bundle', '__return_false' );

I tried as well the wordpress filter but it seems it is ignored by the plugin:

add_filter( 'https_local_ssl_verify', '__return_false' );

I’m my production server everything work perfectly since I’m using a public domain name.

The strange part is that before version 3.4.3 this was working also on my local development station.

Hi

Thanks you for the quick feedback.
Yes i can try that, but not before next weekend. I will post back if i’m successful overcoming the issue or otherwise.

Can you explain meanwhile what is the intended use of the filter ‘backwpup_cacert_bundle’?

Cheers
A

By the way, I upgraded WP to 4.8.2 and confirm the same behavior as described above.

Hi,

from where did you took the Order.php code? Please note that this fix is not yet pushed to the master – that is something Hyyan takes care. If you have taken the Order.php from the master branch, then it will not be fixed.

Try using the code from https://github.com/hyyan/woo-poly-integration/blob/828d8a03db0cc9056300bdcc9b3777bbcc216b34/src/Hyyan/WPI/Order.php

This is my commit with the fix.

Please note also that, the plugin is not yet fully functional with WC2.7. There are a lot of things broken. I would not use the plugin with WC2.7 in production stores.

No worries! The important is that you found the issue. I’m marking to resolve this thread as resolved.

What is the content of the Page with the slug ‘seleccion’?

And instead of clone the english product and then set the language to Spanish, have you tried clicking on the plus signal? in the Polylang metabox to create directly the translation?

I just tested on my setup and can’t reproduce the issue you described.

Just a thought, in the wordpress admin top bar there is a option to “Show all languages”. Is this set to “Show all languages” or have you set it to a single language?

Can you elaborate what you mean with every product is duplicated?

Have you created first the product in the primary language and then created a translation?
When you browse the shop on the secondary language, the translation is displayed twice, is that what you mean?

It’s actually polylang that adds the lang slug into the url. I never used my self the Shop Base = /shop. I use the slug /product and works fine. Can you try with /product instead just to check if this works?

Please share also your configuration for the other permalink settings, and what are the URL Modifications settings in Polylang.

For every WooCommerce page, like for example Shop, you need to create in the WordPress admin a translation. Copy the shortcode from the original page to the content of the translations you create.

You only need to edit the language files if the translation is not 100% completed for the language you are using. In that case, you can use a plugin like Loco Translate that can help you find what strings are not translated and translate it.

Thanks for reporting. I have seen this issue since WooCommerce 2.6.0. Unfortunately, WC 2.6. change the way customer orders are fetched from the database and is ignoring the language argument Hyyan plugin adds in.

I have created an issue with WooCommerce here. I have a fix for that but need some guidance from the WooCommerce folks.

Hello,

thanks for reporting. Some other user has reported this also. I found the issue and suggested the plugin owner a fix here among other things. Hopefully will come out a a future release.

If you don’t want or can’t wait for the fix, you can download the patch here and install it yourself.

When you press the plus sign to add the translation DON’T click edit afterwards.

Note that just after you click the plus sign at this point in the video, the language field in the form on the left hand side changes to Spanish. Your video doesn’t show, but if you scroll down you will see in the Translations field the flag English and the name “Test Category”.

So, after you click the plus sign (DON’T click edit) just fill in the form with your translation name and slug, i.e. “Categoría de prueba” and “prueba”. And of course click the button to save/add.

This is pretty much standard Polylang functionality. Nothing to to with this plugin.

To create a new category, in step 2, you create the category in the language set in the dropbox just below the Thumbnail field. The Translation field you can leave empty at this point. Click the button “Add New Product Category” and it should be added to the list on the right hand side (if not, just refresh the browser).

Now that you located your new category on the list to the right, you need to add the translation. Click on the plus signal for one of the other languages your site supports. The plus signal is under the column with the flags. If it is not there, it can be added in the Screen Options on the top of the screen.

After you click on the plus, you add the translation – just like you did before to create the new category – You will notice that the Translation field this time has the name of the category you created in the step before.

Let me know if this helps.