Thursday, July 1, 2010

Looking for Django Developer(s) in Long Island for part time and full time

Hello Django User group...

I am looking on the site for how to post a job opening to your
community...and I apologize in advance if I am not doing the right.

We are looking for 1 or 2 local (NY Metro area - preferably Long
Island) Django developers to work with me on a new audible Tweet
platform we developed called http://ShoutOmatic.com

If you, or anyone you know is looking for part time or full time work
please contact me normlevy @ shoutomatic <dot> com

We are an exciting start-up and build our platforms with Django...

Thank you for any guidance you may have for us to find Django
developers

Norm Levy
ShoutOmatic

--
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.

Admin datetime js widget and urls

Hello all,
I am trying to leverage the Admin site by adding some urls in the
admin class.

Eg.
class Orders(admin.ModelAdmin):
def changelist_view(self,request,customer_id=None):
pass
#set up view for order list based on customer_id by adding
filter to queryset

def get_urls(self):
urls = patterns('',
(r'customer/(?P<customer_id>)/',self.changelist_view),
)
return urls + admin.ModelAdmin.get_urls(self)

This allows a url like
/admin/customers/orders/customer/1/ to access the orders for customer
with id of 1.

This works wonderfully as it allows me to be at the Customer "level"
in regards to their orders (for all functions, viewing list, changing
orders or adding. I always know the customer).

The problem is that when I do this I know longer have the Admin
datetime js widgets and can't seem to get them back. If I access the
admin through the normal url (eg. /admin/customers/orders/ ) they
appear.

Any ideas, please?
Much thanks in advance.

Chris

--
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: Newby Question: template system doesn't render form html

You dont seem to be closing your input tags, add > to the end of them

On Jul 1, 4:47 am, Gene <kaching1...@gmail.com> wrote:
> When I put a form into my template it comes back blank. Does anyone
> know why?
>
> what is in my template
>
> <form action="/in/" method="post">
>
>     <input type="text" name="username" id="Username" value="Username" /
>
>     <input type="text" name="password" id="Password" value="Password" /
>
> <input type="submit" value="Vote" />
> </form>
>
> what I get in my browser
>
> <Text Node: '<form action="/in/" metho'>

--
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.

Managing the balance between SSL and impact on the server

I have an extranet for staff and known partners. It has absolutely no
public content. I've installed SSL so it should be secure, but I also
heard that SSL can have a big impact on the server.

While login and password changes need to be secure, the content itself
is not particularly sensitive. But actions and views will be user
specific, therefore users will need to be logged in at all times.

Given the above, I was wondering if it is necessary to use SSL at all
times or is possible to use it only for login? Presumably if I dropped
out of SSL after login, the cookies would still be vulnerable to
hijacking. My gut feel is that I have to use SSL all the time and just
accept the hit on the server, but I wondered there were any django
tools (CSRF protection) or best practices anyone has on managing the
balance of SSL and the impact on the server.

- Are they passing logins and passowords? Yes, then SSL
- Is the content sensitive (like bank details or commercial stuff) ?
If yes then SSL.
- Are the content and actions user specific? If yes then SSL.

ALJ

--
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.

best translation solution for my project

Hi,

Sorry if this has been asked before, but i only seem to be finding
bit's and pieces for what i am after.

I have a simple website that needs to be available in English and
French.

I am using locale-url so all pages can have an independent url ( e.g.
en/page and fr/page)

There is a locale folder in my project that contains the .po and .mo
files, all this is working correctly when i switch languages.

The question is, how can my client translate the model fields in the
admin area ? For example, there is a client list page that uses a
model with a title and a body text. If they initially entered the
client list in English, how would they add it in French ?

I have heard about something called Rosetta but have not looked too
much into it yet.

Thanks for any advice on what solution would be best based on my
requirements.

--
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 request path



On Thu, Jul 1, 2010 at 1:36 PM, todd <c.t.matsumoto@gmail.com> wrote:

I've been working through an issue with my django project. The issue
is I've got one project, which will retrieve data for users of
different clients. I need to know 'from where' a viewer is coming from
(request.path [my original solution]). I've been looking at a number
of different options which sound close to what I want to do, but I'm
not sure what the best option is, not having done this before.

Do you mean the referrer?

-V-
http://twitter.com/venkasub

--
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.

django request path

Hello all,

I've been working through an issue with my django project. The issue
is I've got one project, which will retrieve data for users of
different clients. I need to know 'from where' a viewer is coming from
(request.path [my original solution]). I've been looking at a number
of different options which sound close to what I want to do, but I'm
not sure what the best option is, not having done this before.

My first option was to add a url in the urls.py with a 'tag' or
'keyword' then look for that tag/keyword in the request.path, which
I'd add as a session key. Then go onto get the data.

Something else I started looking at was the sites framework. After
reading through the documentation, I'm still confused how sites
actually works, so I'm not sure if this is the right option.

Another solution talked about using middleware, this came up in
connection with the research into using the sites framework.

And then yet another talked about doing this in apache.

Could some one help point me in the right direction?

Cheers,

T

--
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.