Monday, 2009-05-11

../irclogs/#mantishelp.2009-05-11.log
--- scribe started ---00:00
mantisbotNew bug: Bug 10477 - fxm - open - new07:27
mantisbotNew bug: Migration 1.0.5 to 1.1.7: APPLICATION ERROR #700 in adm_config_report.php - http://www.mantisbt.org/bugs/view.php?id=1047707:27
mantisbotNew bug: Bug 10478 - jpp34 - open - new08:12
mantisbotNew bug: Error 500 when creating a new bug or updating a bug - http://www.mantisbt.org/bugs/view.php?id=1047808:12
michaukoHi there, I have a character encoding problem on a fresh mantis installation on Debian (packaged mantis is 1.1.6): some emails are badly encoded, some aren't ; everything seems fine from apache and mysql's point of view (and OS locales, too), anyone to try to debug this with me ? I'm running out of ideas09:01
michauk_(ok, I changed my irc client, I'm the "old" michauko)09:02
harpreet_singhhi all09:57
kenguesthttp://verens.com/?p=72913:03
mantisbotNew bug: Bug 10479 - michauko - open - new13:03
mantisbotNew bug: charset missing in some "Content-Type" email headers - http://www.mantisbt.org/bugs/view.php?id=1047913:03
nuclear_eclipse> The plugin architecture for Mantis is not yet mature13:03
nuclear_eclipsesuggestions/complaints?13:04
kenguestjust pointing this out - feel free to leave a note on kae's blog ;-)13:05
nuclear_eclipseah, it's not yours?13:05
kenguestno.13:05
nuclear_eclipseok, thanks :)13:05
kenguestguy who's currently in irc.linux.ie #phpug13:06
kenguestfeel free to pop in, if you wish ;-)13:07
michauk_bug 10479 is related to what I wrote here some hours ago, I found the explanation and a quick fix - sorry it's on 1.1.6, but it's the one packaged with Debian stable13:08
mantisbotBug 10479 - michauko - open - new13:08
mantisbotcharset missing in some "Content-Type" email headers - http://www.mantisbt.org/bugs/view.php?id=1047913:08
nuclear_eclipsemichauk_: can you please try testing against an official 1.1.7 release?  Debian's not the quickest to adopt new versions/patches, and I wonder if the problem has already been fixed or not.13:10
kenguestlo kae_verens13:15
kenguestnuclear_eclipse: kae_verens  is the guy who wrote that blog posting.13:15
nuclear_eclipsehowdy13:15
kae_verenshowya13:15
kae_verensmust rewrite the post, with a better explanation of what it does13:16
nuclear_eclipseI left a note on the post, but we can discuss it here if you like; I'm just interested to hear your feedback, comments, suggestions, and/or complaints about the plugin system, and why you feel it's not yet mature, other than of course the fact that it's still new, 1.2 isn't released, etc13:18
nuclear_eclipsebasically, how can it be improved for 1.2.0? :)13:18
kae_verensjust replied on the post. it turns out a plugin is not really appropriate for what I was trying to do, as it is supposed to be automatic. is there an RPC API available? I have not been able to find any information on it.13:22
nuclear_eclipseah, ok13:22
nuclear_eclipsethere is a SOAP API13:22
kae_verenson the plugins - basically yes, the fact that it is still new, and that there is not much documentation on it (and the fact that searching for "mantis plugins" brings me somewhere other than the mantis website) - I think that when the plugin architecture is matured a bit more (solidified, documented, and released) it may be very interesting to use13:24
kae_verensI'll dig into the SOAP API later today. I can see it mentioned in a few search queries, but no documentation yet? I don't mind digging through code to learn about it, but it's easier when there's documentation13:26
nuclear_eclipseisn't the WSDL documentation enough? :P13:26
kae_verenslol! okay, I'll give it a shot13:26
nuclear_eclipseseriously though, documentation is probably the single worst part of Mantis13:26
kae_verensSOAP would be better than how I wrote my thing anyway - I didn't like having to hook directly into the DB (and wow - that's some serious normalisation right there...)13:27
nuclear_eclipse> and wow - that's some serious normalisation right there...13:28
nuclear_eclipseis that good or bad? :P13:28
kae_verensyou're not alone there... my own projects barely have comments, let alone documentation13:29
kae_verensgood, actually - I could see why you did it - fulltext, varchars, etc being different sizes make searches a bit slower. made my own work slightly trickier, though, as I needed to figure out how the schema worked. but then - I really shouldn't have been touching the database in the first palce13:30
michauk_nuclear_eclipse: yes I know about debian's release strategy, the point is: it's commonly used by a lot of administrator who should prefer to use the packaged version (for many reasons). Thus, a lot of people should have the same problem I guess. I don't have an environment available to install a 1.1.7 right now. If you have, you can maybe just configure some account in french and send e-mails (assign bug ; reminder works) to see. No matter if you can't13:36
nuclear_eclipsemichauk_: another problem is phpmailer; in the normal release of mantisbt, we package a patched version that fixes some things, and iirc, Debian doesn't yet apply the same patches to their packages (ask aptituz, he's the Debian maintainer for mantisbt)13:38
michauk_talking about the packaged 1.1.6 version, I saw some customization that made the installation of the "plugin manager" quite weird, out-of-the-box. I don't know if this plugin and is part of the official "mantisbt" soft (I don't think so), so maybe we don't care. I can explain if needed13:40
michauk_about phpmailer (I'm not very familiar to PHP, actually), I know I just tried it via $g_phpMailer_Method =2 ; same thing13:41
michauk_(by the way, in debian, PHPMAILER_PATH was not defined, I had to add it in /etc/mantis/config_local.php: define ('PHPMAILER_PATH', '/usr/share/php/libphp-phpmailer/');13:43
nuclear_eclipsemichauk_: the "plugin manager" by deboutv is indeed unofficial, unsupported, and discouraged by us; it relies on many changes to core code, and has been known to cause many problems when trying to upgrade in the future13:44
nuclear_eclipsethere is however an official plugin system in 1.2, but it is completely incompatible with deboutv's system13:45
michauk_yes, I was wondering if the upcoming 1.2 will have an import feature (which is mandatory to my mind when you want to move to mantis with some bug history, even if it's an excel file...). I'm glad to hear that. I saw it had to modify the core.php by adding a few lines at the bottom. Once my import is done, I think i'll remove it13:46
michauk_thanks for the info13:46
michauk_anyway, considering the changes in core.php because of this plugin, I think there's no relationship with my e-mail headers problem13:48
nuclear_eclipsemichauk_: there is a XML Import/Export plugin included with 1.2, you may be interested to look into it, but there isn't any documentation afaik about the DTD it uses13:48
michauk_ok ; I'm quite old school on this: I use the package in Debian each time I can on a productive system :) as the functionnalities in 1.1.6 were OK for my mantis users, I didn't try 1.2 :)13:49
nuclear_eclipsemichauk_: I *always* use repository packages; web applications are my only exception, just because I personally find it simpler/easier to maintain and administer web apps + database without relying on Debian's management system, but I can completely understand your point of view13:51
michauk_Yes, Id do the same sometimes I've done this for wordpress :) tired of debian's release strategy for typical LAMP applications.... Maybe I should have (or I will do, don't know yet) for mantis as well13:53
nuclear_eclipseI guess my point here is that you can setup/"install" an official release off of your existing 1.1.6 package's database, at least for the purpose of testing to see if you have the same problems?13:53
michauk_yes, I'll try to find some time for this, maybe not today13:53
michauk_I'll update the issue13:53
nuclear_eclipsehowever, I do know that 1.2 has made a lot of strides towards the goal of better UTF-8 support, both in the database and in string processing, so hopefully in the future we won't have these troubles anymore...13:54
mantisbotNew bug: Bug 10480 - vivian - open - new14:19
mantisbotNew bug: xx - http://www.mantisbt.org/bugs/view.php?id=1048014:19
CIA-31Mantisbt: jreese master-1.1.x * r86ea1ec7de0b /core/custom_field_api.php: Fix #10184: Properly validate null values for custom date fields.14:20
CIA-31Mantisbt: jreese * r205681da69e9 /core/custom_field_api.php: Fix #10184: Properly validate null values for custom date fields.14:20
michauk_nuclear_eclipse: ok, on a fresh 1.1.7 from .tar.gz, it's working fine14:46
nuclear_eclipsethat's good to know :)14:46
* nuclear_eclipse yells at aptituz 14:46
michauk_:)14:46
michauk_so, either something in debian-mantis 1.1.6, either something due to pluginmanager but I don't think so - even if it modifies the core.php, it's just adds some stuff not related to emails ; furthermore, it's not all the e-mail functionnality which is not working, only some kind of e-mails, as I explained: assignment generates the problem, reminder doesn't14:47
michauk_OR maybe it's a just an old known bug in 11.6, fixed in 1.1.714:47
nuclear_eclipseI'd point to either a problem in debian's mantisbt/phpmailer, or a fix in 1.1.7 that I  can't remember :P14:48
michauk_phpmailer is the lib used when g_phpmailer_method is set to 2?14:49
michauk_because I have the same problem with method 0 & 1 : mail & sendmail14:49
nuclear_eclipsephpmailer is always sued14:50
nuclear_eclipseused(14:50
michauk_ah ok14:50
nuclear_eclipsehowever, like I said, we maintain some bugfixes in the copy of phpmailer we release with mantisbt, so it's possible that Debian hasn't picked up those patches....14:51
michauk_maybe aptituz will help14:51
michauk_I'm leaving soon, I'll come back here tomorrow, thanks14:51
nuclear_eclipseand unfortunately, phpmailer in 1.1.x is no longer the "latest" release, and with our fixes and such, we're not likely to backport the new versions to 1.1.x either...14:52
nuclear_eclipseok, cheers14:52
kae_verensnuclear_eclipse, to be honest, I actually liked what I saw of the plugin architecture. maybe it was just that there was a load of stuff that I didn't see. the documentation is probably only the tip of the iceberg - I'm sure there's a load of stuff in the source that's not there. anyway - the API will do for me. thanks for the pointer15:11
mib_paulnuclear_eclipse: I dont think we do?15:26
paulrlo18:51
nuclear_eclipsehowdy18:51
CIA-31Mantisbt: jreese * re21a1dfa72d0 /bugnote_view_inc.php: Fix inconsistencies with both the collapse area and execution of events for pages without bugnotes.19:04
slestakhola guys19:28
slestakhey, i'm using the soap connecter to expose my mantis tickets to dekiwiki (a fork of mediawiki).  The url that is formed through this method is showing me the nusoap page, and not the ticket itself in mantis19:30
slestakan example is ticket #21 is rendering as "http://mantis.commercecorp.com/api/soap/mantisconnect.php/view.php?id=21"19:30
slestakwhere i would expect it to be "http://mantis.commercecorp.com/view.php?id=21"19:31
* paulr wonders if john has gone20:30
slestakmy soap issue was a misconfiguration on te deki extension.  had the uri wrong20:45
paulrmo22:00
mantisbotNew bug: Bug 10481 - Jenolan - open - new23:11
mantisbotNew bug: Twitter notifications - http://www.mantisbt.org/bugs/view.php?id=1048123:11
harpreet_singhhi all23:58

Generated by irclog2html.py