Support · JNofollow 6.2.8

JNofollow support

Most issues resolve in two minutes with the checklist. For everything else, an email reaches the developer directly – JNofollow is a personally maintained project, and that is a feature.

Quick checklist: links are not being changed?

1. Plugin active? Plugin Manager → Content – JNofollow by SEO NW must be enabled – content plugins are off after installation.
2. Cache cleared? Joomla caches rendered content: System → Clear Cache, plus a private browser window for the test.
3. Tokens visible as text? If {nofollow=off} appears literally on your site, the plugin is not running – see points 1 and 2.
4. A rule doing its job? Whitelist entry, bypass class, data-follow or an article switch may be keeping exactly this link follow – check the settings against the demo cases.
5. Blacklist interplay? The blacklist overrides every bypass – a “stubborn” nofollow often sits there.
6. Testing the right output? Judge the rendered front end (element inspector), not the editor view – the editor shows the stored, unprocessed HTML by design.

What a helpful bug report contains

One email with the facts beats five: your Joomla version, PHP version, the JNofollow version (plugin manager or changelog), the chosen rel strategy (keep/overwrite) – plus one example link as stored in the article and as rendered in the front end. Please never send passwords or access credentials by mail.

Security reports

If you believe you have found a security issue in the plugin, please report it directly by email instead of posting it publicly – responsible disclosure protects all users. Security reports get honest top priority.

Contact

Write to 301@seo-manager.info. JNofollow is a privately maintained free project – replies usually arrive within a few days, with priority for reproducible bugs and security reports. No ticket bot: you write to the person who wrote the code.

Feature requests & translations

Suggestions are welcome – the whitelist/blacklist/bypass triad exists because users asked for control. The backend ships in English and German and is prepared for more languages; contributed translations are credited. A quick look into the FAQ sometimes answers the question already.