Turns out you need to create a `locale` folder first using `mkdir locale`. If you are running the command from within an app folder, you need a `locale` folder within that app folder.

Actually you can configure where the locale folder is. In your settings.py add:

    LOCALE_PATHS = (
        PROJECT_ROOT + &#39;/website/locale&#39;, )


Then create a folder for each of the languages you want to translate: 

    mkdir -p website/locale/de

The problem is that the command is not run from the app directory but from the project directory. [This snippet from the docs][1] explains it: 

Turns out you need to create a `locale` folder first using `mkdir locale`.
&gt; ``./manage.py makemessages`` […] Runs over the entire source tree **of the current directory** and pulls out all strings marked for translation. It creates (or updates) a message file in the conf/locale (in the Django tree) or locale (for project and application) directory. 

So, you either run the command from the app directory:

    $ cd app
    $ django-admin makemessages -l &lt;locale&gt;

… or you define a project wide locale directory using ``LOCALE_PATHS`` and you can run ``makemessages`` from the main directory from there on.

Either way, you should check that the ``./locale/``directory is present and create it using 
    
    $ mkdir locale

in case it&#39;s not.

  [1]: https://docs.djangoproject.com/en/1.10/ref/django-admin/#django-admin-makemessages

Brand new to JS.    	
I am trying to check if the file input element is empty when submitting the form with jQuery/JavaScript.
I have gone through a bunch of solutions and nothing is working for me.  I am trying to avoid the `/c/fakepath` (unless there is no other option)

    &lt;input type=&quot;file&quot; name=&quot;videoFile&quot; id=&quot;videoUploadFile&quot; /&gt;

This does not work:

    var vidFile = $(&quot;#videoUploadFile&quot;).value;

The only way I can get the filename is if I use the following:

    var vidFile = document.getElementById(&quot;videoUploadFile&quot;).files[0].name;

If there is no file available the code throws an error: 
&gt;cannot read property name of undefined

which makes sense because the array is not set. but I cannot figure out how to do any error handling with this.

How do I properly grab the file input element `videoUploadFile`, check if it&#39;s empty, throw an error message if it&#39;s empty?

How to check if input file is empty in jQuery

I tried to convert my Go map to a json string with `encoding/json` Marshal, but it resulted in a empty string.

Here&#39;s my code :

    package main
    
    import (
    	&quot;encoding/json&quot;
    	&quot;fmt&quot;
    )
    
    type Foo struct {
    	Number int    `json:&quot;number&quot;`
    	Title  string `json:&quot;title&quot;`
    }
    
    func main() {
    	datas := make(map[int]Foo)
    
    	for i := 0; i &lt; 10; i++ {
    		datas[i] = Foo{Number: 1, Title: &quot;test&quot;}
    	}
    
    	jsonString, _ := json.Marshal(datas)
    
    	fmt.Println(datas)
    	fmt.Println(jsonString)
    }

My output is :

    map[9:{1 test} 2:{1 test} 7:{1 test} 3:{1 test} 4:{1 test} 5:{1 test} 6:{1 test} 8:{1 test} 0:{1 test} 1:{1 test}]
    
    []

I really don&#39;t know where I&#39;m wrong. Thank you for your help.

Convert Go map to json

I&#39;m trying to translate a Django app. I created some strings with `{% trans %}` in my templates. However, when I execute the following command in my app folder, I receive an error message:

    $ django-admin.py makemessages -l fr 
    CommandError: Unable to find a locale path to store translations for file __init__.py`

What did I do wrong?



Unable to find a locale path to store translations for file __init__.py

I'm trying to translate a Django app. I created some strings with <code>{% trans %}</code> in my templates. However, when I execute the following command in my app folder, I receive an error message:
<pre><code class="hljs language-vbnet">$ django-admin.py makemessages -l fr 
CommandError: Unable to find a locale path to store translations for file __init__.py`
</code></pre>
What did I do wrong?

I&#39;m planning to rename several models in an existing Django project where there are many other models that have foreign key relationships to the models I would like to rename. I&#39;m fairly certain this will require multiple migrations, but I&#39;m not sure of the exact procedure.

Let&#39;s say I start out with the following models within a Django app called `myapp`:

    class Foo(models.Model):
        name = models.CharField(unique=True, max_length=32)
        description = models.TextField(null=True, blank=True)
    
    
    class AnotherModel(models.Model):
        foo = models.ForeignKey(Foo)
        is_awesome = models.BooleanField()


    class YetAnotherModel(models.Model):
        foo = models.ForeignKey(Foo)
        is_ridonkulous = models.BooleanField()

I want to rename the `Foo` model because the name doesn&#39;t really make sense and is causing confusion in the code, and `Bar` would make for a much clearer name. 

From what I have read in the Django development documentation, I&#39;m assuming the following migration strategy:

Step 1
====

Modify `models.py`:

    class Bar(models.Model):  # &lt;-- changed model name
        name = models.CharField(unique=True, max_length=32)
        description = models.TextField(null=True, blank=True)
    
    
    class AnotherModel(models.Model):
        foo = models.ForeignKey(Bar)  # &lt;-- changed relation, but not field name
        is_awesome = models.BooleanField()


    class YetAnotherModel(models.Model):
        foo = models.ForeignKey(Bar)  # &lt;-- changed relation, but not field name
        is_ridonkulous = models.BooleanField()

Note the `AnotherModel` field name for `foo` doesn&#39;t change, but the relation is updated to the `Bar` model. My reasoning is that I shouldn&#39;t change too much at once and that if I changed this field name to `bar` I would risk losing the data in that column.

Step 2
====

Create an empty migration:

    python manage.py makemigrations --empty myapp

Step 3
====

Edit the `Migration` class in the migration file created in step 2 to add the `RenameModel` operation to the operations list:

    class Migration(migrations.Migration):
    
        dependencies = [
            (&#39;myapp&#39;, &#39;0001_initial&#39;),
        ]
    
        operations = [
            migrations.RenameModel(&#39;Foo&#39;, &#39;Bar&#39;)
        ]


Step 4
====

Apply the migration:

    python manage.py migrate

Step 5
====

Edit the related field names in `models.py`:

    class Bar(models.Model):
        name = models.CharField(unique=True, max_length=32)
        description = models.TextField(null=True, blank=True)
    
    
    class AnotherModel(models.Model):
        bar = models.ForeignKey(Bar)  # &lt;-- changed field name
        is_awesome = models.BooleanField()


    class YetAnotherModel(models.Model):
        bar = models.ForeignKey(Bar)  # &lt;-- changed field name
        is_ridonkulous = models.BooleanField()

Step 6
====

Create another empty migration:

    python manage.py makemigrations --empty myapp

Step 7
====

Edit the `Migration` class in the migration file created in step 6 to add the `RenameField` operation(s) for any related field names to the operations list:

    class Migration(migrations.Migration):
    
        dependencies = [
            (&#39;myapp&#39;, &#39;0002_rename_fields&#39;),  # &lt;-- is this okay?
        ]
    
        operations = [
            migrations.RenameField(&#39;AnotherModel&#39;, &#39;foo&#39;, &#39;bar&#39;),
            migrations.RenameField(&#39;YetAnotherModel&#39;, &#39;foo&#39;, &#39;bar&#39;)
        ]

Step 8
====

Apply the 2nd migration:

    python manage.py migrate

&lt;hr/&gt;

Aside from updating the rest of the code (views, forms, etc.) to reflect the new variable names, is this basically how the new migration functionality would work?

Also, this seems like a lot of steps. Can the migration operations be condensed in some way?

Thanks!

Django migration strategy for renaming a model and relationship fields

This is the package I&#39;m interested in:

*[Django filebrowser no Grappelli][1]*

However, the latest version no longer supports Django 1.3. I need to find a version that does.
How do I see a list of older versions?

  [1]: https://pypi.python.org/pypi/django-filebrowser-no-grappelli/




pypi see older versions of package

Django **1.7** introduced [database migrations][1].

When running the unit tests in Django 1.7, it forces a *migrate*, that takes a long time. So I would like to skip the django migrations, and create the database in the final state.


I know that ignoring the migrations can be a bad practice, as that part of the code would not be tested. But that&#39;s not the case: I&#39;m running the full migrations in the CI test server (jenkins). I only want to skip the migrations in my local tests, where the speed matters.


----------


Some context:

Until Django **1.6**, when using South, I used the [*SOUTH_TESTS_MIGRATE*][2] setting:

&gt; By default, South’s syncdb command will also apply migrations if it’s run in non-interactive mode, which includes when you’re running tests - it will run every migration every time you run your tests.
&gt;
&gt; If you want the test runner to use syncdb instead of migrate - for example, if your migrations are taking way too long to apply - simply set SOUTH_TESTS_MIGRATE = False in settings.py.

However, *syncdb* does not exist anymore, now it&#39;s *migrate*.


And from Django **1.8** I&#39;ll use the *[--keepdb][3]* parameter:

&gt; The --keepdb option can be used to preserve the test database between test runs. This has the advantage of skipping both the create and destroy actions which greatly decreases the time to run tests, especially those in a large test suite. If the test database does not exist, it will be created on the first run and then preserved for each subsequent run. Any unapplied migrations will also be applied to the test database before running the test suite.


So this question is limited to Django 1.7.


  [1]: https://docs.djangoproject.com/en/1.7/topics/migrations/
  [2]: http://south.readthedocs.org/en/latest/unittests.html
  [3]: https://docs.djangoproject.com/en/dev/ref/django-admin/#django-admin-option---keepdb

Disable migrations when running unit tests in Django 1.7

In my view to get url parameters like this:

    date=request.GET.get(&#39;date&#39;,&#39;&#39;)

In my url I am trying to pass parameters in this way with the url template tag like this:  

    &lt;td&gt;&lt;a href=&quot;{% url &#39;health:medication-record?date=01/01/2001&#39; action=&#39;add&#39; pk=entry.id %}&quot; &gt;Add To Log&lt;/a&gt;&lt;/td&gt;

The parameter after the ? is obviously not working, how can I pass this data value in order to retrieve in with a get?


How to add url parameters to Django template url tag?

I&#39;m having a little difficulty getting my head around relationships in Django models. 

Could someone explain what the difference is between a OneToOne, ManyToMany and ForeignKey?

Whats the difference between a OneToOne, ManyToMany, and a ForeignKey Field in Django?

Background
--
I&#39;ve recently migrated [**my app**][1] to Android-Studio. I had some issues doing so, but I got over them eventually.

The problem
--
For some reason, on Android Studio, when I try to sign an APK, I get a lot of errors that look like this:

    Error:(16) Error: &quot;...&quot; is not translated in &quot;de&quot; (German), &quot;el&quot; (Greek), &quot;iw&quot; (Hebrew) [MissingTranslation]

(where &quot;...&quot; is a string) 

At the bottom, after a lot of errors of this kind, I see this:

    Error:Execution failed for task &#39;:app:lintVitalRelease&#39;.
    &gt; Lint found fatal errors while assembling a release target.
    To proceed, either fix the issues identified by lint, or modify your build script as follows:
    ...
    android {
        lintOptions {
            checkReleaseBuilds false
            // Or, if you prefer, you can continue to check for errors in release builds,
            // but continue the build even when errors are found:
            abortOnError false
        }
    }
    ...

The question
--
I&#39;m not sure what&#39;s wrong and how I can fix it. On Eclipse I did it very easily. Missing translations shouldn&#39;t stop me from signing an APK... 

To me it seems as if Lint is preventing the exporting of the APK, and that the reason is that I didn&#39;t translate all of the strings. Is that true?

Can anyone please help me? How can I fix this, so that Lint will show me just warnings instead? or a confirmation dialog if I&#39;m sure I want to do it?


  [1]: https://play.google.com/store/apps/details?id=com.lb.app_manager

How to sign APK on Android Studio even with non-translated strings?

I&#39;m building an app that will need to be available in multiple languages and locales.

My question is not purely technical, but rather about the architecture, and the patterns that people are actually using in production to solve this problem.
I couldn&#39;t find anywhere any &quot;cookbook&quot; for that, so I&#39;m turning to my favourite Q/A website :)

Here are my requirements (they are really &quot;standard&quot;):

* The user can choose the language (trivial)
* Upon changing the language, the interface should translate automatically to the new selected language
* I&#39;m not too worried about formatting numbers, dates etc. at the moment, I want a simple solution to just translate strings

Here are the possible solutions I could think off:

**Each component deal with translation in isolation**

This means that each component have for example a set of en.json, fr.json etc. files alongside it with the translated strings. And a helper function to help reading the values from those depending on the selected language.

* Pro: more respectful of the React philosophy, each component is &quot;standalone&quot;
* Cons: you can&#39;t centralize all the translations in a file (to have someone else add a new language for example)
* Cons: you still need to pass the current language as a prop, in every bloody component and their children

**Each component receives the translations via the props**

So they are not aware of the current language, they just take a list of strings as props which happen to match the current language

* Pro: since those strings are coming &quot;from the top&quot;, they can be centralized somewhere
* Cons: Each component is now tied into the translation system, you can&#39;t just re-use one, you need to specify the correct strings every time

**You bypass the props a bit and possibly use the [context][1] thingy to pass down the current language**

* Pro: it&#39;s mostly transparent, don&#39;t have to pass the current language and/or translations via props all the time
* Cons: it looks cumbersome to use


If you have any other idea, please do say!

How do you do it?


  [1]: https://www.tildedave.com/2014/11/15/introduction-to-contexts-in-react-js.html

Content Type	Original Author	Original Content on Stackoverflow
Question	Antoine M.	View Question on Stackoverflow
Solution 1 - Django	Antoine M.	View Answer on Stackoverflow
Solution 2 - Django	David Dehghan	View Answer on Stackoverflow
Solution 3 - Django	jnns	View Answer on Stackoverflow

Unable to find a locale path to store translations for file init.py

Django Problem Overview

Django Solutions

Solution 1 - Django

Solution 2 - Django

Solution 3 - Django

Convert Go map to json

How to check if input file is empty in jQuery

Attributions