jrmarins

Is there anything temporary I can do to make it work until an official update comes out?

Hi, @doublezed2 and @barryhughes-1
And what about custom translations from now on? Will we never be able to customize our translations through a file in a specific location again? Will we have to render yet another third-party plugin to overload our WP?
Or is WOO looking for a solution so that we can have a file with our translations?

I’ve been testing it for a few days and so far it’s ok.

I don’t think there’s a problem, the store won’t stop working because the translation file hasn’t been updated, the most that can happen is a warning in the log.

If any problems appear I’ll post them here.

Hi, @senseart
Thanks for your help!
I’m currently testing another workaround. I changed the permissions of the woocommerce-pt_BR.l10n.php file to read-only permissions. So, theoretically, the woo plugin wouldn’t be able to replace the file. I’ll wait a few more days to see if it stays the same. In the meantime, I’ll wait for woo to update the plugin and resolve this error.
If my solution doesn’t work, I’ll test your code next.

Thanks.

Hi, @ckadenge.
Thanks for the reply.
I’ve been using this solution for a while now, but it’s temporary. From time to time, the deleted files come back. I don’t know if it’s WordPress that creates these files or WooCommerce, but they come back again and I have to check every day to delete them again.
I’d like a definitive solution for this. WooCommerce could allow me to place the customized .l10n.php file inside language/woocommerce and only search for the translation from there, as it used to work until recently.

My WP already has many plugins and I don’t want to add more. I’ve always used the translation by making changes to the .mo and .po files and it’s always worked well. After a few updates, I got this error. Is there any way to block the translation update coming from WOO? Or force it to search for my custom translation file? I’ve also used the code below, as indicated in this link: https://woocommerce.com/document/como-traduzir-o-woocommerce-localizacao/ but it’s not working either.

function load_custom_plugin_translation_file( $mofile, $domain ) {
  if ( 'textdomain' === $domain ) {
    $mofile = WP_LANG_DIR . '/textdomain/yourtranslationfile-' . get_locale() . '.mo';
  }
  return $mofile;
}

@qtwrk

open ticket: #684725

Hi @qtwrk.

I made the update and I’ve been following it for a few days and the problem still persists.

Report number: UTTBHAUL

Report date: 09/10/2021 21:24:52

@qtwrk

Updated now, I’ll wait a few days to see if the error appears again.

Thanks.

Hi @dvazquez260376

Thanks for the answer! It seems to make sense why I removed this option, but it is a great pity, it blocked many attempts to search for backup files on my server.
They could come back with this option for zip, rar, sql and other files that intruders try to find.

Same problem here, version 3.0.2

• This reply was modified 5 years, 9 months ago by jrmarins.

Consegui resolver com o plugin WP Disable Autofill

OK thank you.
The problem was the same!