| ../irclogs/#mantishelp.2010-06-24.log | ||
| --- scribe started --- | 00:00 | |
| dhx_m | nuclear_eclipse: Python though, so not my thing :p | 01:09 |
|---|---|---|
| socorropc | hello, I recently upgraded to version 1.2.1. Installation worked fine before under 1.2rc2. Now I have problem opening issues in spite custom field is showed and required only when resolving the issue... any suggestions? | 18:39 |
| socorropc | get an error # 11 "required field ..." is empty | 18:40 |
| socorropc | another question, any way of improving queries performance? sometimes mantis take ages to save changes... installation with 1400 projects, 10 users, now has only 2500 issues and already slow... | 18:48 |
| nuclear_eclipse | 1400 projects?! | 18:50 |
| nuclear_eclipse | and only 10 users? | 18:50 |
| socorropc | yeap, being used as a call center tracking system, for client support and equipment maintenance purposes... | 18:52 |
| socorropc | projects are clients being attended... | 18:52 |
| daryn | the slowness is most likely due to trying to build a select list with 1400 project entries. | 18:52 |
| nuclear_eclipse | yeah, that's my though | 18:52 |
| nuclear_eclipse | t | 18:53 |
| daryn | we have about 40 projects, 50000 plus entries, 50 users and not slow at all | 18:53 |
| daryn | but i did notice when we loaded up the project list for testing that slowed it down quite a bit. mainly on the html rendering | 18:53 |
| socorropc | any tweaks could be done in php.ini or mysql? mantis is hosted under xampp in the local network | 18:54 |
| daryn | that problem is likely the browser client | 18:54 |
| daryn | nothing php or mysql | 18:54 |
| socorropc | what would you recommend? well projects are divided into subprojects, because are divided into a regional classification, so the region that has more subprojects has about 600... | 18:56 |
| nuclear_eclipse | socorropc: depending on your requirements, perhaps you could replace some of the project segmentation with categories or tagging | 18:57 |
| nuclear_eclipse | ie, rather than having 1400 projects, have 50-100 projects that each have a number of categories associated with them? | 18:58 |
| nuclear_eclipse | but without knowing the context of how your hierarchy is designed, it's hard to give much else as a suggestion | 18:58 |
| socorropc | i dont have a long list of 1400 projects, have about 20 projects and subprojects below them. but cannot reduce to more subprojects, since they are already divided to cities... | 18:59 |
| nuclear_eclipse | socorropc: perhaps at the city project level, rather than having subprojcets under that, you could use categories instead? | 19:01 |
| socorropc | no, because it is important to identify the client being attended at that moment... i will continue trying to enhance the code using ajax filters instead of a dropdown for subprojects... | 19:02 |
| socorropc | got another question, I recently upgraded to version 1.2.1. Installation worked fine before under 1.2rc2. Now I have problem opening issues in spite custom field is showed and required only when resolving the issue... any suggestions? got error 11, required field is empty... | 19:03 |
| nuclear_eclipse | socorropc: maybe the client's name could be a custom field? | 19:03 |
| nuclear_eclipse | rather than a project? | 19:03 |
| nuclear_eclipse | no clue about that error | 19:04 |
| daryn | nuclear_eclipse that is the error where dhx_m change the validation on the custom fields | 19:06 |
| daryn | it is pissing me off right now too | 19:07 |
| nuclear_eclipse | ok | 19:07 |
| daryn | didn't you have a discussion with him regarding that? | 19:07 |
| socorropc | the solution of custom fields for clients I have already reviewed, but the case is that I have additional custom fields to be shown depending to the client. For example, client 1 has 3 equipments being checked. So, if I choose client 1, system should show only equipments for that client... | 19:07 |
| nuclear_eclipse | daryn: if I did, I don't remember it | 19:11 |
| daryn | ok | 19:11 |
| daryn | filters? :) | 19:11 |
| nuclear_eclipse | not yet... =\ | 19:11 |
| socorropc | I have already unchecked the required when resolved, and still does not work... what should I do? go back to 1.2rc2? | 19:17 |
| socorropc | or is there any available atch I could get? | 19:18 |
| nuclear_eclipse | socorropc: iirc, 1.2.0 does not have that behavior | 19:18 |
| socorropc | are there database changes from 1.2.0 to 1.2.1 that I should fix? | 19:19 |
| nuclear_eclipse | no | 19:22 |
| nuclear_eclipse | we have a policy of not changing database schema between minor versions | 19:22 |
| socorropc | great, where is version 1.2.0 located? do you know the link? in mantisbt.org website I dont see it... | 19:23 |
| nuclear_eclipse | the download link for 1.2.1 will take you to source forge, where you'll find teh older releases | 19:23 |
| socorropc | found it, great guys, thank you very much for your time and help | 19:25 |
| nuclear_eclipse | you're welcome | 19:25 |
| John-_d | Hello All, I have searched google with no avail. When I do an export and I am using the field for date_submitted or last_updated. However, when I export these there is no timestamp on them, only a date. Is there a way to export them with the time | 20:38 |
| socorropc | hi, in version 1.2.0, I have config_inc.php variable set $g_enable_profiles = OFF; but still showing profiles, any way of disabling them? | 21:17 |
| socorropc | this feature works okay in 1.2.1 & 1.2rc2 | 21:17 |
| nuclear_eclipse | socorropc: that's one of the bugs that was fixed in 1.2.1 | 21:22 |
| nuclear_eclipse | you could find and apply the patch by hand | 21:22 |
| socorropc | great, where can I find it? | 21:23 |
| nuclear_eclipse | http://www.mantisbt.org/bugs/view.php?id=11565 | 21:24 |
| John-_d | Hello All, I have searched google with no avail. When I do an export and I am using the field for date_submitted or last_updated. However, when I export these there is no timestamp on them, only a date. Is there a way to export them with the time | 21:31 |
| socorropc | dont understand the fix, I changed $tpl_show_profiles = ON == config_get( 'enable_profiles' ); into $tpl_show_profiles = config_get( 'enable_profiles' ); but still nor working | 21:32 |
| nuclear_eclipse | socorropc: that's only part of the fix | 21:33 |
| nuclear_eclipse | http://git.mantisbt.org/?p=mantisbt.git;a=commitdiff;h=19b969e99ed0d8e5be2ee114fa814a3f7521cbe4 | 21:33 |
| John-_d | nuclear_eclipse, I know you have the answer. is it possible to export timestamps? | 21:35 |
| nuclear_eclipse | I've never used the exports, sorry | 21:35 |
| nuclear_eclipse | John-_d: a first glance at excel_xml_export.php sounds like changing $g_short_date_format in your config_inc.php should change how it exports | 21:37 |
| John-_d | thanks I will look there | 21:37 |
| socorropc | John, I have already dealed with this timestamps, there is a function in mysql to convert timestamp into datetime, I think its unixtime. The easiest way is to create a view of the data you need to export, using that command to convert dates | 21:37 |
| nuclear_eclipse | John-_d: alternatively, if you update that file to use normal_date_format instead, that would also work | 21:37 |
| John-_d | so $t_short_date_format = config_get( 'short_date_format' ); would be $t_short_date_format = config_get( 'normal_date_format'); | 21:39 |
| nuclear_eclipse | yep | 21:39 |
| John-_d | sweet thanks | 21:39 |
| John-_d | sry im pretty new at this | 21:39 |
| nuclear_eclipse | np | 21:39 |
| socorropc | nuclear_eclipse, you are great, thanks for your help, worked fine | 21:39 |
| nuclear_eclipse | socorropc: congrats :) | 21:39 |
| John-_d | damn | 21:40 |
| John-_d | this only changed the date format to SQL type | 21:40 |
| John-_d | no time | 21:40 |
| nuclear_eclipse | 00:00 you mean? | 21:40 |
| John-_d | sry I may have edited the wrong file let me try again | 21:41 |
| John-_d | nvm I am seeind this | 21:41 |
| adalwolf | sorry network problems (I am John-_d) | 21:42 |
| adalwolf | I am seeing: Date Submitted | 21:42 |
| adalwolf | 2010-06-24 | 21:42 |
| nuclear_eclipse | what export format are you using? | 21:42 |
| adalwolf | excel | 21:42 |
| nuclear_eclipse | hmm | 21:42 |
| adalwolf | isnt excel and xml the same? | 21:42 |
| nuclear_eclipse | ah ha | 21:43 |
| nuclear_eclipse | you need to edit core/excel_api.php | 21:44 |
| nuclear_eclipse | there are two instances where you'd need to change short_date_format to normal_date_format | 21:44 |
| adalwolf | sry same thing | 21:45 |
| nuclear_eclipse | =\ | 21:45 |
| nuclear_eclipse | I'm not sure then, I'm sorry | 21:46 |
| daryn | nuclear_eclipse sounds like those should be configurable | 21:46 |
| nuclear_eclipse | and I don't have Excel to test anything with, either | 21:46 |
| adalwolf | hehe no problem | 21:46 |
| nuclear_eclipse | daryn: the date formats are | 21:46 |
| adalwolf | even as CSV export id like to see it | 21:47 |
| daryn | i mean which format gets used in various places | 21:47 |
| adalwolf | on the View Issue page, that might be a good start | 21:47 |
| adalwolf | AHA!~ | 21:48 |
| adalwolf | nuclear_eclipse: Turns out I did not save the file (dumb me) that API trick worked | 21:48 |
| nuclear_eclipse | lol | 21:48 |
| nuclear_eclipse | ok | 21:48 |
| adalwolf | yay vi | 21:49 |
| adalwolf | I went to :q and it told me I hadnt saved | 21:49 |
| nuclear_eclipse | daryn: sounds to me like those fields should just default to using normal_date_format instead; I'm not sure why less info on an export is "better"? | 21:49 |
| adalwolf | is normal_date_format a php function? | 21:49 |
| * nuclear_eclipse <3 vim | 21:49 | |
| adalwolf | ya actually im using vim. tbh I hate vi but vim is nice :D I liek to use arrow keys | 21:50 |
| daryn | yeah... | 21:50 |
| adalwolf | and a quick google of normal_date_format reveals: http://www.mantisbt.org/forums/viewtopic.php?t=786 | 21:50 |
| nuclear_eclipse | short/normal_date_format are configurable strings in Mantis that get passed to php's date() function | 21:50 |
| adalwolf | gotcha | 21:51 |
| adalwolf | where do they live? | 21:51 |
| * adalwolf ducks | 21:51 | |
| nuclear_eclipse | config_defaults_inc.php | 21:51 |
| adalwolf | ty sir | 21:51 |
| nuclear_eclipse | if you want to modify them, copy them to your config_inc.php and change them there | 21:51 |
| adalwolf | gotcha | 21:51 |
| socorropc | Is there a way of showing a custom defined field when an issue is "confirmed" by the assigned user? I need the user to input that information only when that happens... | 21:54 |
| nuclear_eclipse | socorropc: not currently | 21:54 |
| socorropc | okay, so, only would work when updating the issue? | 21:55 |
| daryn | yes there is | 21:55 |
| daryn | write a custom function | 21:56 |
| socorropc | hmm how could I write one? | 21:56 |
| daryn | just a sec. it's been awhile since i wrote ours | 21:57 |
| socorropc | thanks daryn | 21:57 |
| daryn | k. the file you need to add is custom_functions_inc.php | 21:57 |
| daryn | if it isn't there already | 21:57 |
| daryn | there are default functions available | 21:58 |
| daryn | for example custom_function_default_issue_update_validate | 21:58 |
| daryn | you override that function with custom_function_override_issue_update_validate | 21:58 |
| socorropc | have not the file... | 21:58 |
| socorropc | have only custom_function_api under core folder | 21:59 |
| daryn | then the defaults are in core/custom_functions_api.php | 21:59 |
| daryn | override them in a new file named as i gave you | 21:59 |
| adalwolf | do you make a file name custom_functions_inc.php in the core or in the / | 21:59 |
| socorropc | great, I will have a look at it | 22:00 |
| daryn | in the / | 22:00 |
| adalwolf | I like the name of this function: custom_function_default_print_bug_view_page_custom_buttons | 22:03 |
| daryn | we like simple names | 22:03 |
| adalwolf | hehe | 22:03 |
| nuclear_eclipse | :P | 22:03 |
| adalwolf | at least there are nice comments | 22:03 |
| * nuclear_eclipse is glad he wasn't around for that design decision | 22:03 | |
| nuclear_eclipse | dinner time | 22:04 |
| nuclear_eclipse | cheers al | 22:04 |
| daryn | i think custom functions might be added to my list of things to review... | 22:04 |
| adalwolf | lucky | 22:04 |
| daryn | cheers | 22:04 |
| daryn | ps...don't forget to review filters | 22:04 |
| daryn | :) | 22:04 |
| adalwolf | this mantis bt is sure sweet | 22:04 |
| adalwolf | I got a lot to learn bout it tho | 22:04 |
| adalwolf | arg | 22:05 |
| adalwolf | it got angry at me making custom_functions_inc.php | 22:05 |
| adalwolf | redeclaring functions | 22:05 |
| daryn | you have to change the name to override | 22:06 |
| daryn | replace default with override | 22:06 |
| adalwolf | ill play with it later :D | 22:06 |
| daryn | have fun | 22:06 |
| adalwolf | I will :D | 22:08 |
Generated by irclog2html.py