Missing text-domain for string translations about codepotent-update-manager HOT 5 CLOSED

On further consideration, I'm re-opening this issue. I see no harm in simply adding the text domain. It won't break anything and, well, it's only 3 strings. I'll get this into the 1.0.0 final release, which I anticipate in another week or so, just to be sure no further issues roll in.

from codepotent-update-manager.

I think you should consider it. If you add text domain to "core" texts, they will not be translated. Never, because strings in UpdateClient.class.php for being translated need to have my-text-domain as text domain (when used not for Update Manager itself).

The line that adds the "View details" link, where there is codepotent-update-manager as text domain (and a typo, it should be esc_html__ and not esc_html) for me creates inconsistent UX in the plugin page.

from codepotent-update-manager.

The line that adds the "View details" link, where there is codepotent-update-manager as text domain (and a typo, it should be esc_html__ and not esc_html) for me creates inconsistent UX in the plugin page.

Thanks, @xxsimoxx, for the additional information. Please open a dedicated issue for this part as it is different than the issue initially raised. I just don't want it to become lost in the mix. 😄

from codepotent-update-manager.

Hi @bahiirwa, good eye! The text domain hasn't been forgotten; these are actually the core texts, so, they don't require a text domain. :)

from codepotent-update-manager.

It seems I originally didn't comprehend what Simone was trying to say above. As he correctly points out, adding a text domain to the update client texts actually breaks the core translation functionality. In light of this, the text domain will be re-removed.

For those who have trouble with builds or sniffs, just add your own text domain to the client file – the same domain that you're using in your plugin.

from codepotent-update-manager.