#2205 closed defect (fixed)
TimingAndEstimationPlugin Plugin Errors
Reported by: | awzm | Owned by: | Russ Tyndall |
---|---|---|---|
Priority: | normal | Component: | TimingAndEstimationPlugin |
Severity: | blocker | Keywords: | |
Cc: | Trac Release: | 0.11 |
Description
Following on from ticket #2192 (http://trac-hacks.org/ticket/2192) I'm still have trouble running this plugin. I upgraded to the newest Genshi and used TracPlugins to extract the .egg file and put in the plugins directory. I added the new line to trac.ini and used the upgrade command. When I start up tracd and go to http://localhost:8000/ my project environment isn't listed. My cmd windows states..
raise UndefinedError(key, owner=owner)
Undefined Error: {'name': ProjectName', 'description': u'The Trac Environment needs to be upgraded. \n\nRun "trac-admin C:
Projectfolder upgrade";} has no member named href"
I've already used the upgrade command only for it to make no difference. I followed the instructions on TracPlugins & TimingAndEstimationPlugin Installation to the word.
Thanks :)
Attachments (3)
Change History (12)
comment:1 Changed 17 years ago by
- Does trac work without the plugin installed?
- Remove the line from the trac.ini and pull the egg out of the plugin directory to be sure. I want to make sure that the problem is with the plugin.
- I dont have any experience with tracd, is it reporting the same error messages as the trac log? Normally an error refers to some place in code, instead of a referencing "Env Needs to Be Upgraded"
- the only error I raise in the whole plugin is in report manager we raise a single TracError and I have verified that that error type exists. Also I think that this error is not possible to hit (because it is only raised with conflicting versions of that file and there is only one version of that file available)
- Are you getting any other tracebacks?
comment:2 Changed 17 years ago by
I started from the beginning and this is what I get.
- Remove .egg file and line from trac.ini and boot up tracd. Trac works fine.
- Start up tracd and start logging (Type: File, Log Level: Error). Stop tracd.
- Put the .egg file in plugins dir and put the line in trac.ini
- Run trac-admin /path/to/projenv upgrade and get the expected return.
- Start tracd back up and go to http://localhost:8000 to find a blank screen
- Go to http://localhost:8000/projectname to find the error message: "Trac Error -
TracError: The Trac Environment needs to be upgraded. - Run "trac-admin c:\essentialtravel upgrade" ".
- Stop tracd.
I've attached a screenshot of the last traceback in cmd and my log file. Hope that helps.
comment:3 Changed 17 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:4 Changed 17 years ago by
Thank you very much for your persistence in helping me track down this bug. The trac log gave me everything I needed to locate and exterminate this bug. Hopefully it will be the last you have to deal with in this process.
Russ
comment:5 Changed 17 years ago by
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Sorry to be a pain but that change doesn't seem to have fixed it. As before I started from fresh and did everything to get the plugin working. I get the same blank screen when trying to list the project environments and the same error message when trying to access the project environment I setup.
I've attached the new log file ('tracv2.log') so you can see what errors are coming up. It looks like SQL errors but I'm no expert. It may help you to note that I'm using pysqlite-2.3.5.win32-py2.5
Thanks for all the time and effort you're putting to getting this fixed :)
comment:7 Changed 17 years ago by
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
comment:8 Changed 17 years ago by
thanks for the continued help with the plugin bobbysmith007 :)
i'll give the new version a go this afternoon
comment:9 Changed 17 years ago by
no problem. I am sorry this didnt get as thoroughly tested as it could have been.
I have installed this version of the plugin from scratch, so hopefully this one actually works!
If it fails please reopen the ticket and post your logfile again.
Thanks for your help debugging this matter,
Russ