This is a bug.
Can you try to open the “/wp-content/ninjafirewall/ninjafirewall.php” script and to comment out lines 55, 60 and 68:
54 global $wp_version;
55 // if ( version_compare( $wp_version, '4.6', '<' ) ) {
56 add_action( 'init', 'nfw_load_translation' );
57 function nfw_load_translation() {
58 load_plugin_textdomain('ninjafirewall', FALSE, dirname(plugin_basename(__FILE__)).'/languages/');
59 }
60 // } else {
61 function nfwhook_load_textdomain( $retval, $domain, $mofile ) {
62 if ( $domain == 'ninjafirewall' && strpos( $mofile, '/plugins/ninjafirewall-fr_FR.mo') !== false ) {
63 load_textdomain('ninjafirewall', __DIR__ . '/languages/ninjafirewall-fr_FR.mo');
64 return true;
65 }
66 return false;
67 }
68 // }
69 add_filter('override_load_textdomain', 'nfwhook_load_textdomain', 10, 3);
Simply add a double-slash ‘//’ at the beginning of each line as shown above.
-
This reply was modified 9 years, 7 months ago by
nintechnet.
Faced with the same problem. Thank you, your solution helped)
Will this bug be solved in the next version?
It will be fixed in the next release.
This bug should only affect users running WordPress <4.6.