Text domain bug in WordPress 6.7 and above [issue #107] #108
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Text domain bug in WordPress 6.7 and above #107
After debugging, I found that ATHENA_SC__CACHE_BUST was being defined too early in the plugin loading sequence.
This caused _load_textdomain_just_in_time warnings, indicating that translation files were being loaded prematurely.
🔍 Debugging Process:
I traced the call stack and found that get_plugin_data() was triggering _load_textdomain_just_in_time too early.
I logged various WordPress hooks (plugins_loaded, init) to determine the correct execution timing.
Moving the definition of ATHENA_SC__CACHE_BUST to an init hook resolved the issue.
✅ Fix Implemented:
Wrapped define( 'ATHENA_SC__CACHE_BUST', athena_sc_get_cache_bust() ); inside an init hook.
Ensured translations and other plugin functions load only after WordPress initializes.
Types of changes
Checklist: