Replies: 2
This plugin’s slug is contact-form-7-dynamic-text-extension
, but the current Text Domain is aurise
. Change the current Text Domain so it is equal to this plugin’s slug, and modify the text domain in all your source files. This change is needed, please refer to this official article.
The GitHub repository seemed out-of-date, so I pasted the modified code here for your reference.
contact-form-7-dynamic-text-extension.php, line 13
* Text Domain: contact-form-7-dynamic-text-extension
includes\utilities.php
Line 67
__('%1$s is <strong>deprecated</strong> since version %2$s! Use Contact Form 7\'s built-in attribute "%3$s" instead. Contact Form 7 Documentation: %4$s', 'contact-form-7-dynamic-text-extension'),
Line 75
__('%1$s is <strong>deprecated</strong> since version %2$s! Use Contact Form 7\'s built-in attribute "%3$s" instead.', 'contact-form-7-dynamic-text-extension'),
Line 83
__('%1$s is <strong>deprecated</strong> since version %2$s with no alternative currently available.', 'contact-form-7-dynamic-text-extension'),
For \includes\admin.php, all changes are the same; change wrong text domain aurise
to contact-form-7-dynamic-text-extension
.
Line 54, 62, 81, 84, 90, 93, 107, 113, 121,134, 142, 145, 153, 166, 169, 177, 190, 204, 211, 219.
I saw this awesome plugin had been localized to 15 languages (including zh_TW) on the WordPress.org plugin directory. Still, this text domain issue must make this plugin cannot apply any language pack pushed from the GlotPress system.
Correcting text domain will fix this problem, tested.