Sunday February 12th from 11:00pm to 02:00am Monday Morning PST

247Apps VPS Scheduled Maintenance


We will be conducting an upgrade to our VPS Servers to provide greater stability and speed. This upgrade will occur during the wee hours of the morning when you are all asleep.
Starting Sunday February 12 @ 11:00pm PST. Our scheduled window for this maintenance cycle should be under 3 hours.
We apologize for any inconvenience this disruption may cause and thank you for your patience.

Thank you,
247AppsMobi – Web Services of MyNetworkSolution Dev Team

How to Return JSON Encoded Response for a non-dict object

In DJango, an HttpResponse sub-class helps to create a JSON-encoded response. It was called Serialized-Object response in Django < 1.7. Its default Content-Type header is set to application/JSON. The first parameter (data set), should be a dict instance. If non-dict object is passed in as the first parameter, a TypeError will be raised. To fix this error, we just need to add a parameter called “safe” to False in the method call JsonResponse.

TypeError: In order to allow non-dict objects to be serialized set the safe parameter to False

This is the fix:

return JsonResponse(["a", "b", 1, 2], safe=False)

The safe boolean parameter defaults is True. If it’s set to False, any object can be passed for serialization (otherwise only dict instances are allowed).

Example non-dict object:

some_object = [{‘pk’: 86, “model”: “machine_models.machinemodel”, “notes”: “This is warehouse imported machine.”}]

return JsonResponse(some_object,safe=False)


A complete sample:

from django.http import JsonResponse

def home_details(req):
    response = {
        'id': 1,
        'address': '123 Main St., San Jose, CA 95111',
        'beds': 3,
        'baths': 2,
        'status': Sold
    return JsonResponse(response)

Django errors while working with components

1) OperationalError at /admin/csv_app/invoicefile/add/
no such table: csv_app_invoicefile
==>solve this error by cmd
makemigrations csv_app

2)System check identified no issues (0 silenced).
You have 6 unapplied migration(s). Your project may not work properly until you
apply the migrations for app(s): csv_app.
Run ‘python migrate’ to apply them.
July 13, 2021 – 14:55:01
Django version 3.2.5, using settings ‘proj3.settings’
Starting development server at
Quit the server with CTRL-BREAK.

==>to fix this error, go to cmd enter:
$python makemigrations csv_app
$python migrate
$py runserver

3)os.path.join(BASE_DIR, ‘static’),
NameError: name ‘os’ is not defined
==>add this line in
import os

Inner class Meta

In Django this class works like post_meta in WordPress. In Django, it acts as a configuration class and keeps the configuration data in one place. Class Meta is the place in your code logic where your model.fields MEET With your form.widgets. So under Class Meta() you create the link between your model’ fields and the different widgets you want to have in your form.
Model metadata is “anything that’s not a field”, such as ordering options (ordering), database table name (db_table), or human-readable singular and plural names (verbose_name and verbose_name_plural). None are required, and adding class Meta to a model is completely optional.
A complete list of all possible Meta options are in this document (
To override the database table name, use the db_table parameter in class Meta.
db_table = ‘”name_left_in_lowercase”‘
app_label = ‘myapp’
permissions (Defaults to (‘add’, ‘change’, ‘delete’, ‘view’)

OperationalError, no such column.

OperationalError at /orders/
no such column: orders.customer_id
Request Method: GET
Request URL: http://localhost:9000/orders/
Django Version: 3.1.2
Exception Type: OperationalError
Exception Value:
no such column: orders.customer_id
Exception Location: /Users/xxx/django/db/backends/sqlite3/ in execute, line 355
Python Executable: /Users/xxx/Programs/Python/Python38-32
Python Version: 3.8.1

You are trying to add a non-nullable field ‘customer_id’ to snippet without a default;
we can’t do that (the database needs something to populate existing rows).
Please select a fix:
1) Provide a one-off default now (will be set on all existing rows)
2) Quit, and let me add a default in

In Django 1.7, the functionality of an app was integrated directly into Django. When working with migrations, the process is a bit different.
Make changes to as usual.
Create a migration. This generates code to go from the current state to the next state of your model. This is done with the “makemigrations my-app-name” command. This command is smart enough to detect what has changed and will create a script to effect that change to your database.
Next, you apply that migration with “ migrate” command. This command applies all migrations in order.

Step 1: Delete all the migration records from your app’s migration directory. These are files named 0001_,0002_,0003_ etc. Be careful as to not delete the file.
Step 2 : Delete the db.sqlite3 file. It will be regenerated later.

Then run the following commands:

$python makemigrations your-app-name
$python migrate (new db.sqlite3 will be generated automatically)

Be sure to write the name of your app after makemigrations. You might have to create a superuser to access your database again. Do so by the following:

$python createsuperuser