| ../irclogs/#mantishelp.2010-01-25.log | ||
| --- scribe started --- | 00:00 | |
| CIA-22 | Mantisbt: hickseydr * r28a23532c5a7 / (core/print_api.php lang/strings_english.txt): Fix #11429: 'Attachment missing' not translatable | 05:44 |
|---|---|---|
| CIA-22 | Mantisbt: hickseydr master-1.2.x * r4beb15aaddc3 / (core/print_api.php lang/strings_english.txt): Fix #11429: 'Attachment missing' not translatable | 05:44 |
| CIA-22 | Mantisbt: hickseydr master-1.2.x * r2f42c6a0501e / (4 files in 4 dirs): Fix #11426: Time tracking stopwatch strings not translatable | 05:59 |
| CIA-22 | Mantisbt: hickseydr * r18c520014815 / (4 files in 4 dirs): Fix #11426: Time tracking stopwatch strings not translatable | 05:59 |
| dawitaya | when I try to arrange the change status for the manage configuration to make visible only this lists (new, assigned and closed) this what I get when I press set configuration option Configuration option "status_enum_workflow " not found. | 06:11 |
| dhx_m | which version of Mantis? | 06:13 |
| dhx_m | what is the name of the page (.php file)? | 06:13 |
| dawitaya | the version mantis-1.2.x | 06:19 |
| dhx_m | and which page does this problem occur on? | 06:20 |
| CIA-22 | Mantisbt: hickseydr * r91049c219a23 /xmlhttprequest.php: Incorrect include filename in xmlhttprequest.php | 06:20 |
| dawitaya | we create plugin called Table Field and we want to arrange the status for the plugin. status eg. new, feedback, assigned, confirmed, resolved, closed I want to make only new, assigned and closed for status can I do that from manage configuration | 06:24 |
| CIA-22 | Mantisbt: hickseydr * r8bc6b668f271 / (3 files in 3 dirs): Fix #11420: 'Loading...' string for AJAX controls isn't translatable | 06:28 |
| CIA-22 | Mantisbt: hickseydr master-1.2.x * r764989fc444a / (3 files in 3 dirs): Fix #11420: 'Loading...' string for AJAX controls isn't translatable | 06:28 |
| dhx_m | status_enum_workflow is most definitely a valid configuration option, and has been for ages | 06:29 |
| dhx_m | you'd have to explain in much greater detail how one can reproduce your problem | 06:30 |
| dhx_m | because as it stands, I'm not too sure what the problem is | 06:30 |
| dhx_m | diff's of your changes, etc so we can check them for errors, etc | 06:30 |
| dhx_m | assuming you've modified Mantis' core | 06:31 |
| dhx_m | or even with plugins, it's easy to get the arguments to core functions wrong | 06:31 |
| dhx_m | ie. config_get( 'g_some_setting' ) instead of just config_get( 'some_setting' ) | 06:31 |
| dawitaya | I didn't touch the mantis code I try to modify from the plugins | 06:52 |
| alemayo | good morning :) | 07:05 |
| dawitaya | On manage columns we insert status_enum_string and we pass the values new, assigned, closed. This one works but when you open myview tickets and clickon the change status to: list button I found this (new,@02@,@03@,assigned,@04@,closed) this error and I want to hide this for new projects we create because we only need of new assigned and closed. | 07:26 |
| dawitaya | any ideas | 07:36 |
| dawitaya | can I adjust it from adm_config_delete.php because In config_default_inc.php have g_status_enum_workflow = array(); and how can I remove those enum strings | 08:28 |
| dawitaya | dhx_m ? help | 08:56 |
| kroed | Hey guys | 09:02 |
| kroed | has anyone of you ever experience the #1901 error in the 1.8.1 release of mantis? | 09:02 |
| kroed | *experienced | 09:02 |
| kroed | the "reset password" link sent out by mantis seems to be incorrect | 09:05 |
| alemayo | is there any chance that the new events we added in our branch (http://git.mantisforge.org/w/mantisbt/gtz-et.git?a=shortlog;h=refs/heads/custom-fields-events) make it into 1.2.0 ? | 11:38 |
| dhx_m | alemayo: we'd need some documentation first :) | 13:05 |
| dhx_m | alemayo: and EVENT_LANG_GET worries me a little | 13:06 |
| dhx_m | (ie. why it's needed) | 13:06 |
| alemayo | LANG_GET is mostly used in the terminolgy plugin | 13:07 |
| alemayo | but actually there were some other situation were it was necessary to overwrite some strings | 13:08 |
| alemayo | how to do that documentation ? just in the events_inc ? | 13:08 |
| alemayo | http://git.mantisforge.org/w/Terminology.git | 13:08 |
| dhx_m | why do you want to overwrite strings instead of using different strings? | 13:15 |
| dhx_m | remember of course that lang_get() uses translations from the lng/ directory | 13:16 |
| dhx_m | *lang | 13:16 |
| alemayo | we have one project that records "service requests" instead of issues :) | 13:16 |
| alemayo | it's not for our custom plugin strings .. don't worry | 13:16 |
| alemayo | the idea is to mess around with the core strings to adapt the wording of certain things | 13:16 |
| dhx_m | does your EVENT_LANG_GET handler call lang_get() to find replacement strings? | 13:17 |
| dhx_m | if so... recursion issue? | 13:17 |
| alemayo | :) | 13:18 |
| alemayo | yes it does ... | 13:18 |
| dhx_m | ah I see | 13:18 |
| alemayo | but anyway .. it uses plugin_lang get | 13:18 |
| alemayo | which it self might use lang_get --- we just should not replace plugin_.... strings | 13:18 |
| dhx_m | but you might want to replace some plugin strings | 13:19 |
| dhx_m | if you want to use your plugin with other plugins | 13:19 |
| alemayo | yes of course | 13:19 |
| alemayo | we just should not replace those strings that we actually access inside of the handler :) .. that would recurse I guess .. | 13:19 |
| dhx_m | also have to tried testing performance yet to see what effect a plugin call has on lang_get performance? | 13:19 |
| alemayo | but isn | 13:19 |
| alemayo | but isn't that a problem of all plugin handlers? | 13:20 |
| dhx_m | yep, but lang_get() is called quite frequently :) | 13:20 |
| alemayo | no, we did not do any dedicated performance tests .. | 13:20 |
| dhx_m | I can see what you're trying to do (and it makes sense to me) | 13:20 |
| alemayo | so you would accept the patch :) ? | 13:22 |
| dhx_m | possibly... with some documentation | 13:22 |
| dhx_m | and I'd want to run some performance tests on it first :) | 13:23 |
| alemayo | okay | 13:23 |
| alemayo | have fun with the performance test :-) concerning documentation, sure we'd like to help ... the question is, were shall we put it ? | 13:23 |
| dhx_m | see the docbook/ folder | 13:29 |
| dhx_m | there is a developer guide with a whole section on plugin events | 13:30 |
| alemayo | okay | 13:50 |
| alemayo | so we just write our documentation into these sgml files | 13:51 |
| alemayo | are you interested in some subcategory hack ? | 14:03 |
| alemayo | :) | 14:03 |
| alemayo | is there any plan to replace the custom field "date" with that fancy DHTML date selector that is used for due_date ? | 14:13 |
| dhx_m | not currently... I can't imagine it'd be hard to do? | 14:16 |
| dhx_m | actually, which DHTML date selector? :D | 14:17 |
| Dieterbe | hey guys. i just migrated a mantis instance (just exported database and imported it elsewhere). it mostly seems to work, however users are reporting they cannot login (even though they give the correct password) and their accounts are getting blocked | 14:23 |
| alemayo | dhx_m: for due_date fields there is some javascript date selector stuff | 14:24 |
| alemayo | Dieterbe: can anybody login ? for example administrator ? | 14:25 |
| Dieterbe | yes | 14:25 |
| Dieterbe | i can.. though i have to admit i also noticed the issue, but i just re-imported the database and it seemed to work (so maybe i just entered the wrong pass too many times) | 14:26 |
| Dieterbe | anyway, now multiple users are reporting this issue | 14:26 |
| Dieterbe | is there salting going on based on hostname or something? a grep on 'salt' did not show anything.. | 14:27 |
| Dieterbe | any idea alemayo ? | 14:31 |
| alemayo | no idea, sorry | 14:45 |
| Dieterbe | k thanks | 14:46 |
| lrojas | hi all | 16:03 |
| lrojas | is there any special steps needed or documented to upgrade a 1.1.8 installation to 1.2rc2 ? | 16:03 |
| lrojas | anybody? | 16:05 |
| nuclear_eclipse | lrojas: you should be able to just extract it, copy over the configs from 1.1.8, and visit admin/install.php to upgrade the database schema | 16:06 |
| lrojas | ok, perfect.. i will try that.. thanks | 16:07 |
| nuclear_eclipse | np | 16:07 |
| lrojas | ok that went well, thanks nuclear_eclipse | 16:28 |
| Dieterbe | what could be wrong if any new user, or existing user who used the 'get new password' feature, gets to see 'Your account may be disabled or blocked or the username/password you entered is incorrect' ? | 16:29 |
| lrojas | now for the real question... i have mantis integrated with svn, but our developers are getting swamped in email because everytime svn adds a comment mantis sends the full history of comments for the issue | 16:31 |
| lrojas | now, i dont want to stop mantis from sending email if a human adds a comment, just when svn adds a comment... is there a way to do this? | 16:32 |
| nuclear_eclipse | lrojas: you can have the devs specify a bugnote limit for notifications | 16:32 |
| nuclear_eclipse | alternately, you could alter checkin.php to disable email notifications | 16:32 |
| lrojas | let me see the code for checkin and see if is something i could alter without screwing up... thanks again for pointing me in the right direction... | 16:33 |
| lrojas | sorry to bother you nuclear_eclipse, i was looking at the code for checkin, i dont see where does it send mail notifications... could you lend me a hand in this ? | 16:37 |
| nuclear_eclipse | lrojas: just set `$g_enable_email_notification = OFF;` after the first require_once() call | 16:42 |
| nuclear_eclipse | that should be sufficient | 16:42 |
| lrojas | would that work even on 1.1.8 ? | 16:42 |
| nuclear_eclipse | probably | 16:43 |
| lrojas | ok, testing theory :) lest do the safety dance... | 16:44 |
| nuclear_eclipse | "we can dance if we want to... *clap*" | 16:46 |
| lrojas | "We can dance. We can dance. Everything's under control... *clap*" | 16:49 |
| Dieterbe | how long does it usually take for a post on the forums to get accepted? | 16:49 |
| nuclear_eclipse | Dieterbe: no clue, I'm not even sure who was access to moderate posts there | 16:49 |
| nuclear_eclipse | Dieterbe: you could always tryy posting to the mantisbt-help mailing list | 16:50 |
| atrol | there was much spam in the forum, | 17:48 |
| atrol | now the first three posts of a new user go thru moderation | 17:48 |
| atrol | after that, posting is without moderation | 17:48 |
Generated by irclog2html.py