OK - fixed it for me, kinda...
I was pushing the flatpage content though the textile markup plugin
and removing this seemed to fix the 404s.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To
I'm having the same problem over here - after checking out the latest
svn version (6373), my own middleware flat out broke (response object
does not have header instance). When I removed that middleware, all my
flat pages are throwing 404's. Super weak.
> 1. You have to explicitly instantiate and save a UserProfile object
> before get_profile() will do anything -- Django will not implicitly
> create objects for you in the shell like that.
>
This is what I need to know. Thanks James.
--~--~-~--~~~---~--~~
Trying to extend the user group using this model code:
class UserProfile(models.Model):
user = models.ForeignKey(User, unique=True,
edit_inline=models.TABULAR, num_in_admin=1,min_num_in_admin=1,
max_num_in_admin=1,num_extra_on_change=0)
hours = models.FloatField( max_digits=8,
I think I got it.
Basically, my old file structure looked like this:
wiki (directory)
__init.py__
views.py
models (directory)
__init__.py
wiki.py
What I did was move wiki.py into the wiki folder and rename it
models.py. Then I deleted the models folder. So the final result
Wow! I was just upgrading an app and came up with these three
questions myself. Any help would be appriciated. This seems to be a
porting issue, as I am not having problems 1 & 2 with the new site I am
working on.
--~--~-~--~~~---~--~~
You received this
You have a good point about the consistancy. The `ifequal` should
mimic the `if` as much as possible. I think a bug report may be called
for in this case.
The ObjectPaginator is cool. I just can't seem to find any
documentation on how to properly implement it in a project.
This is what I did... hopefully it'll be of use to some. If someone
has a cleaner method of implementing this object
##someView.py
paginate_by = 20
paginator =
To clarify some things in the last post:
When I said, "the view should be handling all variable assignments if
possible". I meant to say the controller should be handling all
varialbe assignments. It's confusing because django calls controllers
"views", and views "templates". They have a
Modifying template variables in the template throws out the
model-view-controller way of doing things. In theory, the view should
be handling all variable assignments if possible.
Now, for your specific example, it seems it would be a pain to pass
both a capitalized and a lowercased version of
I've encounterred this problem as well. All I know is that if you run
the following SQL, everything will get better.
DROP TABLE IF EXISTS `django_admin_log`;
CREATE TABLE `django_admin_log` (
`id` mediumint(9) unsigned NOT NULL auto_increment,
`action_time` datetime NOT NULL default
What error are you getting when you try
"milestones.get_list(**request.GET)"?
Okay- that is a lot trickier. Here's some yucky code that uses the exec
command to accomplish the same goal... but it's definitely not the
elegant solution you are looking for...
q = []
for key, value in request.GET.items():
q.append ( "%s = %s" % (key, value) )
All get variables are automagically placed into the request.GET
dictionary. In your example:
http://mysite.com/manage/projects/1/milestones/?responsible__id__exact=1
Your variable `responsible__id__exact` would be obtained through the
code:
myVar = request.GET["responsible__id__exact"]
or
myVar
I cannot figure out the `official` place to put images, stylesheets,
and javascripts and the process to access them. Can someone explain
their method of doing this.
I was thinking of making a CSS_URL in the settings.py file and then
calling {{CSS_URL}}/styles.css, but I can't manage that
15 matches
Mail list logo
