Loco Translate
[resolved] Feature Request: Let user decide where to save po/mo files (5 posts)

  1. podpirate
    Posted 2 years ago #

    As a plugin or theme developer I love to have my po/mo files living inside my packages language directory, so I can add it to my next plugin release.

    As a blog admin, who simply wants to localize a WP installation or maybe adapt some wording to his individual requirements, I would rather prefer my translations to be stored in WP_LANGUAGE_DIR, so they don't get zapped by a plugin update.

    An option like "save in package dir" vs. "save in WordPress language dir" would be helpful.

    Thanks, still a great work!


  2. timwhitlock
    Plugin Author

    Posted 2 years ago #

    Thanks. I'll give it some thought.

    For the record, Loco will attempt to save files in the same place as existing files, so if you put your POT file or other PO files in a particular location new files should follow suit.

    If there are no existing files, Loco will choose a writable directory over an unwritable one.

  3. timwhitlock
    Plugin Author

    Posted 2 years ago #

    The current development release now offers a choice of package vs global language directories when adding new files, but only when both locations are writable. If only one location is writable it will be automatically used. If neither location is writable the best match with existing files will be used automatically.

    Feel free to feed back. It'll go into v1.4.5 when ready to publish.

  4. podpirate
    Posted 2 years ago #

    The folder selection is pretty perfect, Thanks so far :)

    On the packages screen I get a fatal error on my local WP install:
    Screenshot: http://pasteboard.co/2EitUP3.png
    - wp-content is owned by webserver
    - no other plugins running
    - twentyfourteen theme

    Fatal error: Call to undefined method LocoPluginPackage::get_parent() in /www/vhosts/wordpress-stable.local/wp-content/plugins/loco-translate/lib/loco-packages.php on line 444
  5. timwhitlock
    Plugin Author

    Posted 2 years ago #

    Thanks for this. I spotted this bug yesterday and just uploaded a new dev version to SVN along with some other changes.

    I'll probably be releasing 1.4.5 today

Topic Closed

This topic has been closed to new replies.

About this Plugin

  • Loco Translate
  • Frequently Asked Questions
  • Support Threads
  • Reviews

About this Topic


No tags yet.