Make plugin translation ready

Hi @thezuberawordpress,
Thanks for the feedback, and sorry for the inconvenience. This was a maintenance update, to fix an issue reported by another user. We are activity working on a much larger update that will give you control over those strings mentioned above. Stay tuned.

• This reply was modified 4 years, 2 months ago by Christopher Raymond.

Hi,
Thank you for the great update. I’m not sure but I think your plugin doesn’t include the textdomain. I think you need to add this code to the main plugin file:

add_action( 'plugins_loaded', 'alertme_load_textdomain' );
function alertme_load_textdomain() {
  load_plugin_textdomain( 'alert-me', false, dirname( plugin_basename( __FILE__ ) ) . '/languages' ); 
}

Hi @thezuberawordpress
Can you explain a little more? Thx.

Please see https://developer.www.ads-software.com/plugins/internationalization/how-to-internationalize-your-plugin/#loading-text-domain

I also noticed Loco translate returns weird results when I try to generate a pot/po file from your plugin source code. You might want to check this too.

Ok, the Loco issue was probably my mistake – it used the wrong textdomain “alertme” instead of “alert-me”.

I found missing translations – in alertme\inc\front-end\alertme-subscriptions-list.php

the string “Page” is not translatable in line 72:

<th scope="col">Page</th>

and in 86

<label class="form-check-label" for="exampleCheck<?php echo $result['id']; ?>">Unsubscribe</label>

Also the “Front-End Subscribe Form Settings” do not work properly for me. I added custom text into the fields but the form still displays “SUCCESS! You are subscribed to alerts anytime this page is updated. To change your subscription preferences, click here.! “

Thanks @thezuberawordpress will check that out. Couldn’t get everything in this release ??