django-th | Trigger Happy - The bus : bus : for your internet services | Microservice library

Ok, I figured it out after more research, as described here:

New code in forms.py

The solution is actually rather easy. The problem is the docker. The solution is stated here and works: https://medium.com/@vladyslav.krylasov/how-to-use-pdb-inside-a-docker-container-eeb230de4d11

Add this to your docker-compose.yml:

You're accessing the fields themselves, instead of the validated data. You need:

The basic idea of the error is, any view in Django must return HttpResponse or similar object. Here in your views, you are not returning the HttpResponse all the time. That is, the program execution not going into the if... clause of your code. and the execution can't go into the else.. clause unless you define them. So, I've added some else conditions.

Try this

The django-contrib-comments app, according to documentation, makes use of GenericForeignKey, meaning its own model can create a relation to any other model in your project.

A simple solution would be to just copy that existing functionality, creating your own Like/Rate application based on the same concept (i.e. storing the Like/Rate models in that application's models).

I think you would get very far starting out by forking the https://github.com/django/django-contrib-comments codebase.

(I assume you have searched and failed to find an already existing application that already does this).

For completion fields you do not want to be using ngram analyzers. The completion field will automatically index all prefixes and optimize for prefix queries so you are doing the work twice and confusing the system. Start with empty completion field and go from there.

I think i have found a solution for this. The problem could well be caused by the circular dependencies issues when you migrate your default AUTH_USER_MODEL to a custom model in the middle of the project.

From Django Documentation

Changing AUTH_USER_MODEL after you’ve created database tables is significantly more difficult since it affects foreign keys and many-to-many relationships, for example.

This change can’t be done automatically and requires manually fixing your schema, moving your data from the old user table, and possibly manually reapplying some migrations. See #25313 for an outline of the steps.

Due to limitations of Django’s dynamic dependency feature for swappable models, the model referenced by AUTH_USER_MODEL must be created in the first migration of its app (usually called 0001_initial); otherwise, you’ll have dependency issues.

In addition, you may run into a CircularDependencyError when running your migrations as Django won’t be able to automatically break the dependency loop due to the dynamic dependency. If you see this error, you should break the loop by moving the models depended on by your user model into a second migration. (You can try making two normal models that have a ForeignKey to each other and seeing how makemigrations resolves that circular dependency if you want to see how it’s usually done.)

The best way to tackle this is to drop the table and remove all migration files and then re run the migrations with your newly made custom model. Hope this will work.

More details on how to migrate from a built in model to a new model can be found here https://code.djangoproject.com/ticket/25313

You need to explicitly handle this case. In this case, your as_dict method should look like:

Your STATICFILES_DIRS setting looks odd. Are you sure you don't want this?