An administration website for Django

It appears something broke the JS in the master branch with Django 1.5. None of the admin js is working. All the js files are being served.

Uncaught ReferenceError: yawdadmin is not defined select2.min.js:488 Uncaught ReferenceError: yawdadmin is not defined localhost:26 Uncaught ReferenceError: yawdadmin is not defined localhost:33 Uncaught ReferenceError: yawdadmin is not defined actions.js:139

You have it as Django Administration in admin/includes/topnav.html

This should be customizable with a setting attribute or something. It's a fairly large template so overriding it locally would likely be a pain to maintain.

You define a form https://github.com/yawd/yawd-admin/blob/master/yawdadmin/forms.py that has fields hard coded. This can't be for custom user models as the fields may not exist. By defining this Django errors on basics like syncdb or shell.

Hello,

I just installed yawd-admin and it's very nice (thanks for the work!).

I've a problem with the fancy box and the raw_id_fields.

When I click on the magnifiying glass next to a raw_id_field, this open the fancybox but I can't select directly the object that I want to populate the raw_id_field with the object id.

Thanks for looking at this "problem"

We are working with yawd-admin v0.7.0 and django-1.5.2. When we try to add a new user, we see the edition form instead of the add form. Another problem we found is that the password input in the html is not of type password as it should be. More on this, is that when we try to save the changes, the password is not encrypted.

I think it would be a really good idea to namespace the static files since you modify bootstrap.min.js and I may want a different version for my front end. Something like {{ STATIC_URL }}yawd/js/bootstrap.min.js

As it stands now if I call in js/bootstrap.min.js I get yours. If I override it I loose the admin skin.

Hello!

One question, my application needs a PopupModelAdmin) inside another PopupModelAdmin) and i have this:

This is good anyway, but the clean solution would be like modal_size = '900:300px' or something better i guess... Ouch! In this case CKEditor does not show the entire on modal.

What do you think? Is there anything that can help me?

Django Version: 1.4.2 Exception Type: KeyError Exception Value: 'rows' Exception Location: /yawdadmin/utils.py in get_analytics_data, line 98

As the title says, this happens when you add a property which has no visitor tracking data yet (api doesn't return what is expected).

A user should be able to edit his own "Personal Information" (first name, last name etc) even if he has no permissions to edit or view other users. This is not possible with the original django admin, neither with yawd-admin so far, but in real-world apps it's a must-have feature. A new view should be implemented and added to the top-right drop-down menu, above the 'Change password' link.

Hi, when i run collectstatic in django 1.6 this fails, this says

Post-processing 'yawd-admin/css/admin.css' failed!

raise processed ValueError: The file 'yawd-admin/img/gcons/cassete.png' could not be found with <pipeline.storage.PipelineCachedStorage object at 0xa4b5c2c>.

i used django-pipeline, django1.6.x and yawd-admin 0.7.0 is normal the file or imagen cassete.png no exist???

Cheers

The export does not respect filter. The template admin/import_export/export.html has to be changed.

Replace line 18 by this :

As the project seems unmaintained, i forked it and updated it.

As, i did not have any news about the repo owner, I will rename it yawd-admin2 in the future to get an official fork available in pypi.

This is the repo : https://github.com/mwolff44/yawd-admin

Hi there, firstly: great project!

I have a problem using (i.e. editing, updating) models with Yawd-Admin (0.7.0) on Python 2.7.8 when applying modal = True in my Inline Django Admin classes using the Django Proxy model for User Profiles.

Using the following as simplified case (settings.py excluded, as well as INSTALLED_APPS, and associated imports):

# app_name/admin.py
class UserProfileInline(admin.StackedInline):
    model = UserProfile
    max_num = 1
    can_delete = False
    modal = True # This causes the error

class UserProfileAdmin(UserAdmin):
    inlines = (UserProfileInline, )

admin.site.unregister(User)
admin.site.register(User, UserProfileAdmin)

admin.autodiscover()
admin_site._registry.update(admin.site._registry)


# app_name/models.py
class UserProfile(models.Model):
    user = models.OneToOneField(User)
    website = models.URLField(blank=True)

I obtain the following error creating / editing a user (e.g.):

MultiValueDictKeyError at /admin/auth/user/3/ "u'userprofile-0-id'"

Since this inline is now associated with User, the extraneous information (website in this example) shows up as a Profile heading in the same page when creating a user (which is expected behavior). If this information (i.e. website) is added, and then saved; on the next page (the edit page), and a save is attempted, you obtain that error. This also occurs when you attempt to edit such a post. The only time you have a successful user creation / edit occurs when you don't modify any info in the class where modal = True is present.

Also, because of the first save when creating a user, the user is added (in the default django auth tables), regardless of the success of entry of extra information via modal = True.

I've looked quite deeply in the Yawd-Admin source, and for the life of me I cannot find why this information isn't passed correctly.

Furthermore, having tried a number of combinations, it seems to be a Yawd-Admin problem with how modal = True loads and passes the information - as the default Django admin has no problem with this. And, when modal isn't present, everything works perfectly as in the default Django admin.

UPDATE: The problem occurs even without modal = True if one follows the sequence: add extra info, and then modify it. It seems to be Yawd-Admin related as django-admin-bootstrap3 has no issues with it - as does the default Django admin site.

I would appreciate any insight anyone can offer on this, please.

Many thanks!

oauth2client doesn't have support for Python3, since that package is only required for the Google Analytics part, shouldn't it be optional like the google-api-python-client?

Currently the oauth2client requirement is preventing to set up yawd admin in any Python 3 projects.

Using url(r'^', include(admin_site.urls)) makes the admin panel to appear on the root url.

However,

When typing 1 segment aside the root url that doesn't exist. It generates an 500 KeyError, not a 404 Page not Found.

How to reproduce on the example site: 1 ) login demo/demo 2 ) go to http://yawd-admin.yawd.eu/ueoue/

This only happens with unknown urls that have 1 segment and no special characters.