tikservices/django-jet2

Next Generation of django-jet (Modern responsive template for the Django admin interface with improved functionality.)

django-jet2's Issues

it's not migrate well with nosql database

Whenever I migrate the jet.dashboard app

(main-venv) satya@satya:~/PycharmProjects/djangoProject/main_proj$ python manage.py migrate

Operations to perform:
Apply all migrations: admin, android_api, auth, contenttypes, jet, sessions
Running migrations:
Applying jet.0003_auto_20201228_1540...Not implemented alter command for SQL ALTER TABLE "jet_pinnedapplication" ALTER COLUMN "user_id" TYPE int
Traceback (most recent call last):
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/djongo/cursor.py", line 51, in execute
self.result = Query(
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/djongo/sql2mongo/query.py", line 784, in init
self._query = self.parse()
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/djongo/sql2mongo/query.py", line 876, in parse
raise e
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/djongo/sql2mongo/query.py", line 857, in parse
return handler(self, statement)
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/djongo/sql2mongo/query.py", line 889, in _alter
query = AlterQuery(self.db, self.connection_properties, sm, self._params)
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/djongo/sql2mongo/query.py", line 425, in init
super().init(*args)
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/djongo/sql2mongo/query.py", line 84, in init
super().init(*args)
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/djongo/sql2mongo/query.py", line 62, in init
self.parse()
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/djongo/sql2mongo/query.py", line 441, in parse
self._alter(statement)
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/djongo/sql2mongo/query.py", line 500, in _alter
raise SQLDecodeError(f'Unknown token: {tok}')
djongo.exceptions.SQLDecodeError:

    Keyword: Unknown token: TYPE
    Sub SQL: None
    FAILED SQL: ('ALTER TABLE "jet_pinnedapplication" ALTER COLUMN "user_id" TYPE int',)
    Params: ([],)
    Version: 1.3.6

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/django/db/backends/utils.py", line 84, in _execute
return self.cursor.execute(sql, params)
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/djongo/cursor.py", line 59, in execute
raise db_exe from e
djongo.database.DatabaseError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "manage.py", line 22, in
main()
File "manage.py", line 18, in main
execute_from_command_line(sys.argv)
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/django/core/management/init.py", line 419, in execute_from_command_line
utility.execute()
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/django/core/management/init.py", line 413, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/django/core/management/base.py", line 354, in run_from_argv
self.execute(*args, **cmd_options)
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/django/core/management/base.py", line 398, in execute
output = self.handle(*args, **options)
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/django/core/management/base.py", line 89, in wrapped
res = handle_func(*args, **kwargs)
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/django/core/management/commands/migrate.py", line 244, in handle
post_migrate_state = executor.migrate(
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/django/db/migrations/executor.py", line 117, in migrate
state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards
state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/django/db/migrations/executor.py", line 227, in apply_migration
state = migration.apply(state, schema_editor)
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/django/db/migrations/migration.py", line 126, in apply
operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/django/db/migrations/operations/fields.py", line 244, in database_forwards
schema_editor.alter_field(from_model, from_field, to_field)
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/django/db/backends/base/schema.py", line 608, in alter_field
self._alter_field(model, old_field, new_field, old_type, new_type,
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/django/db/backends/base/schema.py", line 765, in _alter_field
self.execute(
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/django/db/backends/base/schema.py", line 145, in execute
cursor.execute(sql, params)
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/django/db/backends/utils.py", line 98, in execute
return super().execute(sql, params)
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/django/db/backends/utils.py", line 66, in execute
return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/django/db/backends/utils.py", line 75, in _execute_with_wrappers
return executor(sql, params, many, context)
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/django/db/backends/utils.py", line 84, in _execute
return self.cursor.execute(sql, params)
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/django/db/utils.py", line 90, in exit
raise dj_exc_value.with_traceback(traceback) from exc_value
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/django/db/backends/utils.py", line 84, in _execute
return self.cursor.execute(sql, params)
File "/home/satya/PycharmProjects/djangoProject/main_proj/main-venv/lib/python3.8/site-packages/djongo/cursor.py", line 59, in execute
raise db_exe from e
django.db.utils.DatabaseError

Replace deprecated oauth2client on google_analytics.py

Continuation of the project

Hi,

I'd like to know if you're going to maintain this project over time, in the long term?

RemovedInDjango40Warning

For Django Version 4.0+

• RemovedInDjango40Warning: django.utils.translation.ugettext_lazy() is deprecated in favor of django.utils.translation.gettext_lazy().

Compatibility with Django 3.1

Hello,

thanks for maintaining django-jet2!

I'd like to report a compatibility issue I experienced upgrading a project to Django 3.1.
It looks like something goes wrong with fieldset rendering:

Django 3.0

Django 3.1

Any chance this can get fixed?

Please let me know if I can be of further help.

Thanks,

Fabio

Database to set

List Editable Visualization Problems

Visualization is broken when FK field is in list editable and widget is autocomplete

autocomplete_fields broken on m2m fields

It looks like the autocomplete in the django admin is broken when using jet. What you type does not filter the options and whatever you type you always get all the possibile entries without filtering.

Widget rendering is broken too:

Django:

with jet2:

django-jet2 is 1.0.12, Django is 3.0.8.

Snippet:

models.py:

class MyModel(models.Model):
    myfield = models.ManyToManyField(...)

admin.py

class MyAdmin(admin.ModelAdmin):
    autocomplete_fields = ['myfield']

View permissions aren't clickeable on sidebar

When i assing view permission to my users i am not able to click the model button on the sidebar. But when i assign change permission it works.

It should be available for view ones, due to i only want that those users only see the info and not edit it

Initial Update

The bot created this issue to inform you that pyup.io has been set up on this repo.
Once you have closed it, the bot will open pull requests for updates as soon as they are available.

Inline create, edit and delete icons not working

The „inline create, edit and delete“ icons do not work in Chrome and Firefox.

It says connection refused.

Can you fix this or is it possible to hide the inline edit icons?

Paginator in admin not correct

Hi,
I've recently installed django-jet2 after upgrading django from version 1.11 and it works perfectly except for one detail.

In change view of a model, if there's an high number of pages, the paginator is messed up as you can see in the screenshot attached.

Instead of showing the last page it shows the last two pages number without any style.

Thanks