django admin with mongodb - django

I'm currently struggling with django admin and mongodb, I found some solutions about combining django admin and mongodb, but none of them is perfectly integrated with django admin. What I need is that I can do CRUD to mongodb tables in admin site like I use MySQL.
mongonaut : besides mapping to mongodb tables, mongonaut has permissions to do CRUD, but I don't know how to integreted mongonaut into django admin index page, mongonaut has its own page and css style to do CRUD.
mongoadmin : lack of permissions management is why I skipped it.
I am new to django,could anyone tell me what is your solution to integrated django admin and mongodb, thanks a lot !

Related

Why django_admin_log table is empty in Django Rest Framework

I am developing a web application where I'm using Django 2.0.8 and Django Rest Framework to build a RESTful API. I have build some endpoint for basic CRUD operations. The problem is now I am trying to view log to my admin Dashboard. (Custom Admin Panel). But when I browsed my Database (PostgreSQL), I found that I have django_admin_log table but it is totally empty. But I created some object with those endpoints. Doesn't Django keep logs of user's activities by default? Or am I missing something?
PS: I was authenticated while creating those objects
django_admin_log table
Django logs actions done only via the Admin Panel. You can create custom logic to create records in the admin log table using the LogEntry model from django.contrib.admin.models.

Django 2.0 upgrade caused Wagtail (2.1) admin to disappear.

I was in the process of upgrading my wagtail app to Django 2.0. After resolving the on-delete errors I thought I had a working app until I went to the /admin page. The standard Wagtail admin interface has disappeared and has been replaced by the default Django admin interface. Can anyone help?
https://github.com/timcknowles/wagtailcmsdemo/tree/django2
Many thanks in advance
Your urls.py has the Django admin before the Wagtail admin, so the Django admin "wins out".
Swap the order of those two, or maybe rename the Django admin prefix to ^djangoadmin/.

Adding Django CMS to an existing Django site. Can it damage the existing site and data?

A friend asked if they could/update their existing site to Django CMS
It has a n e-commerce section added to it and apparently uses the Maris DB.
He wants to use Django CMS mostly to easily add articles and other content.
How intrusive or dangerous is it to install Django CMS to an already existing Django site especially it's customized existing e-commerce section?
Thank you.

Should I use the Django admin for user submitted content?

I'm creating a site that will allow users to authenticate via Facebook and create content.
Should I use the Django admin interface for content creation or would it be smarter to create my own interface. If I should roll my own are there any good tutorials about this?
You can use admin login page and with custom URL redirection. Here is the working example for facebook authentication.
https://github.com/sivaa/django-social-auth-facebook
As a general rule, the django admin is best for validating your models during development and testing; and should not be used as a front end user interface.
Since each site/application has their own unique requirements, it is difficult to recommend a tutorial. Once you are familiar with django, you will find the following libraries helpful:
django-bootstrap-toolkit - this integrates the the excellent bootstrap css/javascript framework in django.
django-social-auth - allows your users to login using their social network credentials.
pinax project - a collection of common utilities for developing just about any kind of front end website.
For customizing the existing admin application:
grappelli - a custom skin for the admin
django-frontendadmin - edit models in the front end using template tags
django-admin-tools - customized widgets and UI elements for the admin application

Where is Django's admin read-only permission for models?

I've read at How can I MODIFY django to create "view" permission? that Django 1.2 cames with a read-only permission for admin models. Where I set this option? It's not found as a permission in the auth app.
Thanks
You need to follow the steps outlined in the linked answer. The 1.2 feature mentioned in the article concerns adding the editable=False option to a model's field which renders the field non-editable in the admin interface for all users.
If you really are missing this functionality i suggest opening a ticket on the django support site to have this fix added to django however remember that the django admin site is for ADMINS. It is not designed to be used as A CRUD interface for all users, just an administrative interface for diving into the data and editing it in place. It's only over time that people have been adding more and more User friendly enhancements to it.