XF Premium Content Blur Pro - Boost Registrations and Upgrades 2.2.11

• UPDATE: Crawler-detect (v1.3.0 => v1.3.4)
• REMOVED: Installer requirement that page caching be disabled
• ADDED: Installer warning outlining the issues with full page caching for guests and the issue that search engines may index obfuscated content unless obfuscation is disabled for guests.
• ADDED: Validation when enabling guest obfuscation in options, if full page caching is also enabled in config.php, validation will fail
• CHANGE: Made guest obfuscation disabled by default
• ADD: Phrase warning + some typo corrections on existing options

• FIX: recordUpgradeView() should not require $threadId
  • This issue was introduced in v2.2.8 to v2.2.9 and requires immediate upgrade if running those previous versions

• BUG FIX: Setting Unblurred Posts to zero (0), or "Inherit 0", would leave all posts unblurred instead of no posts unblurred
• BUG FIX: (Articles/Questions) setting Unblurred Paragraphs to zero would cause: ErrorException: [E_WARNING] preg_match()
• BUG FIX: Obfuscation now always follows individual settings for Users vs Guests
• ADD: Option whether to "Show full article text blurred after fading first X paragraphs?"
• Permission renamed to "How many posts are always unblurred?"
• Permission renamed to "How many [Article] paragraphs are faded?"

• FIX: [User Mode] -> Number of posts unblurred (was previously being ignored in User Mode)
• UPDATE: Long running articles, after fading paragraphs, now also shows remaining article text blurred and obfuscated
• FIX: Error where creating a thread can throw an error due to thread_id being null
• FIX: Improve debugging issue with node_id and thread_id confusion leading to tail chasing during debug
• REMOVE: Unneccessary XF/Pub/Controller/Forum.php class extension
• REMOVE: Unused template modification

FIX: Oddity with templater modification requiring a full line break or else it tries to autoclose a non-existent curly brace