#10935 closed defect (fixed)
Installation Problem
Reported by: | Arlene M Kliewer | Owned by: | falkb |
---|---|---|---|
Priority: | high | Component: | SimpleMultiProjectPlugin |
Severity: | blocker | Keywords: | |
Cc: | Trac Release: | 1.0 |
Description
Installed on a freshly created 1.0 instance of Trac using the mysql database connection. The plugin doesn't show the correct screens for linking the milestones & versions to projects.
I made sure I granted permissions and still don't see the proper screens.
Try to used my backend access(pypMyAdmin) to edit the tables manually to add link records, but still nothing shows up.
How do I get the "Project" item to show up? What did I miss in the install? Thanks for your time! - akliewer
Attachments (5)
Change History (13)
Changed 12 years ago by
Attachment: | MergedScreens.png added |
---|
comment:1 Changed 12 years ago by
Owner: | changed from Christopher Paredes to falkb |
---|---|
Status: | new → assigned |
Did you create a custom ticket field called 'project'?
If yes, please, send me useful parts of logging from yourproject/log/trac.log (plugin startup, plugin access logging, plugin errors). Set Debug level in Admin before you restart Trac. Then click on the page you sent as screenshot attachment:MergedScreens.png.
comment:2 Changed 12 years ago by
Yes I created the "project" custom field.
For tickets there is a new "project" item that wasn't there before. Looks like the plugin it is installed and running okay . . . but no screen for linking the the individual milestones and versions to the projects. Nothing like your sample images.
Attached are the log file and screen capture of ticket screen.
- AMK
comment:3 Changed 12 years ago by
Now it's suddenly clear to me what you've seen in attachment:MergedScreens.png; it's .../yourproject/admin/ticket/milestones/0012, right?! Well, unfortunately, it's not easy to hook into existing dialogs of the Trac core since the API actually does not support that very much, it's always very hackish and can fail with every new Trac version. That is why the plugin just replaces the original "edit milestone" dialog and instead uses an own dialog, that you can see here.
Open your milestone 0012 on the Roadmap page, click on its name to go into it, go to the bottom of the page and click on "Edit milestone". Then you will approach to .../yourproject/milestone/0012?action=edit where you'll get your desired project combobox. :)
Feel free to edit the wiki:SimpleMultiProjectPlugin page to make it more clear.
I hope that helps, CU, F@lk
Changed 12 years ago by
Attachment: | OperationalError2006.txt added |
---|
MySQL server has gone away error
comment:4 Changed 12 years ago by
Thank you that got me the desired page! Can't we put in a redirect link to the new version of the page?
Also, upon clicking the "cancel" edit button when leaving. I got the hairy error message.
OperationalError: (2006, 'MySQL server has gone away')
See attached error.txt file. Not sure if this error is your issue or the mysql connector with the whole trac system? Do I mark this resolved and open a new ticket? or do I post a ticket with the trac folks?
Good idea about editing the wiki for others, I will look into it!
Thanks again for your prompt response! I am loving this plugin. Good job to all! - AMK
comment:5 Changed 12 years ago by
Upon googling this error this link seemed to have the best answer. http://www.mysqlperformanceblog.com/2010/05/05/checking-for-a-live-database-connection-considered-harmful/
Hope that helps!
comment:6 Changed 12 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Sorry answered my own question about OperationalError. Seems to be an issue with the mysql connection and trac as a whole. So I am now marking this ticket fixed! Again Thanks - AMK
comment:7 Changed 12 years ago by
Glad to hear it works for you now :-) Thanks for your positive feedback, I'm happy you like it. I'm gonna think about how to find a way to add that project choice also on that Admin page... CU, F@lk
comment:8 Changed 12 years ago by
P.S.: I use SQLite and don't have such probs with it. Anyway the back trace of the error looks like a Trac core problem.
screen print