Stanislas Kita <skita@...> writes: > Thank you for reply, I ommi the part with password and login ,
You mean omit ? If you provide sample code, you should make sure it's functional otherwise it's useless... > the probleme it's on line when i encode data in base64, when i comment this > line , it's work. Are you using the PHP built-in SOAP extension, or the legacy 'nusoap' library ? Check value of $g_mc_use_nusoap. Unless you override it in mc_config.php, it defaults to PHP extension (if it's loaded) since 1.2.13 To my (empirical) knowledge, the PHP extension as we use it does not (seem to) require base64 encoding. @rombert can you confirm ? If that's correct, I think we have a potential case of regression with apps using attachments written for api < 1.2.13, and later upgraded to 1.2.13+ without specifically setting $g_mc_use_nusoap = ON. See also http://www.mantisbt.org/bugs/view.php?id=15551 - I think it could be the same root cause. ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ mantisbt-help mailing list mantisbt-help@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mantisbt-help
