Search Forums
17 posts Started 1 year ago by overflow012 Latest reply from Jeremy
hi! I followed all the steps from docs, but when I try to run paster serve --reload development.ini
I get this message
WebError Traceback:
"⇝ GenerationException: url_for could not generate URL. Called with args: () {'controller': '/admin'} "
in localhost:8080
Does anyone know?
Hey there Overflow.
That's an error caused by the newest version of Pylons (the new Pylons requires a new Routes package, which breaks things :( ).
Our next version of MediaCore (mediacore 0.8) will fix this by specifying to install Pylons 0.9.7. In the mean time you can do the fix manually with a one line edit.
Add a line that says:
'Pylons == 0.9.7',
to the file "mediacore/setup.py`" above the line that says:
'TurboGears2 >= 2.0.3',
Then make a new Virtual Environment and install Mediacore again:
source my_virtualenv/bin/activate
python setup.py developThanks for the quick response! but I did not find the line 'TurboGears2 >= 2.0.3' in the file MediaCore-0.7.2/setup.py
Please, I need to solve this problem as soon as possible
Ah yes, in 0.7.2 the line reads simply 'TurboGears2' — see line 11.
I've had no luck yet =S
Where is it failing? We'll need more details.
when I run
paster serve --reload development.ini
in localhost:8080 I get the error.
http://img714.imageshack.us/img714/4927/pantallazot.png <---------- Here the image of the error
I'll get one of the guys to respond to you on this a little later today. Busy day in the office here. Thanks for sending the screeny.
Hey Overflow,
Can you try doing the following for me? Activate your virtual environment, then start a python shell (just run 'python'), then paste the following into it:
import routes, pylons, tg
for x in [routes, pylons,tg]:
print xCopy the output of that here, so I can see what versions of the packages are currently installed.
Can you also copy the contents of your setup.py here (or to pastebin.ca)?
That should give me a better idea of what we're dealing with.
-- Anthony
the output it was:
<module 'routes' from '/home/maxi/mediacore_env/lib/python2.6/site-packages/Routes-1.12-py2.6.egg/routes/__init__.pyc'>
<module 'pylons' from '/home/maxi/mediacore_env/lib/python2.6/site-packages/Pylons-0.10rc1-py2.6.egg/pylons/__init__.pyc'>
<module 'tg' from '/home/maxi/mediacore_env/lib/python2.6/site-packages/TurboGears2-2.0.3-py2.6.egg/tg/__init__.pyc'>
and the setup.py content: http://pastebin.ca/1835298
Hey overflow,
We just got new install docs written. Try giving them a shot:
http://getmediacore.com/docs/install/index.html
We've checked the install instructions on a bunch of different OS X platforms and also on Ubuntu. If you follow everything in the instructions it should work.
EDIT: At the time of this posting, there was a line missing from the installation instructions for MediaCore-0.7.2. (the easy_install "Pylons == 0.9.7" line from the reply below. Running this before installing installing MediaCore will ensure that the correct versions of Pylons and Routes are installed, as alluded to in Anthony's first reply. Check out the instructions in the below reply for more details.
At first glance I can see two problems:
rm -rf mediacore_env
virtualenv --no-site-packages mediacore_env
source mediacore_env/bin/activate
easy_install "Pylons == 0.9.7"
cd MediaCore-0.7.2
python setup.py developinstall_requires = [
'Pylons == 0.9.7',
'TurboGears2',Then delete and recreate your virtual environment and reinstall MediaCore:
rm -rf mediacore_env
virtualenv --no-site-packages mediacore_env
source mediacore_env/bin/activate
cd MediaCore-0.7.2
python setup.py developenjoy! thank!
I fixed this by removing any Routes eggs in site-packages, and running easy_install 'Routes == 1.10.3'
After that comes more errors about __init__(self, *args, **kwargs) errors, I fixed those by removing the "*args, **kwargs" from TurboGears/tg/controller.py and set medicore/lib/base:153 to just __init__().
This is a hack and a half, and I'm pretty sure it's a python 2.6 issue. TurboGears errors are very pretty, but I was sick of seeing them, and didn't have time to get the Admin to downgrade to 2.5.
Good luck!
Did I mention this was a bad idea? I've gotten a setup working with Python 2.5. When I made the changes listed above, MediaCore loaded, but nothing happened when I tried to log into the admin area.
These dependency issues are going to be resolved in our upcoming 0.8 release. Most of the problem here is that the turbogears package managers have upgraded certain packages that MediaCore depends on, and thus it is breaking.
You must log in to post.