| ../irclogs/#mantishelp.2009-05-27.log | ||
| --- scribe started --- | 00:00 | |
| mantisbot | New bug: Bug 10540 - brodriguez - open - new | 08:33 |
|---|---|---|
| mantisbot | New bug: Page redirection error - APPLICATION ERROR #18 - http://www.mantisbt.org/bugs/view.php?id=10540 | 08:33 |
| cweiss | hi, | 09:00 |
| cweiss | where can i setup new project states / change lables? | 09:01 |
| DaniW | where can i setup new project states / change lables? | 09:03 |
| DaniW | hello | 09:17 |
| DaniW | hi all | 09:26 |
| thraxisp | DaniW: see http://www.mantisbt.org/manual/manual.customizing.mantis.customizing.status.values.php in the manual. | 10:13 |
| brodriguez | hi everyone | 10:14 |
| brodriguez | may I ask about a problem here or better wait for my issue resolution? (sorry about my english) | 10:16 |
| DaniW | hi | 10:16 |
| dhx_m | brodriguez: which issue? | 10:17 |
| brodriguez | #10540 | 10:19 |
| brodriguez | number 0010540 | 10:19 |
| thraxisp | bug #10540 | 10:26 |
| mantisbot | Bug 10540 - brodriguez - open - new | 10:26 |
| mantisbot | Page redirection error - APPLICATION ERROR #18 - http://www.mantisbt.org/bugs/view.php?id=10540 | 10:26 |
| brodriguez | that´s the issue | 10:27 |
| brodriguez | any help? | 10:29 |
| dhx_m | I don't use 1.1.7 so can't reproduce I'm afraid... | 10:31 |
| dhx_m | haven't seen that issue in 1.2.x but it could be configuration specific | 10:32 |
| dhx_m | oh | 10:33 |
| dhx_m | I see your problem | 10:33 |
| brodriguez | really? :D | 10:34 |
| brodriguez | what did you see? | 10:35 |
| brodriguez | dhx_m: what did you see? | 10:37 |
| kenguest | hmm. is there demo of mantis available somewhere that I can see the summary graphs? | 10:38 |
| dhx_m | brodriguez: I made a reply | 10:41 |
| dhx_m | essentially Mantis is complaining because you've already sent headers somewhere before Mantis wants to | 10:42 |
| dhx_m | or maybe it is some other text/whitespace/whatever that is sent before headers | 10:42 |
| brodriguez | ok thank you very much dhx_m, i´ll take a look | 10:45 |
| dhx_m | are you pulling in any external PHP files into Mantis? | 10:45 |
| dhx_m | what I'd do is check your site with a client that can show you PHP headers | 10:46 |
| dhx_m | sorry... HTTP headers | 10:46 |
| dhx_m | so you can see the order they're sent to you | 10:46 |
| brodriguez | ehmm... Fiddler? | 10:46 |
| dhx_m | pay special attention to the last one in the list | 10:46 |
| dhx_m | Wireshark... or any other packet sniffer | 10:47 |
| dhx_m | not sure what Fiddler is | 10:47 |
| dhx_m | yeah that looks OK from my quick 2sec search of it | 10:47 |
| [KK]Kirill | dhx_m: lo | 10:50 |
| dhx_m | [KK]Kirill: hi :) | 10:50 |
| brodriguez | dhx_m: i´m watching what Fiddler shows | 10:51 |
| [KK]Kirill | How many cost Apple iPhone in your country? | 10:51 |
| brodriguez | but i don´t know where to look or what to search | 10:51 |
| dhx_m | try to reproduce the error again | 10:51 |
| dhx_m | and look through the fiddler logs to find access to the bug_relationship.php file on the server | 10:52 |
| brodriguez | i see that bug_relationship_delete.php has a HTML code before the "html" and "head" tags | 10:52 |
| dhx_m | anything specific? | 10:52 |
| brodriguez | just the code to generate th "SYSTEM WARNING: in_array() [function.in-array]: Wrong datatype for second argument" message | 10:53 |
| brodriguez | to show that message before the real mantis header with its logo | 10:53 |
| dhx_m | you actually see PHP code in fiddler? | 10:53 |
| dhx_m | or just the HTML? | 10:54 |
| brodriguez | no, I see the html code generated | 10:54 |
| dhx_m | ah that is OK then | 10:54 |
| brodriguez | the page I actually see | 10:54 |
| dhx_m | what you're interested in is the page where the full on error message appears | 10:55 |
| dhx_m | the one before <html> is "ok" | 10:55 |
| brodriguez | ok | 10:55 |
| brodriguez | but i don´t see anything significant in that piece of code | 10:56 |
| brodriguez | i´ll paste it | 10:56 |
| dhx_m | nah, you're looking for HTTP headers | 10:57 |
| brodriguez | ok too big | 10:57 |
| dhx_m | not the actual HTML code | 10:57 |
| dhx_m | ie. Content-Type: something | 10:57 |
| brodriguez | oh | 10:57 |
| brodriguez | ok | 10:57 |
| dhx_m | does it show it in raw form, in the order sent by the server? | 10:57 |
| brodriguez | i think i´m getting it | 10:58 |
| brodriguez | i see many parameters from the header | 10:58 |
| dhx_m | what is the first and last ones? | 10:58 |
| brodriguez | Cache Control, Date, Expires, Context-Length... | 10:58 |
| brodriguez | Cache is the first one i think | 10:59 |
| brodriguez | Cache-Control: no-store, no-cache, must-revalidate | 10:59 |
| dhx_m | actually Mantis redirects suck... using meta refresh :( | 10:59 |
| dhx_m | is there anything before "Content-Type"? | 11:00 |
| brodriguez | last one-> Keep-Alive: timeout=5, max=100 | 11:00 |
| brodriguez | yes, before Content-Type there is Content-Length: 5961 | 11:00 |
| dhx_m | anything else? | 11:00 |
| brodriguez | after Content-Length there is Content-Type: text/html;charset=utf-8 | 11:01 |
| dhx_m | hmm let me see what happens on my install | 11:01 |
| brodriguez | ;) | 11:01 |
| dhx_m | looks ok to me | 11:05 |
| dhx_m | maybe some HTML is being sent before those headers then | 11:06 |
| brodriguez | i don´t know, not all redirections makes this error. | 11:07 |
| dhx_m | not sure how to check that | 11:07 |
| dhx_m | is it when you click 'delete' next to a relationship? | 11:07 |
| brodriguez | yes, but not inmediately: i click Delete, then i am redirected to a page with a Delete Button in the middle. | 11:08 |
| brodriguez | then click that delete button an i get the error page | 11:09 |
| dhx_m | is that intermediate page URL bug_relationship_delete.php? | 11:10 |
| brodriguez | yes | 11:11 |
| dhx_m | well it does indeed seem that Mantis is sending out HTML before the headers | 11:13 |
| dhx_m | brodriguez: please try setting $g_stop_on_errors=ON in config_inc.php | 11:15 |
| brodriguez | an user is bugging me now, i´´l be back in a hurry | 11:15 |
| dhx_m | ok | 11:15 |
| dhx_m | oh | 11:20 |
| dhx_m | might have to do with that unhandled error you were talking about | 11:20 |
| brodriguez | nop, other stuff :S | 11:24 |
| dhx_m | so that config option didn't help? | 11:26 |
| brodriguez | still with that user, but i can tell you that i tried the stop_on_errors option with ON and it just breaks the page generation | 11:31 |
| brodriguez | i think it is for debug mode | 11:31 |
| brodriguez | or testing i think, don´t know well | 11:31 |
| dhx_m | what does it do? | 11:33 |
| dhx_m | white pages? | 11:33 |
| dhx_m | error messages? | 11:33 |
| brodriguez | i think i remember it just stops generating html code after the message "SYSTEM WARNING: in_array() [function.in-array]: Wrong datatype for second argument " | 11:34 |
| brodriguez | and doesn´t appear the mantis logo and everything above it | 11:35 |
| brodriguez | :S | 11:35 |
| dhx_m | hmmm now I think we just need to work out where that in_array() error is coming from | 11:35 |
| dhx_m | maybe one of your configuration options is a string instead of number | 11:38 |
| dhx_m | or something like that? | 11:38 |
| dhx_m | doubt it though... | 11:38 |
| brodriguez | i´m back | 11:42 |
| brodriguez | i posted a screenshot | 11:42 |
| brodriguez | wich shows in debug mode wich line of the print_api.php file crashes | 11:43 |
| brodriguez | Full path: /usr/local/http/htdocs/mantis/core/print_api.php Line: 68 ---> trigger_error function | 11:43 |
| brodriguez | with args--> ( '18', 256 ) | 11:44 |
| dhx_m | can you please check that file and paste that line here | 11:44 |
| dhx_m | it has changed in the version I'm looking at :) | 11:45 |
| brodriguez | ok | 11:45 |
| brodriguez | trigger_error( ERROR_PAGE_REDIRECTION, ERROR ); | 11:45 |
| brodriguez | i read your last not in my issue | 11:45 |
| dhx_m | ah yeah, that is the error we already know about | 11:45 |
| brodriguez | i´m so noob at PHP, but i kinda understand what you say | 11:45 |
| dhx_m | what's happening is that somewhere beforehand in the code, in_array() - a PHP function - is failing | 11:46 |
| brodriguez | do you think the problem is bug_relationship_delete.php? | 11:46 |
| dhx_m | not sure at the moment | 11:46 |
| dhx_m | print_api is definitely broken in trying to send HTTP headers after sending HTML content | 11:47 |
| dhx_m | but I'm wondering why no one else has experienced that problem | 11:47 |
| brodriguez | THAT is what i´m wondering too | 11:48 |
| brodriguez | this version, 1.1.7, has been test for a while, so that makes me think if the problem is mantis | 11:48 |
| brodriguez | or it´s me :s | 11:48 |
| dhx_m | oh | 11:48 |
| brodriguez | i mean | 11:49 |
| brodriguez | is the code the problem or a config file? | 11:49 |
| dhx_m | ob_start() is forced by PHP | 11:49 |
| dhx_m | Mantis forces that PHP option on... to do output buffereing | 11:50 |
| brodriguez | aham | 11:50 |
| dhx_m | so it shouldn't matter when HTTP headers are added | 11:50 |
| dhx_m | it must be failing (returning false) | 11:50 |
| brodriguez | i´m confused :s | 11:50 |
| dhx_m | maybe safe mode or something else on your server is preventing ob_start from working? | 11:51 |
| brodriguez | don´t know | 11:51 |
| brodriguez | but | 11:51 |
| brodriguez | # don't send more headers if they have already been sent (guideweb) | 11:51 |
| brodriguez | headers_sent() is making me go trough the "else" and throw the error | 11:52 |
| brodriguez | that´s what you say, a header has been already sent | 11:52 |
| brodriguez | but what/why? | 11:52 |
| dhx_m | well without output buffering, PHP sends headers as soon as it gets them | 11:53 |
| dhx_m | and that happens before the code in print_api.php is called | 11:53 |
| brodriguez | aham | 11:53 |
| brodriguez | but other redirections work fine, so no header is sent before print_api.php, isn´t it? | 11:54 |
| brodriguez | i mean, this happens in specific circunstances, and some header is sent i don´t know why | 11:54 |
| brodriguez | i´so lost, and maybe i´m confusing you. obviously i am a noob at php | 11:57 |
| dhx_m | nah, you're right | 11:59 |
| dhx_m | other redirects should also fail, but they're not... so maybe it is just an isolated thing with the relationships | 11:59 |
| brodriguez | that´s the point | 12:01 |
| brodriguez | i have to go now. thank you VERY much for your help dhx_m. i´ll be back later and check any update on my issue | 12:02 |
| brodriguez | thanks ;) | 12:02 |
| dhx_m | ok keep an eye on the bug, we'll see what the developers say :) | 12:03 |
| mantisbot | New bug: Bug 10541 - stb - open - new | 12:09 |
| mantisbot | New bug: Some german strings (files attached) - http://www.mantisbt.org/bugs/view.php?id=10541 | 12:09 |
| DaniW | how do i add new project states? e.g. ' check customer input and create offer'', 'offered to the customer', 'ordered by customer', 'in process', 'waiting for feedback', 'stoped at all', 'ready for checkup', ... | 12:11 |
| mantisbot | New bug: Bug 10542 - stb - open - new | 12:19 |
| mantisbot | New bug: mysql_real_escape_string used without connection id - http://www.mantisbt.org/bugs/view.php?id=10542 | 12:19 |
| nuclear_eclipse | morning all | 12:29 |
| dhx_m | nuclear_eclipse: hi | 12:31 |
| dhx_m | DaniW: not sure... I don't think it is a customisable feature | 12:31 |
| dhx_m | DaniW: actually it isn't... and it wouldn't make sense | 12:32 |
| dhx_m | DaniW: maybe you're talking about the state of versions of a project (released, obsolete)? | 12:32 |
| dhx_m | I can see where you might want to use Mantis for lots of short time limited projects | 12:32 |
| dhx_m | although it'd be a lot of work to get Mantis to work like that | 12:33 |
| dhx_m | as it doesn't seem it was built that flexibility from day one | 12:33 |
| nuclear_eclipse | 06:13 < thraxisp> DaniW: see http://www.mantisbt.org/manual/manual.customizing.mantis.customizing.status.values.php in | 12:33 |
| nuclear_eclipse | the manual. | 12:33 |
| dhx_m | nuclear_eclipse: I think he wanted to have statuses for projects, not individual bugs? | 12:34 |
| nuclear_eclipse | just want to make sure he saw that link first | 12:34 |
| dhx_m | maybe I'm interpreting wrong :) | 12:34 |
| dhx_m | yep | 12:34 |
| nuclear_eclipse | projects don't really have 'state' in the first place.... | 12:34 |
| dhx_m | nah, that's what I was saying | 12:34 |
| dhx_m | although they *could*, depending on your use of Mantis | 12:35 |
| dhx_m | ie. you run lots of 3 month long projects in a company and you want to use the same tool to handle all of them | 12:35 |
| dhx_m | maybe not 3 months... 2 years maybe | 12:36 |
| DaniW | dhx_m: yes, 1 mantis for all my projects (short time projects) | 12:36 |
| dhx_m | so you have a reason to use versions, categories as intended | 12:36 |
| dhx_m | DaniW: you could hack around it by having one project with 1 category per project | 12:38 |
| dhx_m | what I mean is you might be running 4 3-month projects.... A thru D | 12:38 |
| dhx_m | so in Mantis you'd have "My Project" (whatever name) and under that, 4 categories A thru D where you file tickets | 12:39 |
| dhx_m | this is a big hack workaround though! :o | 12:39 |
| mantisbot | New bug: Bug 10543 - oberger - open - new | 12:39 |
| mantisbot | New bug: Proposal: Relationships to external bugs in remote bugtrackers - http://www.mantisbt.org/bugs/view.php?id=10543 | 12:39 |
| dhx_m | wow, that sounds nice... sounds like they're going to implement that themselves? | 12:40 |
| dhx_m | I always liked how Launchpad had support for external links to other bugtrackers | 12:40 |
| DaniW | i want to create a project for each of my TYPO3-Websites (customer websites), i can use versions for each new release (Website 2009, 2010 and so on), but a project should consists of many subprojects (Extension for something, Extension for another thing, ect.) each of this sub projects should have a state as described above | 12:40 |
| dhx_m | it sounds like you're breaking things up into chunks that are too small? | 12:43 |
| dhx_m | how many tickets do you expect in each project? | 12:43 |
| DaniW | 15-250 per sub-project | 12:44 |
| dhx_m | I agree the idea the subprojects is a good idea | 12:44 |
| dhx_m | ohhh | 12:46 |
| dhx_m | so it seems Mantis might just be able to do this | 12:46 |
| dhx_m | I wasn't even aware | 12:46 |
| dhx_m | $g_project_status_enum_string is what you're after | 12:48 |
| dhx_m | see config_defaults_inc.php for an example of how to change it | 12:48 |
| dhx_m | Mantis gets much cooler the more I look into it :D | 12:49 |
| nuclear_eclipse | dhx_m: also check bug 9940 ;) | 12:50 |
| mantisbot | Bug 9940 - jreese - open - new | 12:50 |
| mantisbot | Create on Integration Plugin for Launchpad - http://www.mantisbt.org/bugs/view.php?id=9940 | 12:50 |
| dhx_m | nuclear_eclipse: very nice :) | 12:51 |
| dhx_m | I wonder what they mean when they say upstream work is scoped for Mantis integration into Launchpad (from their end)? | 12:51 |
| dhx_m | I thought it'd already be possible via SOAP? | 12:52 |
| nuclear_eclipse | good question; I'm assuming that just means that I've created a report for it :P | 12:52 |
| dhx_m | :) | 12:52 |
| dhx_m | nah but your ticket is to integrate Launchpad with Mantis... not Mantis into Launchpad | 12:53 |
| dhx_m | if that makes any sense | 12:53 |
| dhx_m | if I understand correctly? | 12:53 |
| nuclear_eclipse | yes, basically | 12:53 |
| dhx_m | oh I see, that ticket is for creating a plugin *for* Launchpad, not for Mantis | 12:54 |
| nuclear_eclipse | but a "LaunchpadIntegration" plugin could potentially handle communication in both directions.... | 12:54 |
| dhx_m | yep | 12:54 |
| dhx_m | I'd probably argue for a split though | 12:55 |
| nuclear_eclipse | I'd argue, period :P | 12:55 |
| dhx_m | :D | 12:55 |
| dhx_m | the one thing I *really* like about Trac is their source code browser :) | 12:56 |
| dhx_m | although I gather it is still primitive (not so good for DVCS) | 12:56 |
| dhx_m | DaniW: did you get my message about $g_project_status_enum_string ? | 12:58 |
| * nuclear_eclipse is off to a meeting | 12:58 | |
| dhx_m | ok cya :) | 12:59 |
| dhx_m | I'll get paul___ to break some stuff while you're gone? :) | 13:00 |
| DaniW | dhx_m: $g_project_status_enum_string is not in config_defaults_inc.php (1.1.7) | 13:03 |
| DaniW | are you talking about a beta version? | 13:05 |
| dhx_m | DaniW: oh you're right, I'm talking about the latest development version from git master | 13:05 |
| dhx_m | DaniW: seems it was a feature added just recently | 13:05 |
| dhx_m | 1.2.x is *well* worth the upgrade | 13:05 |
| DaniW | for productive useage? | 13:06 |
| DaniW | can i keep my 1.1.7 data? | 13:06 |
| dhx_m | yeah, Mantis always has an upgrade path | 13:07 |
| dhx_m | even for development versions | 13:07 |
| dhx_m | I use it in production OK | 13:07 |
| DaniW | how to update? | 13:07 |
| dhx_m | but I'm also not traditional in the stable vs unstable debate | 13:07 |
| DaniW | update to 1.2.0a3? | 13:08 |
| dhx_m | I tend to be on the side of the argument that favours the newest version available... where you manually test the code yourself | 13:08 |
| dhx_m | 1.2.0a3 should do what you want to do... but from what I just said, you may as well get the latest git master copy | 13:08 |
| dhx_m | rule 1) backup EVERYTHING before you perform any upgrade | 13:09 |
| DaniW | git master copy? | 13:09 |
| dhx_m | rule 2) test everything thoroughly before going live with the new version | 13:09 |
| DaniW | ok | 13:09 |
| dhx_m | git master copy... click the first instance of "snapshot" @ http://git.mantisbt.org/?p=mantisbt.git;a=summary | 13:09 |
| dhx_m | I do warn you that development builds aren't always stable | 13:10 |
| nbkhwjm | is there a config option to modify the email contents, or is editing the code required?? | 13:10 |
| dhx_m | but you've got to upgrade anyway, and my theory is that if you're testing thoroughly, you will benefit more from the features/fixes in the latest development build than you will lose out from a few new bugs introduced | 13:11 |
| DaniW | how to update? copy files , that´s it? | 13:12 |
| dhx_m | also if you're following the development release carefully, you're more likely to get developer support, and patches will get to you a lot quicker when you do find/fix a problem :) | 13:12 |
| dhx_m | 1) back up your database (lock it first to prevent edits during the backup) | 13:12 |
| dhx_m | 2) back up your existing Mantis files on your server | 13:13 |
| dhx_m | 3) untar the latest snapshot to a new directory | 13:13 |
| dhx_m | 4) redo config_inc.php to your liking (you can use your old config as a guide... but follow config_defaults_inc.php in the latest release) | 13:14 |
| dhx_m | 5) visit your new mantis install, it'll tell you the database schema is out of date and you need to upgrade | 13:14 |
| dhx_m | 6) upgrade the database schema and login... now you just have the long task of configuring the latest version of Mantis :) | 13:14 |
| dhx_m | disabling features you don't want, changing the enum levels for the project statuses, etc | 13:15 |
| DaniW | ok, thanks | 13:16 |
| DaniW | backup is running... | 13:16 |
| dhx_m | keep that backup safe :) | 13:17 |
| dhx_m | and make sure you do in house testing before going live | 13:17 |
| dhx_m | so you know it works as intended | 13:17 |
| DaniW | ok, thanks | 13:18 |
| dhx_m | the other thing you'd need to do is keep track of any security problems that may arise in Mantis | 13:18 |
| dhx_m | so you know when you are forced to patch Mantis yourself | 13:18 |
| dhx_m | (or update your installation to a new development version) | 13:18 |
| DaniW | mantis is an internal system in our company | 13:18 |
| dhx_m | using unstable software transfers a lot of work onto you | 13:19 |
| dhx_m | it isn't so bad for web scripts | 13:20 |
| dhx_m | (because updates aren't usually managed as part of package managers) | 13:20 |
| DaniW | yes, but the other way is NOT to use mantis (because 1.1.7) do not fits to our needs | 13:20 |
| dhx_m | yeah, I'm just putting it out there that you really need to do things TheRightWay(TM) | 13:20 |
| dhx_m | which you should be doing anyway if you use stable software | 13:21 |
| dhx_m | but the implications of not backing up/testing before going live with an upgrade are far worse if you're using "unstable" software | 13:21 |
| dhx_m | a lot of people won't back up their databases prior to an upgrade | 13:21 |
| DaniW | i understand | 13:21 |
| dhx_m | and they'll overwrite files in their wwwroot directly during an upgrade, with no testing at all | 13:22 |
| dhx_m | you can still use the "if it isn't broken, don't break it" rule after you've got it running successfully :) | 13:22 |
| dhx_m | formally I think you'd call the approach you're doing now http://en.wikipedia.org/wiki/Rolling_release | 13:24 |
| dhx_m | ... but it'd be a standard release method if you're applying patches on top of your install, instead of upgrading to the latest version | 13:25 |
| nbkhwjm | i cant imagine anyone upgrading without a backup...!! | 13:26 |
| dhx_m | they do... all the time :( | 13:26 |
| dhx_m | lazy people heh | 13:26 |
| dhx_m | most don't even know what the word "backup" means | 13:26 |
| nbkhwjm | I manage 20 internal production sites and i do a (1) test code on Test server, (2) then move to a test site on the same server, then (3) flip over to the new site while leaving the old intact. | 13:27 |
| dhx_m | yep, that's the right way of doing it :) | 13:28 |
| nbkhwjm | then if its broke, we just flip back to the original.... | 13:28 |
| dhx_m | you can't always flip back though if you're modifying data with the new "broken" software | 13:28 |
| dhx_m | and you also can't just port those data modifications from the new version back to the old stable one | 13:28 |
| dhx_m | you get data loss that way | 13:29 |
| nbkhwjm | you can if you define a second copy of the DB tables, then normalize later... | 13:29 |
| dhx_m | but what if the new version does something dramatically wrong like forgetting to write some data to the DB? | 13:29 |
| dhx_m | people think they've entered information, but it is missing | 13:29 |
| nbkhwjm | there is a chance to loose data always, but its better that 2000+ developers who have stopped working | 13:29 |
| dhx_m | yeah :) | 13:30 |
| dhx_m | just saying that switching back isn't always something that can be done easily | 13:30 |
| nbkhwjm | cant he email text be modified by a config or only code mod?? | 13:30 |
| nbkhwjm | i agree about switching back, its not trivial at all... | 13:30 |
| dhx_m | ah sorry forgot to reply to that question... | 13:32 |
| dhx_m | you can change strings appearing in emails with custom_strings | 13:33 |
| DaniW | i get error messages: | 13:33 |
| dhx_m | but I think Mantis will force a few things for you, like dumping the history of a bug in each email | 13:33 |
| dhx_m | DaniW: forgot to mention you need PHP 5.1+ | 13:34 |
| DaniW | Notice: date_default_timezone_set() [function.date-default-timezone-set]: Timezone ID '' is invalid in [...]core/user_pref_api.php on line 173 | 13:34 |
| nbkhwjm | K, im looking at email_api.php... what i need to to remove any links to the bug system and insert links to another server... | 13:34 |
| nbkhwjm | heres the background.. we have the production bug system, but end users submit bugs to another webserver and we crank them in mantis by writing to the tables directly... (i know not ideal) | 13:35 |
| dhx_m | DaniW: there was a recent upgrade to Mantis that added the ability for users to set their own timezones, so I guess you just found a bug | 13:35 |
| dhx_m | DaniW: you may have to manually modify your user table in the database to set the timezone ID to a valid number | 13:35 |
| DaniW | PHP Version 5.2.9 | 13:35 |
| dhx_m | DaniW: that version is fine, let me get a query ready for you to try... | 13:35 |
| nbkhwjm | but when we answer a bug in mantis, we cannot send notification to the reporter, because it directs them to the mantis system and not this intermediate server... | 13:35 |
| dhx_m | paul___: heads up for later... <DaniW> Notice: date_default_timezone_set() [function.date-default-timezone-set]: Timezone ID '' is invalid in [...]core/user_pref_api.php on line 173 | 13:36 |
| nbkhwjm | we allow many different systems to submit bugs in this way, then the bug submission is "internal" to them, but centralized for us... (make sense?) | 13:37 |
| dhx_m | DaniW: did you upgrade the database schema? | 13:38 |
| dhx_m | nbkhwjm: yep that makes sense | 13:39 |
| dhx_m | nbkhwjm: so you have multiple access URLs? | 13:39 |
| nbkhwjm | yes... | 13:39 |
| nbkhwjm | reporters are added to the central mantis, but not allowed to login. | 13:40 |
| dhx_m | nbkhwjm: that may be a problem that needs the use of a transparent proxy in the middle to rewrite URLs? | 13:40 |
| dhx_m | maybe even mod_rewrite could fix it? | 13:40 |
| dhx_m | actually I guess not | 13:40 |
| nbkhwjm | windows hosted systems :^( | 13:40 |
| dhx_m | Mantis will still push out only one type of URL | 13:40 |
| nbkhwjm | can i just remove the url... | 13:41 |
| dhx_m | yeah that'd be easiest I guess | 13:41 |
| dhx_m | but there are lots of places to do that | 13:41 |
| dhx_m | password recovery, notifications, etc | 13:41 |
| dhx_m | maybe you could hack the function in Mantis that is the last step before sending an email | 13:41 |
| nbkhwjm | no need for PW recovery only notifications about bug updates entered into mantis by developers... | 13:42 |
| dhx_m | so it searches and replaces the URL | 13:42 |
| dhx_m | but that is quite a nasty workaround | 13:42 |
| nbkhwjm | yes, i hate to hack on it, then my upgrade path is terrible and unstable... | 13:42 |
| dhx_m | yep, at least with my proposal (as ugly as it is) it'd only affect one function | 13:43 |
| dhx_m | and wouldn't require mantis-wide changes | 13:43 |
| nbkhwjm | are there any discussions about custom email, if I wirte something could it be merged?? | 13:43 |
| dhx_m | I can't find any at http://www.mantisbt.org/bugs/ | 13:45 |
| dhx_m | I'm not sure if it is possible to run Mantis with $g_path set to a relative URL? | 13:45 |
| nbkhwjm | or at least exchange $g_path in the mail function to another var... | 13:46 |
| dhx_m | nbkhwjm: it seems you might be able to just set $g_path to a relative URL | 13:46 |
| dhx_m | no trailing / | 13:47 |
| dhx_m | oh wait | 13:47 |
| dhx_m | let me verify | 13:47 |
| dhx_m | trailing / required | 13:48 |
| nbkhwjm | $g_path is used in new account creation also, so changing it would affect users on the main system also.. ill dig into the bugnote and other funcs to see what i can do.. | 13:48 |
| nbkhwjm | the important thing is that there ISNT a config option... | 13:49 |
| dhx_m | better idea... | 13:49 |
| dhx_m | (maybe) | 13:49 |
| nbkhwjm | k shoot | 13:49 |
| dhx_m | in config_inc.php, set $g_path based on the current PHP headers | 13:49 |
| dhx_m | so grab the Hostname: HTTP field from the client | 13:49 |
| dhx_m | and append the appropriate path to Mantis | 13:50 |
| dhx_m | you can write whatever PHP you like in config_inc.php :) | 13:50 |
| dhx_m | so it could even be as ugly as an if/else clause | 13:50 |
| dhx_m | so set $g_path differently according to whatever factor you like | 13:50 |
| dhx_m | *to set | 13:50 |
| nbkhwjm | IC | 13:51 |
| dhx_m | that way you can maintain multiple URLs and keep them distinct from each other at once | 13:51 |
| dhx_m | *however* you may need to turn off the bugnote linking to other bugs ability | 13:51 |
| dhx_m | ie. #xxx creating a hyperlink to bug xxx | 13:52 |
| dhx_m | Mantis probably stores that as a full text link to the bug... leaking your secret URLs | 13:52 |
| dhx_m | "secret" :) | 13:52 |
| DaniW | dhx_m: sorry for my late response - i had a meeting | 14:16 |
| DaniW | database schema was updated | 14:16 |
| dhx_m | DaniW: ok np, but the error remains? | 14:17 |
| DaniW | np? | 14:18 |
| DaniW | yes, error remains | 14:18 |
| dhx_m | np - no problem | 14:19 |
| dhx_m | hmm ok | 14:19 |
| DaniW | this error only exists if i am loged in as a user with has 'Berlin' as Timezone | 14:20 |
| DaniW | e.g. Amsterdam works | 14:20 |
| dhx_m | oh ;/ | 14:20 |
| dhx_m | how odd | 14:20 |
| dhx_m | I guess you can't change it on the user which is broken? | 14:21 |
| faouzi | salut | 14:21 |
| DaniW | yes, via mantis | 14:21 |
| dhx_m | salut faouzi :) | 14:21 |
| faouzi | est ce que ya quelqu'un qui parle en français loll | 14:21 |
| faouzi | jsalut | 14:21 |
| dhx_m | je ne parle pas francais? :D | 14:22 |
| faouzi | mdr | 14:22 |
| faouzi | oki | 14:22 |
| dhx_m | did that make sense? :) | 14:22 |
| faouzi | j'ai une question!! | 14:22 |
| dhx_m | DaniW: ah, so you tried changing it manually via the database? | 14:22 |
| faouzi | je suis null en anglais dsl | 14:22 |
| dhx_m | faouzi: I only speak English :) | 14:23 |
| faouzi | oki | 14:23 |
| faouzi | i have a question | 14:23 |
| DaniW | no, via mantis (german lables): Konto / Einstellungen ändern | 14:23 |
| faouzi | can I find a plugin for CVS included in Mantis???????????? | 14:24 |
| DaniW | but i have some other errors too: APPLICATION WARNING #300: Zeichenkette 'minutes' nicht gefunden. | 14:25 |
| DaniW | APPLICATION WARNING #300: Zeichenkette 'seconds' nicht gefunden. | 14:25 |
| DaniW | APPLICATION WARNING #300: Zeichenkette 'manage_columns_config' nicht gefunden. | 14:25 |
| DaniW | APPLICATION WARNING #300: Zeichenkette 'timezone' nicht gefunden. | 14:25 |
| DaniW | Zeichenkette = string | 14:25 |
| dhx_m | DaniW: try setting the timezone in the database to "Europe/Berlin" | 14:25 |
| faouzi | dhx_m : can I find a plugin for CVS included in Mantis | 14:26 |
| faouzi | ? | 14:26 |
| dhx_m | faouzi: SourceIntegration does SVN and Git | 14:26 |
| dhx_m | faouzi: no CVS support AFAIK (because it is too old for anyone to still be using I imagine :p) | 14:27 |
| dhx_m | faouzi: it'd be trivial to write a plugin yourself for SourceIntegration that lets you use CVS... I think | 14:28 |
| DaniW | dhx_m: changed via PhpMyAdmin=> works, but if a user change it afterwards via mantis => error | 14:28 |
| dhx_m | faouzi: see http://git.mantisforge.org/w/source-integration.git | 14:28 |
| dhx_m | DanniW: hmm does the database get updated when the user tries to change it? | 14:29 |
| faouzi | dhx_m :yes, but I did not manage to install it. | 14:29 |
| DaniW | yes: empty | 14:29 |
| dhx_m | DaniW: and what option did you select from the dropdown list? Was it just "Berlin" under the category "Europe"? | 14:30 |
| DaniW | but only for Berlin | 14:30 |
| dhx_m | hmm | 14:30 |
| DaniW | yes | 14:30 |
| dhx_m | maybe you can't change it to the same/existing value? | 14:30 |
| DaniW | mantis html form is correct: <option selected="selected" value="Europe/Berlin">Berlin</option> | 14:31 |
| DaniW | but stored as '' (empty) | 14:32 |
| DaniW | no, when selecting 'Europe/Amsterdam' -> save -> select 'Europe/Berlin' -> save => error (empty value in database) | 14:33 |
| faouzi | thanks dhx_m | 14:34 |
| faouzi | dhx_m : Is it possible to change the code does SourceIntegration SVN and Git to fit CVS | 14:36 |
| faouzi | ??? | 14:36 |
| dhx_m | faouzi: yes, but you'd need to write a new plugin for SourceIntegration for CVS | 14:36 |
| dhx_m | faouzi: do you use ViewCVS? | 14:36 |
| dhx_m | DanniW: hmmm interesting, let me check | 14:36 |
| faouzi | dhx_m : no | 14:37 |
| dhx_m | faouzi: you'd need some sort of web accessible repository browser AFAIK | 14:37 |
| dhx_m | faouzi: and your plugin would call the 'cvs' command line utility to pull in new commits | 14:38 |
| faouzi | dhx_m : AFAIK??? | 14:38 |
| dhx_m | faouzi: or if CVS supports event hooks, you can push them into Mantis that way | 14:38 |
| dhx_m | faouzi: as far as I know | 14:38 |
| faouzi | dhx_m : is that you have a document that explains what you tell me, please | 14:40 |
| dhx_m | DaniW: <?php print_timezone_option_list( $t_pref->timezone ? $t_pref->timezone : config_get_global( 'default_timezone' ) ) ?> | 14:41 |
| dhx_m | DaniW: basically, set $g_default_timezone = "Europe/Berlin"; in config_inc.php | 14:42 |
| dhx_m | I think | 14:42 |
| dhx_m | faouzi: general overview @ http://leetcode.net/blog/2009/01/integrating-git-svn-with-mantisbt/ | 14:42 |
| dhx_m | faouzi: but there is no "how to write a plugin" guide from what I know... you' d have to copy the existing plugins to see how it works | 14:43 |
| dhx_m | DaniW: I think... not too sure anymore on what I just said :) | 14:43 |
| faouzi | dhx_m : I have already seen | 14:44 |
| dhx_m | DaniW: ah I see... in account_prefs_update.php the timezone setting is reverted to blank if it matches the default one in config_inc.php | 14:45 |
| dhx_m | DaniW: I have the fix... one line change... 1sec | 14:46 |
| dhx_m | DaniW & paul___ : user_pref_api.php:173 should be: | 14:48 |
| faouzi | dhx_m : thanks for you | 14:48 |
| MaximB | I've just installed mantis , how can I access it via web ? do I need to edit some files first ? | 14:48 |
| dhx_m | date_default_timezone_set( $row['timezone'] ? $row['timezone'] : config_get_global( 'default_timezone' ) ); | 14:49 |
| dhx_m | DaniW: please retry with that line 173 changed to what I suggested | 14:49 |
| dhx_m | DaniW: you can expect that fixed soon :) | 14:51 |
| DaniW | dhx_m: your fix works | 15:15 |
| DaniW | thanks | 15:15 |
| dhx_m | DaniW: great :) | 15:15 |
| DaniW | what about the other issues? (APPLICATION WARNING) | 15:16 |
| DaniW | can we talk about it in 15 hours (i´ll bw back in 15 hours) | 15:17 |
| DaniW | bw = back | 15:17 |
| DaniW | bw = be | 15:17 |
| DaniW | ;-) | 15:17 |
| dhx_m | I think that is to do with missing strings | 15:19 |
| dhx_m | because the German translation probably hasn't been updated to include the new timezone stuff | 15:19 |
| dhx_m | DaniW: so you can add the missing strings to your custom strings file to fix it | 15:20 |
| DaniW | can we meet tomorrow (15+ h) | 15:20 |
| dhx_m | ie. translate it yourself | 15:20 |
| dhx_m | yeah I'll be around :) | 15:20 |
| DaniW | bye, bye | 15:20 |
| dhx_m | or leave messages for me if I'm not | 15:20 |
| dhx_m | cya :) | 15:20 |
| nbkhwjm | dhx_m still there? | 15:54 |
| dhx_m | yep | 15:55 |
| nbkhwjm | iv'e got a solution to this email thing, let me know what you think... | 15:55 |
| nbkhwjm | i defined a couple new config vars bugnote_link_suppress and bug_link_override.. | 15:56 |
| nbkhwjm | these will be checked in email_api then use if present, this is a simple and easy method i think... WDYT? | 15:56 |
| dhx_m | sounds OK to me | 15:57 |
| nbkhwjm | then simple if ( config_get('bugnote_link_suppress)) { blah}.... | 15:57 |
| dhx_m | assuming you're not forgetting a few places where those links might appear into emails | 15:57 |
| dhx_m | yep | 15:57 |
| dhx_m | the override I'm not too sure on | 15:58 |
| nbkhwjm | yea, im doing a code search, but it seems to be all in email_api... | 15:58 |
| dhx_m | yep :) | 15:58 |
| nbkhwjm | yea i tried to use $g_bugnote_link_tag but it always uses $g_path for the prefix. | 15:59 |
| nbkhwjm | if i change g_path then i have problems all over. Since i want to only alter the outgoing email for bugs and bugnotes, it seemed better to alter it there... | 15:59 |
| dhx_m | yep, but changing $g_path as I suggested before is no go? | 16:00 |
| dhx_m | ah ok | 16:00 |
| dhx_m | I think I see what you want to do... I just assumed you wanted access to all of Mantis with different unique hostnames | 16:00 |
| nbkhwjm | then i have problems where developers need the normal mantis ui... its the users i want to force elsewhere... | 16:00 |
| dhx_m | is this for load balancing or authorisation purposes? | 16:01 |
| nbkhwjm | no only the users, we did not want the users to "crawl" all over our bug system, but to control how and what they see.. | 16:01 |
| nbkhwjm | authorisation and security... | 16:01 |
| dhx_m | why not just use inbuilt Mantis auth? | 16:02 |
| nbkhwjm | all users go to one portal to report issues with many products, each product could be from different groups, not all have the same systems. | 16:03 |
| dhx_m | ah, so they never really need to see the Mantis pages? | 16:03 |
| nbkhwjm | so to give the users a single place, while allowing different groups to maintain their bug systems, we did this.. | 16:03 |
| nbkhwjm | yes USERS never see mantis. only developers | 16:03 |
| dhx_m | wouldn't it be better to just use the SOAP interface to remotely insert stuff from users? | 16:04 |
| dhx_m | so they don't have accounts at all | 16:04 |
| dhx_m | what you're doing sounds a little dangerous in that if they find the URL... | 16:05 |
| nbkhwjm | when we built this mantis didnt have SOAP... plus there are situations where we can share a DB, but not allow web traffic... (stupid i know) | 16:05 |
| dhx_m | ok :) | 16:05 |
| dhx_m | I'd still try and lock down Mantis permissions as much as possible, that is the main protection you'll get | 16:05 |
| nbkhwjm | if they do find the url, the account has a crazy password set, no self registration and the lost password link is missing... | 16:06 |
| dhx_m | ah ok | 16:06 |
| dhx_m | no problem then | 16:06 |
| dhx_m | the URL removal is more cosmetic then | 16:06 |
| nbkhwjm | yes i know... security is an issue... | 16:06 |
| nbkhwjm | yes and to make sure they know where to go and get / submit more details... | 16:06 |
| nbkhwjm | its better than using lotus notes or some such stupid thing for bug reporting (which is what they wanted to do)... | 16:07 |
| nbkhwjm | I'll submit to mantisBT bug as a feature then see what abuse i get... :) | 16:08 |
| dhx_m | :) | 16:10 |
| dhx_m | it sounds like a legitimate cause to me | 16:10 |
| dhx_m | if you know git, it'd have much greater chance of being merged if it is attached as a git patch (signed off) | 16:11 |
| nbkhwjm | k | 16:11 |
| dhx_m | but a simple diff shouldn't be too much of a hurdle :) | 16:11 |
| dhx_m | (for devs to merge) | 16:11 |
| dhx_m | it's just when you get people attaching version 1 of a file, and version 2 | 16:12 |
| dhx_m | not in a diff format | 16:12 |
| dhx_m | DIY diff :p | 16:12 |
| nuclear_eclipse | so, what'd I miss? that backlog is much too long :P | 16:46 |
| harpreet_singh | hi all | 16:54 |
| [KK]Kirill | harpreet_singh: lo | 17:04 |
| scooby2 | Can anyone point me to the patch for allowing mantis to receive email? Google comes up with a patch for 1.2.0aX but not for 1.1.7. | 17:13 |
| nuclear_eclipse | scooby2: there's no official patch for it, but bug 4286 contains multiple comunnity contributions | 17:14 |
| mantisbot | Bug 4286 - indy - open - assigned | 17:14 |
| mantisbot | Solution for reporting via E-Mail - http://www.mantisbt.org/bugs/view.php?id=4286 | 17:14 |
| scooby2 | Do the developers ever plan to integrate this excellent feature?:) | 17:15 |
| nuclear_eclipse | it would be nice, but there's no one good way of doing it, so for the forseeable future, no | 17:15 |
| scooby2 | ok | 17:16 |
| nuclear_eclipse | one of the developers is working on a standalone python application that uses the Mantis SOAP API to handle email integration, which is likely the "best" method of doing it IMO, but it likely won't be official | 17:17 |
| scooby2 | sounds like a better plan then the current patch method | 17:19 |
| mantisbot | New bug: Bug 10544 - jonathh - open - new | 17:21 |
| mantisbot | New bug: Email bug note ordering. - http://www.mantisbt.org/bugs/view.php?id=10544 | 17:21 |
| mantisbot | New bug: Bug 10545 - nbkhwjm - open - new | 17:21 |
| mantisbot | New bug: option to make URL in email configurable, on, off ad replace - http://www.mantisbt.org/bugs/view.php?id=10545 | 17:21 |
| mantisbot | New bug: Bug 10546 - stb - open - new | 17:21 |
| mantisbot | New bug: custom avatar - http://www.mantisbt.org/bugs/view.php?id=10546 | 17:21 |
| paul___ | . | 17:30 |
| paul___ | dhx_m: lo | 17:31 |
| paul___ | nuclear_eclipse: lo | 17:31 |
| nuclear_eclipse | hi paul___ | 17:31 |
| paul___ | summary of today in here? | 17:32 |
| nuclear_eclipse | dunno | 17:32 |
| dhx_m | hey | 17:32 |
| dhx_m | summary is... | 17:32 |
| dhx_m | user_pref_api.php:173 | 17:33 |
| dhx_m | missing check for blank timezone info from the database | 17:33 |
| dhx_m | suggested to change line 173 to: | 17:33 |
| dhx_m | date_default_timezone_set( $row['timezone'] ? $row['timezone'] : config_get_global( 'default_timezone' ) ); | 17:33 |
| paul___ | yea, know about that | 17:33 |
| paul___ | anything else? | 17:33 |
| dhx_m | someone needed this feature: http://www.mantisbt.org/bugs/view.php?id=10545 | 17:33 |
| paul___ | bug 10545 | 17:34 |
| mantisbot | Bug 10545 - nbkhwjm - open - new | 17:34 |
| mantisbot | option to make URL in email configurable, on, off ad replace - http://www.mantisbt.org/bugs/view.php?id=10545 | 17:34 |
| dhx_m | someone else wanted to get CVS working with Mantis (they posted to bug 8936) | 17:34 |
| mantisbot | Bug 8936 - egoeht69 - open - acknowledged | 17:34 |
| mantisbot | SVN/CVS checkings don't notify by email - http://www.mantisbt.org/bugs/view.php?id=8936 | 17:34 |
| dhx_m | oh and more importantly... bug #10540 | 17:36 |
| mantisbot | Bug 10540 - brodriguez - open - new | 17:36 |
| mantisbot | Page redirection error - APPLICATION ERROR #18 - http://www.mantisbt.org/bugs/view.php?id=10540 | 17:36 |
| dhx_m | unchecked respose for ob_start() | 17:36 |
| dhx_m | followed by sending additional HTTP redirect headers after HTML content | 17:36 |
| paul___ | dhx_m: it's not to do with ob_start imo | 17:44 |
| dhx_m | paul___: yeah I was unsure what the problem was... definitely to do with headers being sent too late | 17:45 |
| paul___ | the problem is the warnings | 17:45 |
| dhx_m | so I figured it might be because ob_start failed to work on his server | 17:45 |
| paul___ | from in_array | 17:45 |
| dhx_m | but even so, we're still sending headers after the html is printed | 17:46 |
| paul___ | i.e. wrong data type for second argument of in_array | 17:46 |
| dhx_m | yep that too | 17:46 |
| dhx_m | I didn't even look at that | 17:46 |
| dhx_m | that error is bad, I agree... but there seem to actually be 2 errors in 1 here | 17:46 |
| paul___ | and yes, we dont check if ob_start fails | 17:47 |
| paul___ | although I'm not sure in what cases ob_start would fail | 17:47 |
| dhx_m | probably 0.0000000001% of the time if no one has reported issues yet | 17:48 |
| dhx_m | must work for everyone as Mantis seems to require the use of output buffering | 17:49 |
| dhx_m | with unlimited chunk size? :( | 17:49 |
| dhx_m | so the whole output is placed in a buffer before being sent to the client... sounds inefficient to me | 17:49 |
| dhx_m | might be part of the reason why the summary/graphs require such a large amount of memory (or maybe it is just jpgraph) | 17:50 |
| paul___ | in terms of ob_start | 17:52 |
| paul___ | from what I can tell | 17:52 |
| paul___ | the cases that it will fail are not going to get hit | 17:52 |
| paul___ | a) parameters sent to ob_start are incorrect | 17:52 |
| paul___ | b) you call ob_* functions from within ob_start | 17:53 |
| paul___ | c) you input in an object/class/whatever but without specifying the method to use | 17:53 |
| dhx_m | ah, so never... | 17:54 |
| dhx_m | it is interesting then that a warning/error would cause headers_sent() to fail | 17:54 |
| paul___ | what we need is user to change warnings to halt or whatever (i.e. halt on any error | 17:55 |
| paul___ | so we can see what in_array call is generinatg the warning | 17:55 |
| dhx_m | $g_stop_on_errors becomes redundant then? | 17:55 |
| paul___ | alternatively | 17:57 |
| paul___ | shouldn't take too long to review the 211 in_rray calls we have | 17:57 |
| dhx_m | lol | 17:57 |
| dhx_m | need a hand checking? | 17:58 |
| paul___ | db_field_exists | 18:00 |
| paul___ | config_get( 'preview_text_extensions' ); | 18:02 |
| paul___ | config_get( 'preview_image_extensions' ); | 18:03 |
| paul___ | project_get_all_user_rows | 18:05 |
| paul___ | that? | 18:05 |
| dhx_m | it was happening for him when deleting a relationship | 18:06 |
| paul___ | that's nice :P | 18:07 |
| dhx_m | did I mention this was for 1.1.7... :o | 18:07 |
| paul___ | but it's project_get_all_user_rows I believe | 18:07 |
| dhx_m | lol | 18:07 |
| dhx_m | are those 3 cases all possible culprits? | 18:08 |
| dhx_m | 4 sorry | 18:08 |
| paul___ | i'd say so :P | 18:09 |
| paul___ | I suspect it'll be project_get_all_user_rows | 18:09 |
| dhx_m | :) | 18:11 |
| paul___ | actually it's not that | 18:12 |
| paul___ | hmm :) | 18:12 |
| paul___ | could be the db_field_exists one | 18:12 |
| paul___ | probably quicker to ask user | 18:12 |
| paul___ | did they comeo n irC? | 18:12 |
| dhx_m | yeah they were here before | 18:20 |
| dhx_m | <brodriguez> | 18:21 |
| dhx_m | why not fix them all? :p | 18:21 |
| nuclear_eclipse | di giallu | 20:31 |
| nuclear_eclipse | hi* | 20:31 |
| giallu | hi | 20:32 |
| paul___ | http://secunia.com/advisories/product/5571/?task=advisories | 20:46 |
Generated by irclog2html.py