Opened 7 years ago

Closed 7 years ago

#2582 closed defect (bug) (invalid)


Reported by: elliotcondon's profile elliotcondon Owned by:
Milestone: Priority: normal
Component: Translate Site & Plugins Keywords:


Hi Guys,

Elliot here from ACF (Advanced Custom Fields plugin).

I'm looking at the 'translate' page for my plugin ( and it says "This plugin is not properly prepared for localization".

I'm guessing this is because my plugin uses a textdomain of 'acf' which is different to my plugin slug 'advanced-custom-fields'.

I don't see why I should be penalized for choosing an optimized textdomain, is it possible to allow this case?


Change History (1)

#1 @Otto42
7 years ago

  • Component changed from General to Translate Site & Plugins
  • Resolution set to invalid
  • Status changed from new to closed

No, the system is entirely built around the slug being the same as the textdomain. That's how language packs work at a very fundamental level.

You can either change your textdomain, or ship your own translations in the plugin and not use the system.

Note: See TracTickets for help on using tickets.