WordPress / WordPress/secure-custom-fields
Function _load_textdomain_just_in_time was called incorrectly (WP version 6.7 and above)
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 131
- Forks
- 64
- Avg merge
- 10m
- Merged PRs (30d)
- 1
Description
the following notice for secure custom fields is now displayed for wordpress version 6.7 and above:
Notice: Function _load_textdomain_just_in_time was called incorrectly. Loading translation for the secure-custom-fields domain was activated too early. This is usually an indication that some code in the plugin or the theme encounters something too early. Translations should be loaded during the init action or later. Read Debugging in WordPress for more information. (This message was added in version 6.7.0.)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating where the secure-custom-fields translation domain is loaded, then reproduce the notice on WordPress 6.7 or later. The issue does not name a file or test; done means the notice no longer appears while the plugin's translations continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- internationalization
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100