Definitely go into phpmyadmin or something and see what the default
value for forum_topics is. Should be 0.
On Mar 9, 3:31 pm, "Richard Zehnal" <[EMAIL PROTECTED]> wrote:
> Thank you guys.
>
> Yes, I have installed the wiki as well and as I said, everything works
> just fine. The only problem I have is with adding new forum.
>
> And yes, recently the last error message, but ir might be for due some
> other mistake.
>
> Michael, you were right about my mess with different python versions :-(( :
>
> Take a look at that, it is not even funny: The following pop up after
> command "django-admin.py shell":
>
> from django.core.management import execute_manager
> try:
> import settings # Assumed to be in the same directory.
> except ImportError:
> import sys
> sys.stderr.write("Error: Can't find the file 'settings.py' in the dir
> ectory containing %r. It appears you've customized things.\nYou'll have t
> o run django-admin.py, passing it your settings module.\n(If the file set
> tings.py does indeed exist, it's causing an ImportError somehow.)\n" % __
> file__)
> sys.exit(1)
>
> if __name__ == "__main__":
> execute_manager(settings)
> [EMAIL PROTECTED] raw]$ django-admin.py shell
> Traceback (most recent call last):
> File "/home2/zehi/bin/django-admin.py", line 5, in ?
> management.execute_from_command_line()
> File "/home2/zehi/lib/python2.4/django/core/management.py", line
> 1237, in execute_from_command_line
> from django.utils import translation
> File "/home2/zehi/lib/python2.4/django/utils/translation/__init__.py",
> line 3, in ?
> if settings.USE_I18N:
> File "/home2/zehi/lib/python2.4/django/conf/__init__.py", line 27,
> in __getattr__
> self._import_settings()
> File "/home2/zehi/lib/python2.4/django/conf/__init__.py", line 52,
> in _import_settings
> raise EnvironmentError, "Environment variable %s is undefined." %
> ENVIRONMENT_VARIABLE
> EnvironmentError: Environment variable DJANGO_SETTINGS_MODULE is undefined.
> [EMAIL PROTECTED] raw]$ python manage.py shell
> Python 2.5 (r25:51908, Sep 20 2006, 04:00:21)
> [GCC 3.4.6 20060404 (Red Hat 3.4.6-3)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
> (InteractiveConsole)
>
>
>
> It happened right after I've changed my server setting for multi
> domans from one django instance..... Well, I have something to do over
> the weekend..
>
> But still wondering, why I can not get running the board app at my
> local machine. There is no problem with versions..
>
> On 3/9/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
>
>
> > zehi, this may be a dumb question, but do you have the wiki installed
> > or just the board?
>
> > On Mar 9, 8:15 am, "Michael K" <[EMAIL PROTECTED]> wrote:
> > > On Mar 8, 6:41 pm, "zehi" <[EMAIL PROTECTED]> wrote:
>
> > > > All Right. It seems to be a problem somewhere else:
>
> > > > Both, localy and on server I run python 2.5. It looks like, that
> > > > diamanda installation procedure is calling older python version
> > > > 2.4.... ??? Is it possible?
>
> > > > sample:
>
> > > > [EMAIL PROTECTED] raw]$ python manage.py syncdb
> > > > [EMAIL PROTECTED] raw]$ cd ..
> > > > [EMAIL PROTECTED] django_current_python_25]$ export
> > > > DJANGO_SETTINGS_MODULE=raw.settings
> > > > [EMAIL PROTECTED] django_current_python_25]$ export PYTHONPATH=$PWD
> > > > [EMAIL PROTECTED] django_current_python_25]$ django-admin.py syncdb
> > > > Traceback (most recent call last):
> > > > File "/home2/zehi/bin/django-admin.py", line 5, in ?
> > > > management.execute_from_command_line()
> > > > File "/home2/zehi/lib/python2.4/django/core/management.py", line
> > > > 1238, in execute_from_command_line
> > > > translation.activate('en-us')
>
> > > [snip]
>
> > > This alone tells me that your djang-admin.py is using python2.4,
> > > unless you have your ~/lib all messed up. :)
>
> > > Check the django-admin.py source's shebang (first line) and see if
> > > it's calling 2.4 specifically?
>
> > > Other than that, it still sounds like a database problem for the first
> > > part. I'd still consider looking at your table's defaults. This
> > > latest error looks like Python can't find your modules, which, again,
> > > appears to be because of the version you think you're running not
> > > being the version you're actually running. :)
>
> > > > It's over my head yet. Somebody has experience with that?
>
> > > Everything is typically over my head when it comes to Django, but I'm
> > > getting there. :) Best bet: focus more on Python than the "Django
> > > Way" and it will make more sense as you learn.
>
> > > --
> > > Michaelhttp://tsal.arikel.net
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
