Localization file prevented upgrade until I set permissions correctly

  • Resolved mevilsizor

    (@mevilsizor)


    8 years, 2 months ago

    Hello,

    I effected the change of “name” to “term” by creating an English language localization file.

    When I first tried to upgrade, it failed and pointed me toward the localization file permissions.

    I found that I needed to change the permissions on these new files to match the existing files, then the upgrade worked as it should.

    However it did remove my .po and .mo files which I had to copy back in and then worked as before.

    https://wordpress.org/plugins/name-directory/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Jeroen Peters

    (@jeroenpeters1986)

    8 years, 2 months ago

    Hi mevilsizor,

    thanks for reporting this. It’s good to know in case another user will try and to the same thing. As I read it, there isn’t much I can do for now am I right? Just checking 🙂

    Kind regards,
    Jeroen

    Thread Starter mevilsizor

    (@mevilsizor)

    8 years, 2 months ago

    It would be great to put a new feature on your roadmap which would allow a custom word to be used instead of “name”. This could be in the settings page and make it very easy to set this once and not need to worry about it in the future.

    Thanks

    Plugin Author Jeroen Peters

    (@jeroenpeters1986)

    8 years, 2 months ago

    Hi mevilsizor, this is on my list. The only thing with this that it would be impossible to use in translations and all of the current translations have to be done from scratch. So I do have to think how to implement this properly

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Localization file prevented upgrade until I set permissions correctly’ is closed to new replies.