Thursday, 2010-07-15

../irclogs/#mantishelp.2010-07-15.log
--- scribe started ---00:00
istvanbhi there08:15
istvanbI need some help from a developer, is anybody here?08:16
nuclear_eclipseistvanb: just ask your question an we'll eventually get around to it :P12:06
istvanbI have attached a wrong index.php to a certain issue. Actually the file is correct but it has my email address. (also has a password which expired a year ago, but...) can you just remove the file and I can upload a new one?12:15
istvanbissue no: 1198912:16
nuclear_eclipsedeleted12:16
slim_hello all, i installed mantistb and i this error ...12:26
slim_Database user doesn't have SELECT access to the database ( Table 'mantis-mw.mantis_config_table' doesn't exist )12:27
mustangsalslim_:  Did you create the database and a database user?  just askin'13:08
slim_yes mustangsal , i create the database and the user is the same that i use it to create db13:09
mustangsalif you're getting that error the first test should be to login to the database with the mantis user from the mantis host.13:10
slim_mustangsal:   i do it and find empty database13:11
mustangsaldid you go to /admin/install.php ?13:11
mustangsaland that's where you got this error?13:11
slim_yes, this is from admin page13:12
slim_check for everything ok only i got 4 errors13:12
slim_checking ability to SELECT records13:12
slim_checking ability to INSERT records13:12
slim_the same for UPDATE, and DELETE13:12
slim_BAD13:13
slim_Database user doesn't have DELETE access to the database ( Table 'mantis-mw.mantis_config_table' doesn't exist )13:13
slim_i do it twice and delete db and create it again, with the same result13:13
mustangsalfro the db... what does select * from mysql.db where User=<your mantis db username>  return13:14
mustangsal...also try changing mantis-mw to mantis_mw13:15
slim_ok13:15
mustangsal...you're using 1.2.1 right13:15
mustangsalmantis 1.2.113:15
slim_yes, the latest stable version13:15
mustangsal...wait13:16
mustangsaltry using bugtrack as the database name13:17
mustangsalI think I see it hardcoded in the install script13:17
slim_mustangsal:   there is already another working mantis that use this database13:17
mustangsalhmm ok13:18
slim_in which file this exist ?13:18
slim_in this case i can change it13:18
mustangsalI'm looking through /admin/install.php13:18
mustangsalI'm looking for your specific error message13:18
mustangsalto see how it checks13:19
slim_currently i will change dbname and try again13:19
mustangsalyeah if there's a config already is asks otherwise it appears to assign both 'localhost' and 'bugtrack'13:22
slim_i change the name  to mantismw the same error still exist13:24
mustangsal...it's ugly.. but you could also grab the DB schema from schema and build it manually13:24
slim_this will be better of course13:24
slim_where db schema exist ?13:25
slim_i see it now schema.php13:25
slim_thanks mustangsal i will try and see how it work13:25
istvanbnuclear_eclipse: thanks man13:27
mustangsalworth a shot... if you have mysql root user.. you could let mantis create everything... but if bugtrack is hardcoded (and not replaced in the script elsewhere) that could be bad13:27
slim_yes, old mantis full of data :)13:27
slim_thanks mustangsal now it work13:29
mustangsalnice13:29
slim_thanks again for your help13:29
mustangsalyour welcome]13:30
nuclear_eclipsesiebrand: good timing17:29
nuclear_eclipsesiebrand: can you review bug 12145?17:30
foobotBug 12145 - udobes2 - reopened - feedback17:30
foobotsearch should be case insensitiv - http://www.mantisbt.org/bugs/view.php?id=1214517:30
siebrandnuclear_eclipse: at a camping site at the moment - will see if I have the battery life to get to it...17:32
nuclear_eclipseoh, no worries17:33
nuclear_eclipseit can wait17:33
nuclear_eclipseI assigned it to you anyways :P17:33
nuclear_eclipsefeel free to take care of it whenever you're back at home17:33
nuclear_eclipseand have fun camping :)17:33
siebrandnuclear_eclipse: thank.17:36
siebrand+s17:36
Shakra@nuclear_eclipse - got a sec for some source integration questions? :)19:13
foobotShakra: Error: "nuclear_eclipse" is not a valid command.19:13
nuclear_eclipseShakra: go ahead :)19:19
Shakranuclear_eclipse  - I think i have things mostly set up correctly...I found my repository and it looks like it imports properly19:20
ShakraI also had the Resolve Fixed Issues checkbox unchecked...19:20
Shakrahowever once things started importing...i started getting emails saying that my issues were being resolved19:21
Shakraand statuses were being changed from closed to our done status which is a custom resolved status in our mantis flow19:22
Shakrado i have to leave the Bug Fixed regexes blank or something to keep it from doing that?19:22
Shakrai really only need the bug linking at the moment19:23
nuclear_eclipseno, if the box is indeed unchecked (the default state), then it shouldn't be changing statuses19:23
Shakrait is...but it did...19:23
nuclear_eclipsethat sounds like either a bug, or an odd conflict of some sort19:23
nuclear_eclipseare you by chance using a git clone, or are you using a snapshot?19:24
Shakrawebsvn19:24
nuclear_eclipseI mean how did you install the plugin?19:24
Shakrai downloaded a snapshot19:24
nuclear_eclipseok19:24
Shakra1.6.219:24
nuclear_eclipseif you take a screenshot of your source configuration page, and report a but to my tracker at http://leetcode.net/mantis, I'll try to take a look at it when I get the chance, and see if I let a bug slip in with one of my recent updates19:26
Shakraalso...what does [Disabled] mean in the Bug Fixed Status listbox?19:26
nuclear_eclipseif I remember correctly, disabled means that it won't actually change the status when it detects a fixed issue, but it will still process it as a fixed issue, ie, update the resolution field, assign it, and/or attach a bugnote19:29
nuclear_eclipseyou could potentially try using that as a stopgap measure to prevent it from changing the bug status19:30
ShakraI did. I also killed my apache server and quick changed all the emails in my test database to my own email to stop spamming everyone since I was just using a snapshot of our live database :\19:32
nuclear_eclipseShakra: you can set $g_enable_notifications = OFF in your config_inc.php to prevent sending emails on a test install19:33
nuclear_eclipseoops, that's not correct19:34
nuclear_eclipse$g_enable_email_notification = OFF19:34
Shakraah...thanks...didn't think of that19:35
nuclear_eclipse:)19:35
nuclear_eclipseI made a similar mistake when I was testing a migration at my last workplace, ended up mailing almost the entire company with a bogus notification :X19:36
ShakraI'm going to try the import again.  We have a huge SVN repository so it takes a while.  But I'm going to make sure the Resolve Fixed Issues checkbox is unchecked really hard this time.  And make sure i'm not sending out emails :)19:37
ShakraI'll report it on your bugtracker if it happens again...thanks nuclear_eclipse :)19:37
nuclear_eclipseShakra: ah, I think I've found the bug just looking at the source code19:38
nuclear_eclipsemind testing a small change to Source/Source.API.php for me?19:39
nuclear_eclipseon line 331: change `} else {` to `} else if ( $t_enable_resolving ) {`19:40
Shakrasorry was afk...sure i can test it19:48
nuclear_eclipsecool, either way, a bug report would be appreciated, and if it does work, go ahead and post that, and it will help me remember what to fix19:50
ShakraI won't be able to report it till probably tomorrow...the import takes several hours19:53
nuclear_eclipsenp19:54
nuclear_eclipseI've got a busy schedule as it is :P19:55

Generated by irclog2html.py