Expand FlatPage admin interface.

I am learning Django using the book "Practical Django Project". This isn't such an old book but seems to be very out-dated in terms of django. it Uses the old admin interface which I assume was replaced in version 1.0.

 

To make a long story short, one of the example of the book is to add a keyword items to a flatpage model. this is done by doing somthing like that :

page = models.ForeignKey(FlatPage, edit_inline=models.STACKED,....)

 

Now, I am trying to do the same using the new admin interface but with no luck. I can use admin.StackedInline but how do I associate it with the flatpage model ?

 

Hope I am clear here.

 

Thanks,

Elad

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

Re: Unable to display static content.

Are you sure you read this?:
https://docs.djangoproject.com/en/1.3/ref/contrib/staticfiles/

From my own experience, storing my static files in '/static/' never
works so I always create a separate folder for my static files and add
the path to STATICFILES_DIRS in my settings.

On 1/1/12, Chirdeep <chirdeep.tomar@gmail.com> wrote:
> Now I have changed the project structure to
>
> Project
> -webApp
> ---static
> -----images
> -----stylesheets
> -----index.html
> ---templates
>
> I can browse to index.html inside static folder.
>
> http://127.0.0.1:8000/static/index.html
>
> For some reason, its adding the search-form to the URL for loading CSS
> and Images when I browse to http://127.0.0.1:8000/search-form/
>
> Firebug shows :
> http://127.0.0.1:8000/search-form/common.css
>
> Obviously then it won't find the resources.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>

--
Sent from my mobile device

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

Re: User-set domain-prefixes, i.e. myname.googlegroups.com

Hello Alec Taylor,

I've done something like this at one of my websites.

The basic steps I use are gather the info in a form.

On form submit the info goes into a website registration database and the user is sent a website creation confirmation email.

The user receives the email and clicks on the supplied confirmation link.

The user is informed that they will receive an email when their website has been created.

(The above should be familiar to those of you that have used James Bennett's django-registration.  It's basically the same mechanics but applied to website registration/creation.)

A cron job triggers once a minute and scans the website registration database, creating any confirmed pending website registration requests.

The cron job sets up a django environment and calls a series of custom django-admin commands that creates databases, django projects, apache configs, etc.

The DNS config for the domain is given a wildcard (*.googlegroups.com) address record and Apache is used to redirect to a default domain for any domain that isn't picked up by Apache's config files.

Toodle-looooooooooooooooooo............
creecode

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/0VvJsoARllkJ.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

Re: "1054 unknown column..." in MySql5

Its not a mysql problem but you really have to give a better
description of the problem so you can get quick and useful replies to
your question.

However:
Have you snycdb-ed?
Also, did you remove or add an attribute from a model class after
syncdb-ing? If you did, you have to manually drop the table and syncdb
again.

On 1/1/12, James Jang <jjangdm@gmail.com> wrote:
> Hi,
> I hope I get your good helps or advises.
>
> MY SYSTEM : win7, python2.6, django-1.3.1, using development
> server(django), MySql5
>
> After making model class, "1054 unknown column...in field list."
> message is shown in admin page.
>
> Is this a MySql version issue? or?
>
> Thanks any.
>
>
> Happy New Year~
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>

--
Sent from my mobile device

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

Re: Unable to display static content.

Now I have changed the project structure to

Project
-webApp
---static
-----images
-----stylesheets
-----index.html
---templates

I can browse to index.html inside static folder.

http://127.0.0.1:8000/static/index.html

For some reason, its adding the search-form to the URL for loading CSS
and Images when I browse to http://127.0.0.1:8000/search-form/

Firebug shows :
http://127.0.0.1:8000/search-form/common.css

Obviously then it won't find the resources.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

Re: Django dev/deploy environment for distributed agile teams

Hello Ashkan,

Gunicorn can handle async from what I read < http://gunicorn.org/design.html >.  From the docs...

Sync Workers

The most basic and the default worker type is a synchronous worker class that handles a single request at a time. This model is the simplest to reason about as any errors will affect at most a single request. Though as we describe below only processing a single request at a time requires some assumptions about how applications are programmed.

Async Workers

The asynchronous workers available are based on Greenlets (via Eventlet and Gevent). Greenlets are an implementation of cooperative multi-threading for Python. In general, an application should be able to make use of these worker classes with no changes.

Tornado Workers

There's also a Tornado worker class. It can be used to write applications using the Tornado framework. Although the Tornado workers are capable of serving a WSGI application, this is not a recommended configuration.

Of course there may be other technical reason to not use Gunicorn but if you're looking for something that eases deployment, give it a go!

Toodle-loooooooooooo..........
creecode

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/otf8gw9roOMJ.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

Re: Happy new year

+1

On Sun, Jan 1, 2012 at 8:28 PM, Cal Leeming [Simplicity Media Ltd] <cal.leeming@simplicitymedialtd.co.uk> wrote:

Happy new year everyone :)

Lets hope 2012 is a great year for Django!!

On Sun, Jan 1, 2012 at 8:58 AM, Daniel Ngarambe <dngarz@gmail.com> wrote:

Hello Geeks,

I wish you all a happy mew year.

DNSr.

Sent from Samsung Galaxy S

On 1 Jan 2012 08:24, "girish shabadimath" <girishmss.1203@gmail.com> wrote:

New year wishes to everyone,,

regards,
girish ms
On Sun, Jan 1, 2012 at 10:24 AM, Nikhil Verma <varma.nikhil22@gmail.com> wrote:

Happy new year to all of you.

On Sun, Jan 1, 2012 at 10:22 AM, yati sagade <yati.sagade@gmail.com> wrote:

Happy new year all :)

On Sun, Jan 1, 2012 at 7:54 AM, Adrien Lemaire <adrien.lemaire@aquasys.co.jp> wrote:

Happy new year dear folks !

On Jan 1, 1:48 am, Sławomir Zborowski <stilew...@gmail.com> wrote:
> Happy new year, Django users :-) !

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

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

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

--
Girish M S

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.