richardevcom

Thank you for info. I will look in to this.

Please open https://yourwebsite.com/wp-admin/admin.php?page=mlang and make screenshot where this message is shown, to prove that it really doesn’t work while Polylang is activated (change yourwebsite.com with your actual domain name).

We could not reproduce the same issue on neither version of Polylang plugin. If it is possible we have discord server where you might possibly present the issue with screen share and we might be able to get on debugging it asap?

• This reply was modified 3 years ago by richardevcom.

Hi there.

Please read this and provide more information on your environment.

We can’t reproduce the same issue on neither free and pro version of Polylang plugin, but we will look into it asap.

So far we could trigger this bug only in older versions, not in the new one.
Could you please provide more detailed info on versions, plugins and theme you’re using? Read this to see what to share.

Hi there.

Sorry for late reply. We have noted this bug and will debug it ASAP.
Thank you for your reply.

Meanwhile feel free to join our live support server here: Frontbee Discord server and I might be able to assist you directly.

Hi @jakovljevic984
I had a chance to test our latest plugin against multiple versions of WordPress with Polylang and Polylang PRO, but we couldn’t produce the same error.

However it seems like an old error we had. So we suggest, that you fully remove our plugin, clear cache and install it from Plugin Install page within your admin panel.

Also, join https://discord.gg/sfuevNp5E3 and you could maybe stream and show how and when does it happen, so maybe we can help you out.

For now it seems like an old issue that was fixed in older versions, so I’m closing this thread for now.

Yes. Thank you for waiting.

I’m currently making sure it can be replicated on WordPress default themes, since this is second time having similar report – we have a feeling it could indeed be due to our plugin trying to require a duplicate standalone files from Polylang.

After that, next step will be pushing bug fix if its a bug, or I’ll keep you updated here if it was something else.

Sorry it’s taking so long, but this is open source solution that we work on using our free time. ??

• This reply was modified 3 years, 3 months ago by richardevcom.

Hi there.
Thank you for detailed error report. I will check this out later this evening (EET) and get back to you in matter of 2 working days.

We haven’t heard back from you for a while, so for now we are marking this post as resolved.

• This reply was modified 3 years, 3 months ago by richardevcom.

Hi @emrecinar22
Please provide versions of our plugin, WordPress and theme you’re using.
Also PHP version you’re using.
We couldn’t reproduce this issue on latest one with Twenty Twenty One theme.

• This reply was modified 3 years, 4 months ago by richardevcom.
• This reply was modified 3 years, 4 months ago by richardevcom.

@biguenique thank you for your review. Glad it helped you! ??

In my case I edited POT file with another editor and added parsable function (translatable string function name) _nx and reupload it. As explained above, WooCommerce has some _nx strings and all of them were not read by Loco Translate. To read them first test workaround I did to make sure its because Loco Translate can’t read _nx was to rename it to _n and it worked. Then I just passed _nx to POT file an that’s all.

If you’re stating that Loco does parse _nx then I have to double check it was Locos fault in first place and get back to you with my findings.

• This reply was modified 3 years, 4 months ago by richardevcom.
• This reply was modified 3 years, 4 months ago by richardevcom.

@timwhitlock really weird. I tested on local test environment and WooCommerce _nx() translation strings behave the same.

Yeah, manually (for testing purposes).

I’ll double check that there is an error and it’s really not on my end and get back to you soon.

Thanks for follow up reply @rik1234