Fixed
- Resolved the WordPress 6.7+ "translation loading was triggered too early" notice that 0.5.0 reintroduced: the plugin logged one
_load_textdomain_just_in_timenotice on every request, whether or not any translations were installed. The Excluded paths field's label and help text are now translated lazily, when the settings page renders (afterinit), instead of while the plugin file is still being included.Settings\Fieldwas the one value object that never received the lazy-label treatmentSectionandCapability_Columngot in 0.2.2, so the two strings the 0.5.0 exclusion section introduced were resolved at bootstrap.Fieldnow accepts aClosure(): stringfor bothlabelanddescription, mirroringSection::title()andCapability_Column::label(), and unit tests guard all three against resolving a label at construction.
Full changelog: https://github.com/Kntnt/kntnt-ai-visibility/blob/v0.5.1/CHANGELOG.md