| CIA-22 | Mantisbt: daryn * rb4038b50a16c / (5 files in 3 dirs): Load common.js after jquery conflicts have been resolved. | 01:09 |
|---|---|---|
| CIA-22 | Mantisbt: daryn * r2dc8409eb9d5 / (3 files in 3 dirs): Remove ToggleDiv call from the html and add jquery listener. Modify to use | 01:09 |
| CIA-22 | Mantisbt: daryn * r1819bbdf8c2d / (54 files in 6 dirs): Add html_css_link function and convert hardcoded links to use the function. | 02:01 |
| *** Quits: micahg (~micah@ubuntu/member/micahg) (Ping timeout: 252 seconds) | 02:18 | |
| *** Joins: Cupertino (~Cupez@unaffiliated/cupertino) | 02:37 | |
| *** Joins: giallu (~giallu@fedora/giallu) | 02:39 | |
| *** Joins: rolfkleef (~rolf@urtica.xs4all.nl) | 03:03 | |
| *** Quits: daryn (~daryn@h16.5.170.216.ip.windstream.net) (Quit: Ex-Chat) | 03:30 | |
| *** Joins: Rixie (~Rixie@0x4dd7390e.adsl.cybercity.dk) | 03:41 | |
| *** Joins: fanno (~Morten@90.184.93.233) | 04:15 | |
| *** Joins: dhx_m (~anonymous@c122-107-185-177.eburwd5.vic.optusnet.com.au) | 04:50 | |
| *** Joins: davidinc (~d5374b0d@gateway/web/freenode/ip.213.55.75.13) | 05:17 | |
| *** Quits: siebrand (~beis@sm.xs4all.nl) () | 05:41 | |
| *** Quits: rolfkleef (~rolf@urtica.xs4all.nl) (Ping timeout: 265 seconds) | 05:52 | |
| *** Joins: rolfkleef (~rolf@82-204-82-162.fttx.bbeyond.nl) | 06:09 | |
| *** Joins: _obook (~olivier@2a01:e34:ee77:ce60:21c:25ff:fe28:c750) | 06:42 | |
| *** Quits: davidinc (~d5374b0d@gateway/web/freenode/ip.213.55.75.13) (Ping timeout: 252 seconds) | 07:12 | |
| *** Joins: davidinc (~d5374b0d@gateway/web/freenode/ip.213.55.75.13) | 07:37 | |
| *** Joins: kirillka (~Miranda@82-205-36-78.baltnet.ru) | 08:08 | |
| *** Joins: moto-moi (~hylke@cara.xs4all.nl) | 08:08 | |
| *** Joins: gunee (~wollivie@ARennes-251-1-130-249.w86-210.abo.wanadoo.fr) | 08:34 | |
| gunee | Hi everyone. Is there a way to configure Mantis so that the e-mails related to a same bug are threaded ? | 08:35 |
| Cupertino | hi davidinc | 08:45 |
| Cupertino | I see you updated reminder again | 08:45 |
| davidinc | Cupertino: hi | 08:58 |
| Cupertino | :) | 08:58 |
| davidinc | Cupertino: what can I help you/ | 08:59 |
| davidinc | ? | 08:59 |
| Cupertino | nothing m8 | 08:59 |
| Cupertino | just wanted to say hi and say i uploaded your new version | 08:59 |
| nuclear_eclipse | gunee: they should all be part of a single thread afaik, or it at least works that way in Thunderbird | 09:01 |
| davidinc | Cupertino: Cool have fun!! | 09:01 |
| *** Quits: fanno (~Morten@90.184.93.233) (Read error: Connection reset by peer) | 09:02 | |
| gunee | nuclear_eclipse: thanks for the answer. I use thunderbird though, and messages do not appear as threads. | 09:03 |
| gunee | Is it possible that the Mantis version installed on our server is buggy ? It's 1.0.0 rc 2 | 09:03 |
| nuclear_eclipse | oh | 09:03 |
| nuclear_eclipse | that's quite out of date... | 09:03 |
| nuclear_eclipse | you should *really* try to upgrade to the latest stable versions | 09:04 |
| gunee | so it seems... I'll talk to the server admin about that. What would be the recommended version ? | 09:04 |
| nuclear_eclipse | 1.2.1 is the latest stable version | 09:05 |
| gunee | ok. I'll see what I can do... | 09:06 |
| *** Joins: fanno (~b3g@193.3.95.240) | 10:03 | |
| *** Quits: rolfkleef (~rolf@82-204-82-162.fttx.bbeyond.nl) (Ping timeout: 258 seconds) | 10:18 | |
| *** Joins: micahg (~micah@ubuntu/member/micahg) | 10:33 | |
| *** Quits: kirillka (~Miranda@82-205-36-78.baltnet.ru) (Read error: Connection reset by peer) | 10:53 | |
| *** Quits: giallu (~giallu@fedora/giallu) (Ping timeout: 252 seconds) | 10:55 | |
| *** Quits: Cupertino (~Cupez@unaffiliated/cupertino) (Quit: I give up...) | 10:58 | |
| *** Quits: Rixie (~Rixie@0x4dd7390e.adsl.cybercity.dk) (Quit: Rixie) | 11:10 | |
| *** Joins: daryn (~daryn@rrcs-76-79-4-2.west.biz.rr.com) | 11:34 | |
| gunee | Hi again. I've read the documentation about e-mail notifications but I haven't really understood how to replace the $g_to_email parameter. Can someone help me ? | 11:57 |
| *** Quits: daryn (~daryn@rrcs-76-79-4-2.west.biz.rr.com) (Quit: Ex-Chat) | 12:00 | |
| *** Joins: daryn (~daryn@rrcs-76-79-4-2.west.biz.rr.com) | 12:00 | |
| *** Joins: rolfkleef (~rolf@urtica.xs4all.nl) | 12:03 | |
| nuclear_eclipse | daryn: | 12:18 |
| daryn | lo | 12:18 |
| nuclear_eclipse | gunee: add a new line in your config_inc.php with $g_to_email = "wahatever"; | 12:18 |
| nuclear_eclipse | daryn: re your jquery changes in master | 12:18 |
| daryn | ya? | 12:19 |
| nuclear_eclipse | does that maintain the existing behavior of remembering what divs a user has collapsed for future page loads? | 12:19 |
| daryn | yes | 12:19 |
| nuclear_eclipse | ok, cool, it just wasn't immediately obvious from the diffs :P | 12:19 |
| daryn | it still calls ToggleDiv, it just gets assigned from the script | 12:20 |
| *** Quits: micahg (~micah@ubuntu/member/micahg) (Ping timeout: 240 seconds) | 12:20 | |
| daryn | there is one minor bug i found when hitting the report page the Ajax object is not found and then it forgets the settings. i'll be tracking that down soon | 12:22 |
| daryn | i'm cleaning up filter changes now and piecing together the commits so hopefully you'll have something to look at real soon | 12:23 |
| nuclear_eclipse | awesome | 12:24 |
| daryn | i updated your product matrix plugin as an example as well | 12:24 |
| nuclear_eclipse | wheee! | 12:24 |
| daryn | it isn't 100% because i wasn't sure on a couple of things but at least it will give you an idea of what i'm doing | 12:24 |
| nuclear_eclipse | pvm filters are quite a workaround hack, very tightly tied to the way that mantis internals work... =\ | 12:28 |
| nuclear_eclipse | eg, using a filter to specify a set of columns to force into the current configuration | 12:28 |
| daryn | ok, well, maybe that won't be necessary now. we can talk about it once i push to forge and figure out how it should work | 12:29 |
| nuclear_eclipse | ok | 12:29 |
| nuclear_eclipse | tbh, I did it that way because I didn't like any way of integrating that as part of the core filter/plugin system | 12:30 |
| nuclear_eclipse | ie, better to have the tacky stuff in a single plugin than part of the core APIs | 12:30 |
| daryn | right | 12:30 |
| *** Quits: _obook (~olivier@2a01:e34:ee77:ce60:21c:25ff:fe28:c750) (Remote host closed the connection) | 12:44 | |
| *** Joins: AzaToth (~azatoth@wikipedia/AzaToth) | 13:07 | |
| *** Joins: siebrand (~beis@sm.xs4all.nl) | 13:09 | |
| *** Joins: micahg (~micah@ubuntu/member/micahg) | 14:02 | |
| gunee | nuclear_eclipse: thanks, but is this also valid for version 1.2.1 ? I've done what you suggested, but it doesn't seem to be working. What about the last bullet of this section http://docs.mantisbt.org/master/en/administration_guide.html#ADMIN.CUSTOMIZE.EMAIL ? | 14:43 |
| *** Quits: daryn (~daryn@rrcs-76-79-4-2.west.biz.rr.com) (Read error: Connection reset by peer) | 14:44 | |
| *** Joins: daryn (~daryn@rrcs-76-79-4-2.west.biz.rr.com) | 14:48 | |
| nuclear_eclipse | gunee: I don't see "to_email" anywhere in config_defaults_inc.php in 1.2.1, so I guess not | 14:49 |
| gunee | This is what I understood when reading the doc I pointed above | 14:50 |
| *** Joins: ultra_blue (~gogogo@129.24.112.59) | 14:51 | |
| nuclear_eclipse | unfortunately, much of the admin guide is leftover from 1.0.x and 1.1.x... =\ | 14:51 |
| ultra_blue | Hello, everybody. Mantis 1.1.8. Is there a way to prevent released versions from appearing in the Report Issues page? Thanks! | 14:52 |
| ultra_blue | In the 'Target Version' drop down. | 14:52 |
| gunee | I created an account for our bug reports mailing list, but the mailing list still doesn't receive messages. I'm not sure if I configured the mailing properties for this user correctly... | 14:53 |
| nuclear_eclipse | ultra_blue: a) that should only happen by default for developers or higher, and b) it's a configurable threshold that you could set to NOBODY | 14:53 |
| nuclear_eclipse | ultra_blue: counter intuitively, I believe $g_report_issues_for_unreleased_versions_threshold controls that | 14:55 |
| ultra_blue | nuclear_eclipse: Understood. But I often get confused about which version I'm applying an Issue to, and since we never add Issues to released versions, it would be great if they didn't appear at all. | 14:55 |
| ultra_blue | nuclear_eclipse: sweet. I | 14:55 |
| ultra_blue | 'll take a look. | 14:55 |
| ultra_blue | It looks like $g_report_issues_for_unreleased_versions_threshold controls who can assign Issues to an unreleased version. I want to hide released versions in the 'Target Version' drop down. | 15:01 |
| nuclear_eclipse | hide individual released versions, or all of them? | 15:09 |
| ultra_blue | just individual released versions. | 15:10 |
| ultra_blue | Once we release, there's no need for them appear in that list anymore. Once a release has happened, we can't add any more Issues to it. Cause it's released. | 15:11 |
| ultra_blue | ;) | 15:11 |
| nuclear_eclipse | in that case, you should be able to set the version as "obsolete", which will hide it from the various version dropdowns, as well as the roadmap/changelog, but I don't know of a way to hide individual versions from *only* the target version field, although IMO that sounds like a bug, because you shouldn't be able to set something to target a released version... | 15:11 |
| nuclear_eclipse | per chance, are you using versions inherited from a parent project? | 15:12 |
| nuclear_eclipse | nvm, inherited versions were added in 1.2 | 15:13 |
| ultra_blue | Lemme see if obsolete is an option. | 15:14 |
| nuclear_eclipse | either way, you might want to consider upgrading to version 1.2.1, first to see if it fixes the behavior, but also because it hasa lot of feature and security updates | 15:15 |
| ultra_blue | Good advice. I'll see if I can rattle the system folk chains a little. I don't see any way of setting the version to obsolete in our version. | 15:16 |
| ultra_blue | Thanks for your help! | 15:17 |
| nuclear_eclipse | ultra_blue: that might be yet another feature added in 1.2.x =\ | 15:19 |
| nuclear_eclipse | it's hard to keep track | 15:19 |
| ultra_blue | <nods> But still, you're right, we should upgrade. | 15:19 |
| ultra_blue | How painful is it? | 15:19 |
| ultra_blue | On a scale of 1-10. ;) | 15:19 |
| nuclear_eclipse | about 3 or 4, assuming you don't have any customizations to the code | 15:21 |
| ultra_blue | hardly any. | 15:22 |
| nuclear_eclipse | backup your database/install, copy configs and custom_* to the fresh 1.2.1 install, point your browser at admin/install.php to upgrade the database schema, and that should be it | 15:22 |
| ultra_blue | It took us awhile to realize that we can configure Mantis a lot, and that what comes out of the box isn't necessarily best practice but more of a guideline. | 15:23 |
| nuclear_eclipse | http://git.mantisbt.org/?p=mantisbt.git;a=blob;f=doc/INSTALL;h=e77fc6a7818d89e7ebbd748b345f3ba4b83b3c7c;hb=a6a8ed17748a91e019239beff77869c94198a232 | 15:23 |
| ultra_blue | Ha, sweet. | 15:23 |
| ultra_blue | Systems folk love short instructions. | 15:24 |
| nuclear_eclipse | I don't like writing long instructions :P | 15:24 |
| ultra_blue | Ah, that's your work? | 15:27 |
| nuclear_eclipse | yep | 15:28 |
| gunee | nuclear_eclipse: Still no idea of how to fix this problem ? | 15:28 |
| nuclear_eclipse | gunee: no, I'm not sure | 15:29 |
| nuclear_eclipse | I rarely deal withemail in mantis | 15:29 |
| ultra_blue | Ah. Well thanks again for your attention. | 15:29 |
| gunee | ok. Thanks anyway | 15:29 |
| nuclear_eclipse | ultra_blue: np, hope the upgrade works out | 15:29 |
| *** Joins: shruggar (~shruggar@5acc3e92.bb.sky.com) | 15:42 | |
| shruggar | when trying to view rss feeds for mantis, I get: "APPLICATION WARNING #403: Database field "email" not found." at the top of the xml output. I have already tried running the upgrade script under admin/, and have updated to 1.2.1 | 15:45 |
| *** Quits: micahg (~micah@ubuntu/member/micahg) (Ping timeout: 265 seconds) | 15:53 | |
| shruggar | can someone with a working install send me a mysql schema? | 15:54 |
| *** Joins: micahg (~micah@ubuntu/member/micahg) | 15:56 | |
| gunee | nuclear_eclipse: I finally managed: I created an account with the bug reports ML address, set it up as a viewer account, and then I ticked all the boxes for "viewer" in the E-mail notifications page. | 16:09 |
| gunee | It is cheesy, but it seems to be working. I wonder why the developers have decided to remove this g_to_email setting though... | 16:10 |
| gunee | And e-mails are still not threaded, but I think that comes from our mailing list system. | 16:11 |
| shruggar | apparently, somehow there were some issues with an invalid reporter_id | 16:19 |
| *** Quits: shruggar (~shruggar@5acc3e92.bb.sky.com) (Remote host closed the connection) | 16:37 | |
| *** Quits: fanno (~b3g@193.3.95.240) (Remote host closed the connection) | 16:42 | |
| *** Parts: gunee (~wollivie@ARennes-251-1-130-249.w86-210.abo.wanadoo.fr) | 16:51 | |
| *** Joins: slestak (~sromanow@63-144-86-130.dia.static.qwest.net) | 16:53 | |
| slestak | hi guys. upgradign my 1.1.6 vm to 1.2.1 I have my backups and have copied the new code to the vm. I am getting a 403 forbidden on install.php | 16:54 |
| slestak | i dont think i would need to modify my apache vhost for the upgrade. I see the permission denied in apaches error.log | 16:55 |
| *** Quits: micahg (~micah@ubuntu/member/micahg) (Read error: Connection reset by peer) | 17:05 | |
| slestak | i tried this from localhost in lynx as well as from remote browser. | 17:06 |
| *** Joins: micahg (~micah@ubuntu/member/micahg) | 17:20 | |
| *** Quits: daryn (~daryn@rrcs-76-79-4-2.west.biz.rr.com) (Read error: Connection reset by peer) | 17:28 | |
| *** Joins: fanno (~Morten@90.184.93.233) | 17:34 | |
| *** Quits: moto-moi (~hylke@cara.xs4all.nl) (Quit: Ex-Chat) | 17:43 | |
| *** Quits: PennStater (~Aaron@unaffiliated/pennstater) (Ping timeout: 240 seconds) | 18:02 | |
| *** PennStater^AtWrk is now known as PennStater | 18:02 | |
| *** Quits: rolfkleef (~rolf@urtica.xs4all.nl) (Ping timeout: 276 seconds) | 18:35 | |
| *** Joins: PennStater- (Aaron@unaffiliated/pennstater) | 18:42 | |
| *** Quits: PennStater- (Aaron@unaffiliated/pennstater) (Ping timeout: 240 seconds) | 18:50 | |
| *** Joins: PennStater- (Aaron@unaffiliated/pennstater) | 18:53 | |
| *** Quits: PennStater- (Aaron@unaffiliated/pennstater) (Ping timeout: 264 seconds) | 18:58 | |
| *** Quits: CIA-22 (cia@208.69.182.149) (Ping timeout: 260 seconds) | 19:08 | |
| *** Joins: pconrad (~pconrad@dhcp-41-207.cs.ucsb.edu) | 19:30 | |
| pconrad | Hi Everyone | 19:30 |
| pconrad | I'm trying to do some custom reporting against the SQL tables for my Mantis install | 19:31 |
| pconrad | and am wondering if anyone knows off the top of their head where the mapping between the bug status codes in the status field of mantis_bug_table and the text status codes lives? | 19:32 |
| pconrad | I'm gonna start hunting through source code in a minute, but I figured I'd ask the room first in case someone just knows off the top of their head | 19:33 |
| pconrad | One of the things I'm trying to do in my custom reports is locate bugs that are either 'resolved' or 'closed' | 19:35 |
| pconrad | I can hard code "90" and "80" in my SQL queries but I'm wondering if there is any reason not to do that... i.e. do these numbers live in a configuration file or a database table somewhere? | 19:37 |
| pconrad | I see code such as config_get( 'bug_resolved_status_threshold' ) that makes me thing that there is some mapping somewhere I might be able to look up... | 19:38 |
| pconrad | Ok, core/config_api.php seems to be the code where the thresholds are looked up | 19:43 |
| pconrad | and it seems you look first in cache, then database, then $GLOBALS | 19:43 |
| pconrad | where are the $GLOBALS set? that's what I haven't found yet | 19:44 |
| *** Quits: ultra_blue (~gogogo@129.24.112.59) (Quit: Leaving.) | 19:48 | |
| pconrad | The answer appears to be core/constant_inc.php | 19:48 |
| *** Joins: CIA-22 (~CIA@208.69.182.149) | 19:48 | |
| pconrad | That's not where $GLOBALS is defined---haven't found that yet---but it is where the relationship between "80" and "90" and "resolved" and "closed" is made | 19:51 |
| pconrad | Sounds like its ok to just hardcode 80 and 90 at least for now----can anyone at least say "yup, sounds ok"? | 19:52 |
| *** Quits: scribe9343423 (~scribe934@static.96.23.63.178.clients.your-server.de) (Remote host closed the connection) | 19:59 | |
| *** Joins: scribe9343423 (~scribe934@static.96.23.63.178.clients.your-server.de) | 20:00 | |
| *** Quits: AzaToth (~azatoth@wikipedia/AzaToth) (Remote host closed the connection) | 20:45 | |
| *** Quits: pconrad (~pconrad@dhcp-41-207.cs.ucsb.edu) (Quit: pconrad) | 20:49 | |
| *** Joins: daryn (~daryn@h148.221.31.71.dynamic.ip.windstream.net) | 20:52 | |
| *** Joins: daryn_ (~daryn@h248.133.28.71.dynamic.ip.windstream.net) | 21:27 | |
| *** Quits: daryn (~daryn@h148.221.31.71.dynamic.ip.windstream.net) (Ping timeout: 245 seconds) | 21:31 | |
| *** Joins: daryn__ (~daryn@h196.67.29.71.dynamic.ip.windstream.net) | 22:05 | |
| *** Quits: fanno (~Morten@90.184.93.233) (Read error: Connection reset by peer) | 22:06 | |
| *** Quits: daryn_ (~daryn@h248.133.28.71.dynamic.ip.windstream.net) (Ping timeout: 276 seconds) | 22:09 | |
| *** Quits: daryn__ (~daryn@h196.67.29.71.dynamic.ip.windstream.net) (Quit: Ex-Chat) | 22:26 | |
| *** PennStater is now known as PennStater^AtWrk | 22:52 | |
| *** Joins: PennStater (Aaron@unaffiliated/pennstater) | 22:53 | |
| *** Quits: micahg (~micah@ubuntu/member/micahg) (Ping timeout: 264 seconds) | 23:52 | |
Generated by irclog2html.py 2.9.2 by Marius Gedminas - find it at mg.pov.lt!