I am trying to use django-treebeard in the admin.

Hello,

hi

I have tried extending django registration page with little progress.
I can now add new user from the admin but cannot do that on the 
front end. the problem is that the url does not display the from,
but raises exception, "the page cannot be found". Do I need to create a view.py

I have created my tree structure, now I am trying to create a form that selects a node which I will use to do some operations.

Hello Guys


I want to make the urls dynamic and change according to roles in the project for every app.
Example if there is role x so it should change like x/manage/view_name() , if the role is admin the urls will become  /admin/manage/view_name().

So basically i want to know how can i access request variable from middlewares into my main project urls.
I know how to access template context processors but want  to  learn how to access request in urls.

This is what i have written
 
url_variable = 'corporate'

for app_name in settings.INSTALLED_APPS:
    if not app_name in excluded_apps:
        app = get_app(app_name)

        #-----------------------------------------------------------------------
        # Per module url
        #-----------------------------------------------------------------------
        for model in get_models(app):
            model = model._meta.module_name[5:]
            url_path = r"^manage/%s/?$" % (model.lower())
            view_name = "admin_manage_%s" % (model.lower())
            urlpatterns += patterns('project_name.%s.views' % app_name,
                                      url(url_path, view_name, name=view_name),)

Thanks in advance

--
Regards
Nikhil Verma
+91-958-273-3156

I've been reading up on how transactions work in Django 1.5 and how they will work in 1.6. I think I have a grasp of things, but I wanted to reach out on here to just check that my understanding of things is correct, and ask a question or two.

Django 1.5:

• The database-level auto-commit is turned OFF.
• SQL standards dictate that every query opens a transaction if one does not already exist. This happens regardless of the database's auto-commit setting.
• After each Django ORM operation (read or write), Django commits this open transaction. This emulates the database-level auto-commit.
• Transaction decorators cannot be nested. When one is opened, any previous transaction will be committed.
• When executing raw SQL (with a database cursor), Django marks the current transaction as dirty but does not issue a commit. If data changes were made then they need manually committing. Why do the docs say that you only need to commit the change if data was changed? If the transaction is marked as dirty regardless of a read or a write, would it not always need committing or rolling back to ensure the transaction is properly closed by the end of the connection?
• Setting TRANSACTIONS_MANAGED to True stops Django from sending any commits after ORM operations. The database-level auto-commit is still disabled. With this setting, using any Django ORM read or write operation (all wrapped in `transaction.commit_on_success`) fails with TransactionManagementError('This code isn't under transaction management'). Is this expected?

Django 1.6:

• The database-level auto-commit is turned ON.
• Every database operation via the ORM will be committed using the database's auto-commit, including any custom SQL executed with the database cursor.
• The `atomic` decorator / context manager either starts a new transaction, or creates a new savepoint if it's nested within an existing transaction. They are committed as long as no exception is raised.
• If ATOMIC_REQUESTS is specified in the database config, all views are wrapped in `atomic`, unless it's wrapped in `non_atomic_requests`.
• If you set AUTOCOMMIT to False in a database configuration, this will disable the database-level auto-commit. All DB reads and writes will need manually wrapping in transactions. The docs say that with this disabled, Django won't perform any commits. Does this mean that the `atomic` decorator won't work properly and you have to use the underlying database library to handle transactions? In 1.6 it would appear that Django never performs a commit outside of `atomic`, so I'm confused by this comment!

I'd really appreciate any information if some of what I understand to be true is not accurate.

Many thanks!

Hello,

I am fairly new to both django, so please excuse this question if there is a doc I missed somewhere that answers it...  Anyhow, I'm planning on moving a large drupal site into django.  Currently the site - yinyanghouse.com - has more or less static content, dynamic community submitted content and some ecommerce functionality.  I'm considering moving the site into three domains to ease some aspects of administration and also give us the future possibilities of moving some parts into other systems - like the static parts into a static site generator and the store into a 3rd party system - for example.

So we would have www.yinyanghouse.com, store.yinyanghouse.com, community.yinyanghouse.com .

Now my question is that we currently have data queries that are important to the site that would then encompass the three subdomains.  I've read a little on the django "sites" framework, but it wasn't clear if you could perhaps share a category between all 3 subdomains, for example, and allow you to display data from one site on another site.  For example, we currently have a "conditions" meta-page say "low back pain" and this pulls in information from all over including related products from our store, related acupuncture points from our static collection of information, etc.  So in that case community.yinyanghouse.com/conditions/low-back-pain would pull in products from store.yinyanghouse.com tagged with "low back pain" in the conditions category as well as acupuncture points from www.yinyanghouse.com tagged with "low back pain".

Is this possible?  Is it too much work for the benefits we would get in clearer layouts between sites, probably better caching prospects, etc.?

Thanks for any ideas/feedback you can offer!
-Chad.

Hello, is there a way to get a Custom Label for a RadioSelect() widget?

I have a Model and wanted to get a label like:

'<label for="id_customer_0">
<input type="radio" value="1" name="customer" id="id_customer_0">
{{ customer.name }}
{{ customer.address.city }}
{{ customer.address.zip }}
</label>'

Is there a way to get certain output?
I heard about the RadioSelect Renderer but i can only access the __unicode__ output i definied for the model. Is there a better / other way to implement such functionallity?