Friday, 2010-08-06

../irclogs/#mantishelp.2010-08-06.log
--- scribe started ---00:00
dhx_mhowdy08:27
paulrboo09:58
dhx_mpaulr: hey10:30
paulrlo10:30
paulryou about this w/e?10:30
paulror family10:30
dhx_mshould be around here a bit :)10:30
istvanbhi there! One of my users has lost the "hide status" option in the "view issues" tab. All the other users (reporters) have it except him. Any guess what can cause this?10:40
istvanbany guess?11:07
istvanbresolved. After couple logouts and logins its back. Pretty wierd though11:23
nuclear_eclipseistvanb: "advanced filters" mode doesn't use "hide status", and he had most likely selected that11:48
istvanboh11:53
istvanbIt makes sense11:53
istvanband now... believe or not: another question11:54
istvanbI have turned on the due-date function11:54
paulrunlucky11:54
istvanbbut actually I can not use it because if I report an issue and select the due date I can not submit it11:54
istvanbit goes back to the due date field like if it has a problem with it11:54
paulrwhat's it say11:55
istvanbnothing11:55
istvanbit just doesnt allow me to use it11:55
istvanbany guess?12:04
paulrit was never that reliable when it got added12:11
paulrI tried to fix some of it12:11
paulrso it's prboably completely broken12:11
paulron top of that dhx has rewritten bug_report.php12:11
paulrso without looking.. ;/12:11
dhx_mstop blaming me :p12:17
dhx_mI fixed it :p12:17
istvanblet me rephrase then: is there any known bug about the due-date field which makes it not recommended to use?12:21
paulrit should 'work'12:21
paulrit used to get a bit confused with timezones12:21
paulri.e. you could find that it would adjust -1 hour each time you viewed/edited a bug12:22
istvanbhmm12:22
istvanbI have checked out the DB12:22
istvanbmost of the issues has a default value of 112:22
istvanbtwo of them has something else, looking like a date12:22
paulryes12:22
dhx_mpaulr: perhaps that was just a feature management put into your last work-related bug tracker? :p12:22
paulr1 second past 197012:22
istvanblet me check those two iessues very quick12:22
paulrdhx_m: mm?12:22
istvanbok12:24
istvanbit shows (and I remember it) I was able to set duedates 3 weeks ago12:24
istvanbI was on vaction since then12:24
istvanbthose two issues shows the due-date correctly12:24
istvanbbut now I can not report an issue with a due-date :(12:25
istvanbalso one of the issues is due, and it show is12:26
paulrwhat version are you on ?12:26
paulrof mantis12:26
istvanb1.2.112:27
istvanbis there anything to setup for due-dates except $g_due_date_update_threshold and $g_due_date_view_threshold?12:31
istvanbThe due date field accepts "1" though12:47
istvanbif the due date is not filled then if I edit the issue I can modify it. But lets say if I click "change status to" then I have the same problem as descirbed above12:52
istvanbI am restarting the server to see if it solves (?)13:19
istvanbno, its not :P13:21
istvanbok, I have found this. If I run mantis from the server "localhost/mantis" I have no problems with the due date13:27
istvanbif I run mantis from a client computer like "192.168.10.111/mantis" then due date can not be applied13:28
ToreadorVampire2 things:  #1 (which maybe you already know about) - on the Mantisbt website there's a link to this channel and it includes a Mibbit widget, which nobody is able to use because Freenode banned Mibbit a while back ...15:43
ToreadorVampire#2 is my actual question which is:  Is there a way to suppress Mantis' automatic parsing of URLs as hyperlinks within the bug notes?  I am pasting data that Mantis is interpreting as URLs and trying to be helpful and offer links and stuff.  Is there some kind of markup I can use to tell Mantis not to do that?15:44
paulryou can turn it off always15:49
paulrquestion: is it getting the url's wrong? or just they are urls but you dont want them linkable15:50
ToreadorVampireUh15:50
ToreadorVampireIt's sort of a mixture of two15:50
paulrin that if your pasting a url and we are parsing it wrong15:51
paulri'm tempted to see if we can fix the parser15:51
paulrnuclear_eclipse loves fixing the url parser15:51
paulrwhen I break it so that's especially fun15:51
ToreadorVampireIt's information from a detailed error report within a web app we're developing, and the error relates to email validation.  So, it includes URLs and also things that look like email addresses.  Since this is part of a detailled error report though I don't want that stuff clickable.  By parsing it is's mangling the text I pasted into the bugreport15:52
ToreadorVampire1 sec, will check to see whether "technically" it is getting it right though15:53
paulrin terms of the parsing15:53
paulrif your on mantis 1.2 , you can configure the default text formating (core formatting) plugin15:53
ToreadorVampireNo, it's also screwing up the parsing ... badly15:53
paulrand tell it to turn off some of the parsing I believe15:53
paulrcan you generate a safe version of the url so I can see?15:54
ToreadorVampireNah, I'm on 1.1.8 atm15:54
ToreadorVampireWill pastebin the text I pasted into mantis and then ... uh ... will see if I can get the HTML that mantis generated on the bug page15:54
ToreadorVampirehttp://pastebin.com/pbE5z9WD15:57
ToreadorVampireIn the mean time what I'll do is save that information + the stack trace in a textfile and attach it to the bug.  That way it'll be safe from being mangled by the URL parser16:00
ToreadorVampireI was just wondering where there was any kind of "suppress the URL parser" escape sequence built into Mantis.  Something like <nourl>http://example.com/foo</nourl> that would prevent it from screwing with my text16:01
paulrwtf did it do there16:05
ToreadorVampireWell, you know ... that's what i thought :D16:07
ToreadorVampireBut - that's a pretty complex string it ended up trying to parse.  It wasn't even a use case where I /wanted/ it to parse it as a URL ...16:08
paulri'm trying to work out in what order it parsed that :)16:08
ToreadorVampireHaha, have fun :p16:08
paulrmwell16:08
paulrwhat it's done is wrong16:08
paulras obviously you'd expect that to be a url16:08
paulryou might not want it to parse but as a user/dev/whatever you'd expect it to parse it as a url not an email address16:09
paulrI think atm we only allow the parsing to be turned off globally16:09
paulrhowever, the idea of an escape sequence..16:09
ToreadorVampireMan this web app project I have inherited :s16:13
ToreadorVampire99.9% of the codebase belongs on thedailywtf :(16:13
ToreadorVampireThe level of stupidity I'm dealing with:  Until I fixed it, all of their 404 error pages returned HTTP status code 200 OK.  All of their HTTP 500 error pages still return 200 OK (I still have to track down wtf they are doing there)16:15
ToreadorVampireThere's something ironically amusing about a page that reads "HTTP error 404: Page not found" but that page not actually using a 404 status code16:15
paulrheh16:18
ToreadorVampireK, I'm out, time to get to the pub!16:37
paulrnuclear_eclipse: lo?19:32
nuclear_eclipsehowdy19:32
paulrdi you see that pastebin url earlier?19:33
paulr<ToreadorVampire> http://pastebin.com/pbE5z9WD19:33
nuclear_eclipseno19:33
paulrseems you broke url parsing :P19:33
nuclear_eclipseI haven't had any time to investigate19:33
nuclear_eclipseno, I didn't, 1.1.x has always had a shitty parser19:33
nuclear_eclipsethat's why I fiexd it all in 1.219:34
paulroh was that dude on 1.1?19:34
nuclear_eclipse11:54 < ToreadorVampire> Nah, I'm on 1.1.8 atm19:34
paulrdidn't see that19:34
nuclear_eclipsegood job on reading19:34
paulrnp19:34
paulrit'#s not one of my skills19:34
ShakraDoes anyone know anything about wiki integration?21:26
ShakraIs there a reason why wiki links changed from being http://$g_wiki_engine_url/index.php/$g_wiki_root_namespace:<bug number> to http://$g_wiki_engine_url/index.php/<project name>:<bug number> after I upgraded from Mantis 1.1.6 to 1.2.1?21:57

Generated by irclog2html.py