Tickets :: [#4081] API contains incorrect data type definition

6.0.0-beta1

7/30/25

Summary	API contains incorrect data type definition
Queue	Nag
Queue Version	HEAD
Type	Bug
State	Resolved
Priority	1. Low
Owners
Requester	bklang (at) alkaloid (dot) net
Created	06/26/2006 (6974 days ago)
Due
Updated	06/26/2006 (6974 days ago)
Assigned
Resolved	06/26/2006 (6974 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

06/26/2006 05:55:06 PM	Matt Selsky	Comment #4 State ⇒ Resolved	Reply to this comment
Committed to HEAD and FW_3. Thanks!

06/26/2006 03:43:51 PM	bklang (at) alkaloid (dot) net	Comment #3 New Attachment: mnemo-urn-typo.patch	Reply to this comment
Here is the mnemo patch

06/26/2006 03:43:29 PM	bklang (at) alkaloid (dot) net	Comment #2 New Attachment: kronolith-urn-typo.patch	Reply to this comment
Here is the kronolith patch

06/26/2006 03:42:59 PM	bklang (at) alkaloid (dot) net	Comment #1 State ⇒ Unconfirmed Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ API contains incorrect data type definition Queue ⇒ Nag New Attachment: nag-urn-typo.patch	Reply to this comment
I have attached a patch which contains a fix for the return type specified in nag/lib/api.php. It is currently urn:hash when it should read urn:horde. These changes are required for the SOAP WSDL to parse correctly and were suggested by Jan on #horde-dev this morning. I have attached the first patch here for nag (it's wrong in seven places) and I will be attaching two more files which correct the same issue in Kronolith and Mnemo. These errors exist in the latest tarball releases as well as CVS HEAD.