On 27 Jun, 2009, at 1:18 , stefan wrote:

> Hello, me again ;-)
Hi :-)

> I wanted to get the full fun out of agilo but sadly I failed right at
> the start.
>
> With no actions for creating anything at all agilo is not that much
> fun, you know.
>
> I don't know what I could have done wrong, maybe anyone of you does.
It seems from the log below that you didn't install the default  
settings. Probably through extensive hacking you manage to get Agilo  
egg recognized by Trac, but apparently it didn't modify your config  
with all the information you need. so I suggest you to:
1) Make sure that the "process" running trac can write the trac.ini  
file, and you from the console are doing the upgrade with a user that  
can do the same.
2) Remove from the system table in the database any agilo_* related  
entry, this will cause trac to force another upgrade.
3) Clean up your trac.ini from any change you made manually and leave  
there only the agilo.* = enabled in [components] this will allow the  
upgrade process to configure all the rest
3) Run the upgrade and check the trac.ini again, should be filled up  
with a lot of agilo configuration sections
4) You are running apache, so make sure that the process is restarted,  
cause mod_python will cache and mod_wsgi as well. Make also sure that  
if apache runs with www-data that user can write the trac.ini


This should fix it :-)

Best
ANdreaT

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Agilo for Scrum" group. This group is moderated by agile42 GmbH 
http://www.agile42.com and is focused in supporting Agilo for Scrum users.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/agilo?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to