Please fix text domain issue

  • For a long time, the text domain in this plugin code has been acf, and its text domain should be advanced-custom-fields. Please fix this long-standing bug as soon as possible.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Moderator Felipe Santos

    (@foosantos)

    Hi there,

    Doing something like that right now would likely bring several compatibility issues, and I’m not sure what exactly it would achieve.

    As SCF is a new plugin, I believe the long-term goal is to have it as scf or secure-custom-fields as the text domain, but not something that will be done until it is possible technically without bringing issues.

    Thread Starter Alex Lion (阿力獅)

    (@alexclassroom)

    Whatever this plugin’s current changes are, its text domain should be advanced-custom-fields, or the language packs delivered by GlotPress can’t be affected.

    https://developer.www.ads-software.com/plugins/internationalization/how-to-internationalize-your-plugin/#text-domains

    If this plugin should have a new slug/text domain, the new developers should create a new SVN repository for it, and then maybe add a migration feature for ACF to SCF.

    tplomari

    (@tplomari)

    @foosantos I’m a bit confused – if this is a new plugin, how do the support forum and reviews for it go back years and years? That doesn’t make sense.

    dooza

    (@dooza)

    This is why Automatic should have forked it with a new slug straight away rather than take over and rename an existing plugin. We’re not getting support from the orginal developers as they have been blocked from www.ads-software.com. None of this makes sense.

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.