Re: Issue 4 in django-blocks: Installation instructions do not work, directory structure doesn't match instructions

[django...@googlecode.com]

Comment #2 on issue 4 by linuxgfx: Installation instructions do not work,
directory structure doesn't match instructions
http://code.google.com/p/django-blocks/issues/detail?id=4

Same problem here, after running PYTHONPATH=<path to django-blocks>
and ./manage.py runserver the
same error occurs, such "Error: No module named blocks.apps.core".
What can i do to solve this issue?
Thank you in advance

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[django...@googlecode.com]

Comment #3 on issue 4 by jeremyberto: Installation instructions do not

work, directory structure doesn't match instructions
http://code.google.com/p/django-blocks/issues/detail?id=4

I also cannot run the demo.
I have added the "django-blocks" to the PATH. The same error is
encountered "Error:

No module named blocks.apps.core".

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--

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

[django...@googlecode.com]

Comment #4 on issue 4 by kimus.linuxus: Installation instructions do not

work, directory structure doesn't match instructions
http://code.google.com/p/django-blocks/issues/detail?id=4

@jeremyberto and @linuxgfx: if django-blocks was on your PYTHONPATH then you
shouldn't have that error.

@linuxgfx: PYTHONPATH=<path to django-blocks> ./manage.py runserver (is one
command
not two)

@jeremyberto: can you explain what you've done?


If you do:
cd <path_where_you_have_python_modules ie: /usr/lib/python2.6/site-packages,
~/.local/lib/python2.6/site-packages, etc (depends on your OS)>
svn co http://django-blocks.googlecode.com/svn/trunk/src/python/blocks/

and you are OK to do directly: ./manage.py runserver

[django...@googlecode.com]

Comment #5 on issue 4 by ljiang510: Installation instructions do not work,

directory structure doesn't match instructions
http://code.google.com/p/django-blocks/issues/detail?id=4

I don't have the right to access /usr/lib/python2.6/site-packages
(webfaction.com host),and I think I have set django-blocks into the
PYTHONPATH ( I verified from python shell with "import sys" and "sys.path"
commands.

I still see "No module named blocks.apps.core"

What can I do?

Thanks,

[django...@googlecode.com]

Comment #6 on issue 4 by kimus.linuxus: Installation instructions do not

work, directory structure doesn't match instructions
http://code.google.com/p/django-blocks/issues/detail?id=4

@ljiang510: hi, can you be more explicit?

did you put django-blocks in: ~/lib/pythonX.Y ??

i.e (assuming that your default python version is 2.6 and you have done
mkdir -p ~/lib/python2.6):
cd ~/lib/python2.6
svn co http://django-blocks.googlecode.com/svn/trunk/src/python/blocks/

You can read more in: http://docs.webfaction.com/software/python.html

[django...@googlecode.com]

Comment #7 on issue 4 by ljiang510: Installation instructions do not work,

directory structure doesn't match instructions
http://code.google.com/p/django-blocks/issues/detail?id=4

I had this issue solved by your instruction and webfaction's instruction.
Thanks for the help.

a few things I noticed:
1）how to make feeds working? I set it up on webfaction hosting, I put feed
url, for instance, http://sports.espn.go.com/espn/rss/nba/news is the feeds
source I want to use, I can't make it work

2) when I make a news article, I attached an image, but the image seems
never show up. What happened is that the webfaction recommends static_media
to store media. so i copy over the media from demo/media to
usr/my_webfaction_id/webapps/static_media/

the images under static_media is the place to store the attached images...

what can I do this?

Thanks,

[django...@googlecode.com]

Comment #8 on issue 4 by kimus.linuxus: Installation instructions do not

work, directory structure doesn't match instructions
http://code.google.com/p/django-blocks/issues/detail?id=4

I never used Webfaction but maybe this can help:
http://docs.webfaction.com/software/django/getting-started.html

For pulling your feeds you need to execute ./manage.py aggregate
You can put that command in a cron to execute in a interval that suits you.

PYTHONPATH=/path/to/python
DJANGO_SETTINGS_MODULE=mysite.settings
20,50 * * * * python /path/to/mysite/manage.py aggregate

[django...@googlecode.com]

Comment #9 on issue 4 by ljiang510: Installation instructions do not work,

directory structure doesn't match instructions
http://code.google.com/p/django-blocks/issues/detail?id=4

Thank you very much, Kimus. I had the issues solved.
I don't quite get the following tho.
*******************************

PYTHONPATH=/path/to/python
DJANGO_SETTINGS_MODULE=mysite.settings
20,50 * * * * python /path/to/mysite/manage.py aggregate

*******************************
I searched..

[django...@googlecode.com]

Comment #10 on issue 4 by kimus.linuxus: Installation instructions do not

work, directory structure doesn't match instructions
http://code.google.com/p/django-blocks/issues/detail?id=4

@ljiang510: that's an example of a crontab to run aggregate command every
hour at 20 and 50 minutes.

[django...@googlecode.com]

Updates:
Status: Fixed

Comment #11 on issue 4 by kimus.linuxus: Installation instructions do not

work, directory structure doesn't match instructions
http://code.google.com/p/django-blocks/issues/detail?id=4

I'm going to close this because the issue was corrected long ago. Tough I
want to write a better help page.