| ../irclogs/#mantishelp.2010-01-15.log | ||
| --- scribe started --- | 00:00 | |
| cmc | hi, good evening... I have a few questions on mantis. Is it possible to show the project description in the bug report page? I want the users to look @ some details that could be stored in the project description... | 03:36 |
|---|---|---|
| dhx_m | cmc: hi, that's not too hard to do... but you'd have to hack the code yourself (or possibly write a plugin to make those changes) | 03:36 |
| dhx_m | it isn't a built in feature as such | 03:36 |
| cmc | oh right, I was wondering there could be an option in the configuration file... | 03:37 |
| dhx_m | I guess it's one of those things where everyone has a different opinion on what the bug report page should look like | 03:38 |
| cmc | do you know where can I find a tutorial on how to make a plugin for mantis? | 03:38 |
| dhx_m | we get a lot of people asking for the ability to add a disclaimer/text to the top of the bug report page | 03:38 |
| dhx_m | there's no tutorial as such... there is some documentation at mantisbt.org | 03:38 |
| dhx_m | (note: plugins are only for mantis 1.2.x) | 03:38 |
| dhx_m | and otherwise, examples at git.mantisforge.org | 03:39 |
| dhx_m | we generally add plugin events on an as-needed basis, so if they don't exist where you need them, you'd have to file a request at the official bug tracker | 03:39 |
| dhx_m | with an explanation of where you need the event triggered, why it's needed, etc | 03:39 |
| cmc | ok thanks, I was looking at that git but could not understand much either. Guess I will have to spend some more time on this... | 03:40 |
| cmc | another question... | 03:40 |
| dhx_m | actually this should be easy for you | 03:40 |
| dhx_m | we already have: | 03:41 |
| dhx_m | event_signal( 'EVENT_REPORT_BUG_FORM_TOP', array( $t_project_id ) ); | 03:41 |
| dhx_m | so your plugin would simply hook EVENT_REPORT_BUG_FORM_TOP | 03:41 |
| dhx_m | and then echo raw HTML messages (on a per-project basis in your case) | 03:41 |
| dhx_m | actually that's not entirely true... that event is meant to be for adding fields to the top of the bug report page | 03:42 |
| dhx_m | thus the event is triggered within the bug report form itself | 03:42 |
| dhx_m | so you'll see "Enter Report Details" | 03:43 |
| dhx_m | then your extra content | 03:43 |
| dhx_m | whereas you'd ideally want this text message above the "Enter Report Details" table header | 03:43 |
| cmc | ok I found the line event_signal( 'EVENT_REPORT_BUG_FORM_TOP', array( $t_project_id ) ); in bug_report_page.php | 03:49 |
| cmc | but you say I shall create a plugin to change the variable EVENT_REPORT_BUG_FORM_TOP, right? | 03:50 |
| dhx_m | not quite... EVENT_REPORT_BUG_FORM_TOP is the name of an event that is triggered when event_signal() is called | 03:51 |
| dhx_m | when that happens, the plugin system looks through the list of loaded plugins to find which ones are registered to do something on the event | 03:51 |
| dhx_m | in which event, the plugin system calls a function within the plugin to handle the event (where you can do whatever you want) | 03:52 |
| cmc | ok so, it is easier to hack the code? | 03:52 |
| cmc | and add a sql statement somewhere calling the data... | 03:52 |
| dhx_m | it's a little bit easier | 03:53 |
| dhx_m | as you don't need to learn as much about how Mantis' plugin system works | 03:53 |
| dhx_m | although... it's extremely easy after you look at some examples at git.mantisforge.org :) | 03:54 |
| cmc | I will have a look at them with some time... I will do so, thanks for the advice. I have another question, if you don't mind... | 03:54 |
| dhx_m | sure | 03:55 |
| cmc | i'm using 1.2rc2. Users are able to upload project documentation, but I'm able only to look at it as an administrator. Other users get an empty list, in spite list has data... any clues, is this some bug or just some configuration? | 03:56 |
| dhx_m | I've never used the project documentation feature I'm afraid | 03:59 |
| dhx_m | it might be best to wait around here for someone else with more knowledge on that subject to respond | 03:59 |
| dhx_m | or you could try the help mailing list? | 04:00 |
| cmc | mailing list can be found @ mantisbt.org? | 04:04 |
| dhx_m | http://www.mantisbt.org/mailinglists.php | 04:16 |
| cmc | thanks a lot for your help, have a great night | 04:23 |
| dhx_m | not a problem, cya later | 04:23 |
| alemayo | good morning | 06:25 |
| kirillka | alemayo: mo | 06:57 |
| CIA-22 | Mantisbt: vboctor * rcb5ca45521f6 /bug_change_status_page.php: Fixes #3391: Set assign_to when resolving bug. | 07:38 |
| CIA-22 | Mantisbt: vboctor master-1.2.x * rdc96dcfbafa2 /bug_change_status_page.php: Fixes #3391: Set assign_to when resolving bug. | 07:50 |
| dhx_m | paul__: your indentation commit annoys me now... when you want to backport from 1.3.x to 1.2.x, you can't just cherry-pick anymore :( | 11:18 |
| dhx_m | paul__: but it's necessary... I'm surprised there isn't an easier way in git to get around this problem | 11:19 |
| alemayo | on login_page in master-1.2.0 we get: Fatal error: Call to undefined function user_pref_get_language() in /home/am/Development/mantis/mantisbt/core/lang_api.php on line 104 | 11:30 |
| alemayo | ah okay works ... our session cookies were dirty | 11:33 |
| dhx_m | :) | 11:35 |
| CIA-22 | Mantisbt: hickseydr master-1.2.x * r45a2b5c3fa27 /core/relationship_api.php: Fix #11397: XSS with project names in relationship table | 11:35 |
| CIA-22 | Mantisbt: hickseydr master-1.2.x * r8a9f6d0593d7 /core/bug_api.php: Fix #11375: Copy list of users monitoring duplicate bug to original bug | 11:35 |
| CIA-22 | Mantisbt: hickseydr * r0995c231d401 /core/relationship_api.php: Fix #11397: XSS with project names in relationship table | 11:35 |
| CIA-22 | Mantisbt: hickseydr * r8815b9d0fe47 /core/bug_api.php: Fix #11375: Copy list of users monitoring duplicate bug to original bug | 11:35 |
| CIA-22 | Mantisbt: hickseydr * r5cd754dac3fe /bug_update.php: Improve support for multiple resolved and closed statuses (bug_update) | 11:35 |
| CIA-22 | Mantisbt: hickseydr master-1.2.x * r0d044ba08e89 /bug_update.php: Improve support for multiple resolved and closed statuses (bug_update) | 11:35 |
| alemayo | oh no .. | 11:35 |
| alemayo | looks like a bug | 11:35 |
| alemayo | require_once( 'user_pref_api.php' ); | 11:35 |
| alemayo | is missing in lang_api | 11:35 |
| dhx_m | interesting | 11:40 |
| dhx_m | 1.3.x branch? | 11:40 |
| dhx_m | ah not 1.3.x branch because I fixed it there :) | 11:40 |
| dhx_m | are you including core.php? | 11:40 |
| dhx_m | core.php loads the minimum required API of Mantis | 11:41 |
| dhx_m | as such, it needs to be included at the start of each user request/page load | 11:41 |
| alemayo | we did some first patches to the mantis core concerning new events for custom fields --- I guess we should create a fork on mantis forge and somehow push it to there? | 12:51 |
| alemayo | dhx_m: will you backport that lang-fix to 1.2.x ? | 12:55 |
| alemayo | I am confused again | 12:57 |
| alemayo | what is the difference between http://git.mantisforge.org/w/mantisbt.git and http://git.mantisbt.org/?p=mantisbt.git;a=summary ??? | 12:57 |
| dhx_m | the mantisforge one isn't official... it's just a mirror | 12:58 |
| dhx_m | which lang fix? | 12:58 |
| dhx_m | oh | 12:58 |
| alemayo | dhx_m: ah not 1.3.x branch because I fixed it there <-- | 12:58 |
| dhx_m | how can I reproduce? which function were you trying to call in lang_api? | 12:58 |
| alemayo | hm | 12:58 |
| alemayo | the error came directly after login with the master-1.2.0 version | 12:59 |
| dhx_m | do you have a plugin enabled? | 13:00 |
| alemayo | yes ... | 13:00 |
| alemayo | including our own :) | 13:00 |
| alemayo | dhx_m: concerning that git mirror at mantisforge: we cloned the mantisbt.git, switched to master-1.2.0 and now want to publish our changes --- can we just press the fork button on mantisFORGE and push it there or will we create unnecessary differences because those mirrors are out of sync? | 13:02 |
| dhx_m | what you should do is create a fork on mantisforge, setup SSH keys, etc | 13:02 |
| alemayo | that SSH key stuff is already done thanks to the ServiceLevel plugin yesterday :) | 13:03 |
| dhx_m | and like you said, push your mantisbt-1.2.x branch (and probably 1.3.x as well if you're maintaining your plugin for both stable and devel branches) | 13:03 |
| dhx_m | to mantisforge | 13:03 |
| dhx_m | ignore the mantisbt repository hosted at mantisforge | 13:03 |
| dhx_m | afaik you'll need to setup the fork in a similar way | 13:04 |
| dhx_m | alemayo: I'm not sure what to do with the require_once( 'user_pref_api.php' )... | 13:04 |
| dhx_m | the include system in the 1.2.x branch is a mess | 13:05 |
| dhx_m | which is why I overhauled it in 1.3.x | 13:05 |
| dhx_m | however I don't want to backport everything I did to 1.2.x because it likely breaks stuff | 13:05 |
| alemayo | dhx_m: just leave it :) we will fix it in our fork --- I thought it happens always, but if it just called by some plugins ... | 13:06 |
| dhx_m | is your plugin calling lang() functions directly? | 13:06 |
| alemayo | dhx_m: ignore the mantisbt repository hosted at mantisforge <-- ??? you mean I just push into my fork repo ? okay, clear | 13:07 |
| dhx_m | I hate stable/development branching (and the versioning systems to go with it)... it's so outdated | 13:08 |
| alemayo | ? | 13:08 |
| dhx_m | well... maintaining two (or more) branches of the same thing, having to backport stuff and deal with 1000 merge conflicts | 13:09 |
| alemayo | so what's better? | 13:09 |
| dhx_m | yeah what you do is create a local clone of mantisbt.org | 13:09 |
| dhx_m | then add a remote (git remote --add) for your repository on mantisforge | 13:10 |
| dhx_m | that way you can pull from mantisbt.org (to keep your local copy updated) | 13:10 |
| dhx_m | make changes, create branches, etc | 13:10 |
| dhx_m | and then push those branches to mantisforge | 13:10 |
| dhx_m | you don't really have to push a copy of mantisbt's master branch | 13:11 |
| dhx_m | just push your branches that divert from master | 13:11 |
| alemayo | mh | 13:11 |
| alemayo | okay let's do it together :) | 13:12 |
| alemayo | mantisbt/master-1.2.0-gtz is created on mantisforge already | 13:12 |
| alemayo | whenever I'd better just call it gtz I guess and do not have to include the branch name ? | 13:12 |
| dhx_m | usually yeah | 13:20 |
| dhx_m | is it too late to change it? | 13:20 |
| alemayo | no | 13:20 |
| alemayo | changed it already and told paul__ to delete the old one (I guess he is the MF-paul ?) | 13:20 |
| alemayo | so | 13:21 |
| alemayo | hm .. weired ... | 13:21 |
| alemayo | git is strange :) | 13:21 |
| alemayo | sooo I did am@am-laptop:~/Development/mantis/mantisbt$ git remote add mantisforge ssh://am-gtz@git.mantisforge.org/srv/git/mantisbt/gtz-et.git | 13:23 |
| dhx_m | yep | 13:24 |
| alemayo | $ git push mantisforge feature | 13:24 |
| alemayo | error: src refspec feature does not match any. | 13:24 |
| alemayo | error: failed to push some refs to 'ssh://am-gtz@git.mantisforge.org/srv/git/mantisbt/gtz-et.git' | 13:24 |
| alemayo | is a refspec a branch ? | 13:24 |
| dhx_m | not too sure | 13:28 |
| alemayo | he I think it worked :) | 13:31 |
| alemayo | crazy stuff that GIT :) | 13:31 |
| alemayo | I am still thinking to much SVN | 13:32 |
| dhx_m | :) | 13:36 |
| CIA-22 | Mantisbt: hickseydr * r5c727ba9ac50 /config_defaults_inc.php: Fix #11400: Increase default $g_view_configuration_threshold | 13:57 |
| CIA-22 | Mantisbt: hickseydr master-1.2.x * r589ef8ff2dc1 /config_defaults_inc.php: Fix #11400: Increase default $g_view_configuration_threshold | 13:57 |
| CIA-22 | Mantisbt: hickseydr master-1.2.x * rf3d5815f911b /config_defaults_inc.php: Fix #11395: show_queries_list should be a global option | 14:03 |
| CIA-22 | Mantisbt: hickseydr * re22eeacf9386 /config_defaults_inc.php: Fix #11395: show_queries_list should be a global option | 14:03 |
| cmc | hello good morning, I was wondering if anyone could help me solve one issue about release 1.2rc2. Users developers and up are able to upload project documents, but when trying to view it, only administrators get the list of documents. Any clues if this is a bug or a misconfiguration? | 14:08 |
| paul__ | dhx_m: manager | 16:14 |
| paul__ | . | 21:34 |
| paul__ | dhx_m: ? | 21:34 |
Generated by irclog2html.py