joel_birch

Hello. In order to help you debug this, I think I’d need to know which other plugins you have activated and also which PHP version you are running.

Square bracket syntax for arrays requires PHP v 5.4, if I remember correctly. If you can update PHP on your server it’s highly recommend.

Sorry about that! I began using a feature of PHP 5.4, without thinking how many people may still be stuck on 5.3 and below.

I have pushed an urgent update which corrects this. The auto-update seems to be slow today, but if you need the update urgently you can download it from https://nofollowr.com and install manually. Or just wait until the auto-update appears in your plugin page.

Thank you for this report!

Joel Birch.

Great, thanks for prioritising this, we really appreciate it! I’ll look forward to the update.

Cheers.

The issue seems to be on line 196 of the wp-approve-user.php file.

$suffix = defined( 'SCRIPT_DEBUG' ) AND SCRIPT_DEBUG ? '' : '.min';

Should be:

$suffix = (defined( 'SCRIPT_DEBUG' ) AND SCRIPT_DEBUG) ? '' : '.min';

Note the brackets around the condition part of the ternary statement. This fixes the issue for me, so hopefully the plugin will be updated to include this fix.

Sorry, I wasn’t clear. I’m just suggesting a feature for you to add to the plugin whereby it adds an opt-in checkbox to the registration form.

I’m hoping this can be fixed soon as it clogs up my error logs and makes debugging difficult. Thanks in advance.

Interesting feature suggestion, thanks.

I guess this resolved itself.

I have tested that the plugin works all the way up to WP 4.0 given the default twentyfourteen theme and no other plugins.

Now tested to work on WordPress 4.0 and I have updated that note on the plugin page.

I wish I could help you all. @stardaug you mentioned W3 Total Cache – are you using that plugin? If so, do you have “Don’t cache pages for logged in users” unchecked? If you click a nofollowr icon then edit the page and go to text view is the nofollow rel attribute altered?

@cspeake your issue seems to be unrelated and would need proper debugging.

Omitting the closing slash on a self-closing element is valid HTML5. Please see this Stack Overflow answer (plus official spec references it provides).

Thanks very much, that worked. Coincidentally, it was also the solution for another plugin with a similar issue, so double thanks!

I’ve heard this issue a few times over the years so it doesn’t seem related to specific WP updates. Whenever I attempt to recreate the issue so I can debug it the plugin works perfectly. I wonder if you have caching interfering, or…I don’t know what else. More information would be appreciated because it’s impossible to debug without access to the problem website in question.