ubernostrum - Project Hosting on Google Code

User Profile		Updates

Earlier this year Oct 14, 2009 django-registration issue 125 (Suggestions for documentation) commented on - Please see the notice on the main project page indicating that django-registration's hosting has moved. No further tickets or comments should be posted here. Please see the notice on the main project page indicating that django-registration's hosting has moved. No further tickets or comments should be posted here. Oct 12, 2009 django-registration issue 144 (unused variable in models.py) Status changed - 1) No, it's not; you should read up on Django a bit more. 2) The homepage for this project clearly tells you that it's moved to being hosted at Bitbucket, so you shouldn't be filing issues here. Status: Invalid 1) No, it's not; you should read up on Django a bit more. 2) The homepage for this project clearly tells you that it's moved to being hosted at Bitbucket, so you shouldn't be filing issues here. Status: Invalid Jul 26, 2009 pygowave-server issue 24 (Licensing) reported - I hate to be that guy, but I can't find a copy of the django-registration license notice in here, which is required by the BSD terms. Also, ideally you'd just document it as a dependency or use something like a pip requirements file to have it pulled automatically for you; then you wouldn't need to bundle or worry about attribution at all :) I hate to be that guy, but I can't find a copy of the django-registration license notice in here, which is required by the BSD terms. Also, ideally you'd just document it as a dependency or use something like a pip requirements file to have it pulled automatically for you; then you wouldn't need to bundle or worry about attribution at all :) Jul 08, 2009 django-registration issue 143 (Add mechanism to allow subclassed User models) changed - As should be clear from the home page here, this is not the appropriate place for this ticket. Status: Invalid Labels: −Type-Defect −Priority-Medium As should be clear from the home page here, this is not the appropriate place for this ticket. Status: Invalid Labels: −Type-Defect −Priority-Medium Jun 20, 2009 ibm-db issue 27 (Test DB creation in Django backend should respect verbosity) reported - The methods create_test_db and destroy_test_db of DatabaseCreation in ibm_db_django/django/db/backends/db2/creation.py always print messages to stdout, which can cause problems in applications which perform scripted calls to management commands in environments where doing so is either undesired or forbidden (e.g., WSGI restricts access to stdout). To resolve this, these methods should only print messages when the "verbosity" argument is 1 or greater, per Django's documentation: http://docs.djangoproject.com/en/dev/ref/django-admin/#django-admin-verbosity The methods create_test_db and destroy_test_db of DatabaseCreation in ibm_db_django/django/db/backends/db2/creation.py always print messages to stdout, which can cause problems in applications which perform scripted calls to management commands in environments where doing so is either undesired or forbidden (e.g., WSGI restricts access to stdout). To resolve this, these methods should only print messages when the "verbosity" argument is 1 or greater, per Django's documentation: http://docs.djangoproject.com/en/dev/ref/django-admin/#django-admin-verbosity Jun 20, 2009 ibm-db issue 26 (Do not require installation into django.db for Django backen...) reported - django.db is not a setuptools namespace package, so installation of the Django backend is likely to be problematic. At any rate, Django can use database backends from any location on the Python path (DATABASE_ENGINE can be either the name of a bundled backend, or a dotted Python module path to a third-party backend), specifically to enable the use of third-party backends. django.db is not a setuptools namespace package, so installation of the Django backend is likely to be problematic. At any rate, Django can use database backends from any location on the Python path (DATABASE_ENGINE can be either the name of a bundled backend, or a dotted Python module path to a third-party backend), specifically to enable the use of third-party backends. Jun 20, 2009 ibm-db issue 25 (Django backend sequence reset likely to fail in real-world s...) reported - The implementation of sequence_reset_sql() in ibm_db_django/django/db/backends/db2/operations.py is extremely fragile. It assumes that fewer than 10,000 sequential values have been used from the sequence, which is highly likely to fail on real-world installations. For a better implementation, consult the existing Django backends for PostgreSQL and Oracle, both of which select the maximum value in use and increment it to obtain an unused value to reset the sequence. The implementation of sequence_reset_sql() in ibm_db_django/django/db/backends/db2/operations.py is extremely fragile. It assumes that fewer than 10,000 sequential values have been used from the sequence, which is highly likely to fail on real-world installations. For a better implementation, consult the existing Django backends for PostgreSQL and Oracle, both of which select the maximum value in use and increment it to obtain an unused value to reset the sequence. May 20, 2009 django-registration issue 142 (Sha check for 2.6 patch) Status changed - Please look at the main page for this project. Status: Invalid Please look at the main page for this project. Status: Invalid Feb 16, 2009 django-registration issue 141 (Confirmation mail is not going) Status changed - This is not a support forum. This is a bug tracker (and in fact the real bug tracker has moved elsewhere, as you'd know if you looked at the main page for this application). Since no-one else is reporting that email sending doesn't work (including the many sites on which I personally use this application in production), this is not a bug. The application works as advertised; most likely something is wrong with either your setup or with your understanding of Django or of this application. But it will be up to you, personally, to work out the problem, perhaps with the assistance of a real support forum. Status: Invalid This is not a support forum. This is a bug tracker (and in fact the real bug tracker has moved elsewhere, as you'd know if you looked at the main page for this application). Since no-one else is reporting that email sending doesn't work (including the many sites on which I personally use this application in production), this is not a bug. The application works as advertised; most likely something is wrong with either your setup or with your understanding of Django or of this application. But it will be up to you, personally, to work out the problem, perhaps with the assistance of a real support forum. Status: Invalid Jan 30, 2009 django-comment-utils issue 37 (Comment moderation does not work with django 1.0) Status changed - The guy who did the refactored django.contrib.comments for Django 1.0 is incorporating comment-utils' moderation features directly into Django for 1.1. As a result, there's not much need for this project, or for forks of it. Status: Invalid The guy who did the refactored django.contrib.comments for Django 1.0 is incorporating comment-utils' moderation features directly into Django for 1.1. As a result, there's not much need for this project, or for forks of it. Status: Invalid Jan 27, 2009 django-registration issue 127 (Adding First Name / Last Name do registration) commented on - This is not the correct place to file this request. This is not the correct place to file this request. Jan 27, 2009 django-registration issue 139 (Login Functionality) Status changed - This is not the correct place to file this request. Status: Invalid This is not the correct place to file this request. Status: Invalid Older Nov 20, 2008 django-contact-form issue 18 (specifying form_class variable in url.py is insufficient) Status changed - I don't see how this is a bug; if you're doing custom stuff, it's to be expected that you'll need to ensure anything you use is imported. Perhaps the problem is that you're editing the provided default URLConf when you really ought to just set up your own. Status: Invalid I don't see how this is a bug; if you're doing custom stuff, it's to be expected that you'll need to ensure anything you use is imported. Perhaps the problem is that you're editing the provided default URLConf when you really ought to just set up your own. Status: Invalid Nov 11, 2008 django-registration issue 138 (django-registration email configuration using starttls) Status changed - This is a Django/email issue and not in any way specific to this application. Status: Invalid This is a Django/email issue and not in any way specific to this application. Status: Invalid Nov 11, 2008 django-registration issue 137 (delete_expired_users is removing many users) Status changed - If you're using the automated expired-user deletion, you must either: * Manually delete the RegistrationProfile for a user who you wish to set inactive, or * Not set users inactive unless you want them to be deleted. The django-registration documentation covers this, and it is intended behavior. Status: Invalid If you're using the automated expired-user deletion, you must either: * Manually delete the RegistrationProfile for a user who you wish to set inactive, or * Not set users inactive unless you want them to be deleted. The django-registration documentation covers this, and it is intended behavior. Status: Invalid Nov 06, 2008 django-profiles issue 9 (success messages) Status changed - This ticket has been migrated to django-profiles' new issue tracker: http://www.bitbucket.org/ubernostrum/django-profiles/issue/1/create-auth-messages-on-profile-events Status: Duplicate This ticket has been migrated to django-profiles' new issue tracker: http://www.bitbucket.org/ubernostrum/django-profiles/issue/1/create-auth-messages-on-profile-events Status: Duplicate Nov 06, 2008 django-profiles issue 3 (how to order by) Status changed - The (belated) answer to this is to make sure that the default ordering of your profile model is the ordering you'll want. Status: Invalid The (belated) answer to this is to make sure that the default ordering of your profile model is the ordering you'll want. Status: Invalid Nov 06, 2008 django-profiles issue 12 (AttributeError at /profiles/create/ ) Status changed - This typically means you have not set AUTH_PROFILE_MODULE, or have set it incorrectly. Consult the documentation for details. Status: Invalid This typically means you have not set AUTH_PROFILE_MODULE, or have set it incorrectly. Consult the documentation for details. Status: Invalid Nov 06, 2008 django-registration issue 114 (Need to capitalize form labels) Status changed - This ticket has been migrated to django-registration's new issue tracker: http://www.bitbucket.org/ubernostrum/django-registration/issue/2/capitalize-form-labels Status: Duplicate This ticket has been migrated to django-registration's new issue tracker: http://www.bitbucket.org/ubernostrum/django-registration/issue/2/capitalize-form-labels Status: Duplicate Nov 06, 2008 django-registration issue 132 (accept template_loader as param in views) Status changed - Status: Duplicate Status: Duplicate Nov 06, 2008 django-registration issue 132 (accept template_loader as param in views) Status changed - This ticket has been migrated to django-registration's new issue tracker: http://www.bitbucket.org/ubernostrum/django-registration/issue/1/accept-template_loader-in-views Status: Invalid This ticket has been migrated to django-registration's new issue tracker: http://www.bitbucket.org/ubernostrum/django-registration/issue/1/accept-template_loader-in-views Status: Invalid Nov 06, 2008 django-registration issue 116 (Refactor activation email to RegistrationProfile method for ...) Status changed - There are a couple of apps already out there doing generic email/reminder/confirmation functionality; what django-registration currently does is fine for the default case, and for extensive customization of email behavior you should probably be looking to plug in something designed for that rather than rewrite django-registration. Status: WontFix There are a couple of apps already out there doing generic email/reminder/confirmation functionality; what django-registration currently does is fine for the default case, and for extensive customization of email behavior you should probably be looking to plug in something designed for that rather than rewrite django-registration. Status: WontFix Nov 06, 2008 django-registration issue 125 (Suggestions for documentation) Status changed - The 0.7 docs cleaned up the explanation of what the email templates use, but other than that django- registration is mostly following the lead of Django itself; sooner or later I need to be able to assume that someone using django-registration is familiar enough with Django to, e.g., know how to work with a form object in a template. But if you've got further suggestions on how to walk the line between being helpful and duplicating Django's own docs, you've got my email address :) Status: WontFix The 0.7 docs cleaned up the explanation of what the email templates use, but other than that django- registration is mostly following the lead of Django itself; sooner or later I need to be able to assume that someone using django-registration is familiar enough with Django to, e.g., know how to work with a form object in a template. But if you've got further suggestions on how to walk the line between being helpful and duplicating Django's own docs, you've got my email address :) Status: WontFix Nov 06, 2008 django-registration issue 133 (New release compliant with django 1.0) Status changed - django-registration has moved off Google Code, so information about the latest release (0.7, which works on Django 1.0) is available at the new project page: http://www.bitbucket.org/ubernostrum/django-registration/ Status: Fixed django-registration has moved off Google Code, so information about the latest release (0.7, which works on Django 1.0) is available at the new project page: http://www.bitbucket.org/ubernostrum/django-registration/ Status: Fixed

issue 141 (Confirmation mail is not going) Status changed - This is not a support forum. This is a bug tracker (and in fact the real bug tracker has moved elsewhere, as you'd know if you looked at the main page for this application). Since no-one else is reporting that email sending doesn't work (including the many sites on which I personally use this application in production), this is not a bug. The application works as advertised; most likely something is wrong with either your setup or with your understanding of Django or of this application. But it will be up to you, personally, to work out the problem, perhaps with the assistance of a real support forum.

Status: Invalid

This is not a support forum. This is a bug tracker (and in fact the real bug tracker has moved elsewhere, as you'd know if you looked at the main page for this application). Since no-one else is reporting that email sending doesn't work (including the many sites on which I personally use this application in production), this is not a bug. The application works as advertised; most likely something is wrong with either your setup or with your understanding of Django or of this application. But it will be up to you, personally, to work out the problem, perhaps with the assistance of a real support forum.

Status: Invalid

Earlier this year

Older