Bill,
Did the trick!
Many thanks.
Best wishes,
LRP
On Jul 17, 9:13 pm, Bill Totman <[EMAIL PROTECTED]> wrote:
> Here's the solution (so far):
>
> 1) Obtain the SVN version of django-tagging.
> 2) Place it or link the 'tagging' directory step '1' provides you into
>
Hello,
Still working my way through James Bennett's Practical Django
Projects. Now on p. 64.
I get this import error when I try to syncdb the Coltrane models.
from tagging.models import Tag
File "/usr/lib/python2.5/site-packages/tagging/models.py", line 9,
in from tagging.managers
Many many thanks to all who helped.
Problem solved.
There seem to have been two issues:
1) Mathias pointed out missing slash.
2) I'd copied only the top tiny_mce directory into my .../media/
jscripts/tiny_mce directory.
Mario, I'll definitely look at your note again when I try out django
Hi,
Thanks to all for responses, but puzzle persists...
Mathias, I added the slash. Still can't see the tiny_mce edit bar.
But it does provide a clue: Output of runserver now looks like:
[08/Jul/2008 19:37:17] "GET /admin/ HTTP/1.1" 200 4851
[08/Jul/2008 19:37:20] "GET
Thanks Chatchai.
Unfortunately, integration of tiny_mce still eludes me. It seems that
django is not looking in the proper directory for tiny_mce.js. But I
can't see why, despite generous off-list help from kind-soul Peter.
1) I've reviewed and documented my configuration below and would be
Many thanks for the help, Chatchai.
> Can you start web server and
> typehttp://localhost/usr/share/tinymce/www/tiny_mce.js
> and see if it return something rather than 400.
I get 404.
Here's url config:
urlpatterns = patterns('',
# Example:
# (r'^cms/', include('cms.foo.urls')),
s.py prior to the
generic views changes. It almost feels like the writer of the tutial
rushed through the last, important, section.
Thanks,
LRP
On May 11, 11:44 am, Scott SA <[EMAIL PROTECTED]> wrote:
> On 5/11/08, Aragorn son of Arathorn ([EMAIL PROTECTED]) wrote:
>
>
>
&
Hi Tkm,
That did the trick!
I actually had a symlink in /usr/local/bin, but it wasn't correctly
formatted. I must have misread the `pwd` phrase in the symlink
command.
Many thanks,
LRP
On May 7, 8:21 pm, "Bruno Tikami" <[EMAIL PROTECTED]> wrote:
> Hello LR
r in the django's install
instructions?
Many thanks,
LRP
--~--~-~--~~~---~--~~
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 unsu
on Debian Etch and postgresql8.1? Must be
many others who've confronted the same issues.
Many thanks,
LRP
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to djan
Oops! False alarm. My blunder.
Thought I had add products to db, but that was before I dropped table
for revision.
Sorry. Sorry.
Lloyd
On Apr 15, 3:34 pm, LRP <[EMAIL PROTECTED]> wrote:
> Hello,
>
> Suppose I have two models:
>
> class Product(models.Models
Hello,
Suppose I have two models:
class Product(models.Models):
product_name = models.CharField(max_length=100)
def __str__(self):
return self.product_name
def Admin:
pass
class Part(models.Models):
product = models.ForeignKey(Product)
part_name =
On Apr 6, 2:08 am, Michael <[EMAIL PROTECTED]> wrote:
> Not really following you here. The default layout of django auth is that you
> can have 100 people of the same name in multiple entries unaware that there
> is another person with the same name unless they try to make a username the
> same.
This pesky problem transcends Django. But many Django users will
encounter it.
Say we're creating a contact or registration application.
What is the best way to deal with the problem of two or more people
with exactly the same name?
This problem actually has two faces:
1) In an admin
Hello,
The models documentation in the Django site (http://
www.djangoproject.com/documentation/model-api/)
shows an admin screen for inputting articles.
Simple enough, but suppose we need to style some of the text in the
content field, e.g., italicize a word, display a string of words in
Hello,
On Jan 27, 11:45 pm, "James Bennett" <[EMAIL PROTECTED]> wrote:
> A better solution:
Many thanks. I will explore this approach.
Lloyd
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
Hello,
I'm speculating on how to replicate a site (same structure and
functionality, different url and content).
Am I correct that it would go as follows?
1) Create a new database
2) Assuming that the first site is in .../django/firstsite; make
directory .../django/secondsite
3) Copy content
On Jan 21, 8:28 pm, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
> On 21-Jan-08, at 10:32 PM, LRP wrote:
> this is an unsafe default for you to get things working. Now
> experiment with using password or md5 or ident for authentication
>
Thanks, Kenneth,
I've got it work
Thanks Kenneth,
That did the trick.
Looks like I'll have study pg_hba.conf configuration in much more
detail.
All the best,
Lloyd
On Jan 20, 9:07 pm, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote:
> On 21-Jan-08, at 4:07 AM, LRP wrote:
>
> > Psycopg2.Operational
Hello,
I've been making small progress moving into Django 0.96.1-1, but have
hit a snag early on.
I'm able to start a project and bring up the Django blue "It works!"
screen.
Following the instructions in http://glasnost.beeznest.org/articles/218,
I've created a Postgresql database web and
Hello,
Wow. This list is not only friendly, it parties!
Thanks to tips from Jeff Anderson, Tim Chase, and Forest Bond, I now
have start-up directories.
The trick: Debian redirects django-admin.py to django-admin. And, as
Forest Bond points out, django-admin is in a shell-executable path.
I
Hello,
Many many thanks for the thoughtful corrections and comments.
Particularly...
Karen Tracey for pointing out my dunder- headed mistake in running
django-admin.py from Python rather than shell command line.
I'm still having a problem since my shell can't seem to find django-
admin.py. I
...well, the local folks are friendly enough.
Last I washed upon these sands, capsized on the first leg of my maiden
voyage, I was advised that my vessel, django 0.95.1-1, running on
Linux Debian Etch, was a relic beyond salvage.
So back in port, I smash a magnum of champagne across the bow of
First, many thanks to all the kind salts who've responded to my SOS.
And particular thanks to Karen Tracey who replied to my first plea for
help. Your reply did slip by me. And it was a most helpful one.
So, it appears that my major problem is version. As several of you
point out, I'm running
Hello,
I'm trying to install django following directions in The Django Book.
I would like to run with Postgres on my Debian etch system.
When I try to build psycopg2.0.6 I get the error messages shown below.
Would much appreciate any help to enable me to bring up a healthy
system.
All the
25 matches
Mail list logo