> 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
Andrea Tomasini schrieb:
>
> On 27 Jun, 2009, at 1:18 , stefan wrote:
> [...]
> This should fix it :-)
First of all: it worked! *yeah*
Some explanations of what I did (for the list archive):
* modified my trac.db (Sqlite) with http://sqlitebrowser.sourceforge.net/
* removed the agilo-row in the system-table and deleted all tables
starting with agilo_
* removed every agilo-related entry in my trac.ini but the one below
components
* furthermore I deleted all other custom plugins
(clients,timingandestimation,burndown) which might colide with
agilo-features
* restart of apache (to restart trac running in mod_python)
* trac-admin /myreps upgrade
* done
Now I have all the create actions in the menu.
Sidenote: I noticed this line in my trac.ini:
permission_policies = AgiloPolicy, DefaultPermissionPolicy,
LegacyAttachmentPolicy
It seems to me that a config missing "AgiloPolicy" might act like mine did.
Anyway, I wanted to thank you very very much.
NOW I finally can look around, thanks to you. :)
-stefan