Hi,
I think lasso should useload_plugin_textdomain instead of manually building the path and using load_textdomain.
This brings the positive side effect that one doesn't have to reupload the translations after each update, since they can be stored in wp-content/languages/plugins instead of wp-content/plugins/lasso/languages.
Just replacing
$out = load_textdomain( $domain, trailingslashit( LASSO_DIR ). 'languages/' . $domain . '-' . $locale . '.mo' );
in
|
$out = load_textdomain( $domain, trailingslashit( LASSO_DIR ). 'languages/' . $domain . '-' . $locale . '.mo' ); |
with
load_plugin_textdomain( $domain, false, dirname( plugin_basename( LASSO_FILE ) ) . '/languages' );
is all that's needed and it still allows translations to be stored in the languages folder of lasso.
Hi,
I think lasso should use
load_plugin_textdomaininstead of manually building the path and usingload_textdomain.This brings the positive side effect that one doesn't have to reupload the translations after each update, since they can be stored in
wp-content/languages/pluginsinstead ofwp-content/plugins/lasso/languages.Just replacing
in
lasso/public/includes/lasso.php
Line 251 in 836c5da
is all that's needed and it still allows translations to be stored in the languages folder of lasso.