[SOLVED] Custom zimlet XML parsing error
A former employee implemented a custom zimlet called part_zimlet.zip. It worked until we went to Zimbra 5.0.x.
The purpose of the zimlet is so that if I user highlights a part number such as xxxx-xxxx, a popup displays with details of the item. The details are obtained by querying our host server.
What happens now if is a user highlights a part such as 0001-0001, the following popup displays:
XML Parsing Error: XML or text declaration not at start of entity Location: http://webmail.xxxxx.com/service/pro...0.200%2....etc
To ensure the zimlet is installed, I typed: "zmzimletctl listZimlets all". The custom zimlet does show up - "Installed Zimlet files on this host: part_zimlet".
I extracted the contents of part_zimlet.zip and it contains: config.xml, part.xsl, and part_zimlet.xml.
config.xml contains:
<zimletConfig name="part_zimlet" version="1.0">
<global>
<property name="url">http://10.9.110.200/cgi-bin/db.sh/tools/zimlet.w</property>
<property name="allowedDomains">*</property>
</global>
</zimletConfig>
part.xsl contains:
<zimletConfig name="part_zimlet" version="1.0">
<global>
<property name="url">http://10.9.110.200/cgi-bin/db.sh/tools/zimlet.w</property>
<property name="allowedDomains">*</property>
</global>
</zimletConfig>
part_zimlet.xml contains:
<zimlet name="part_zimlet" version="1.0" description="Cust">
<resource>part.xsl</resource>
<contentObject>
<matchOn>
<regex attrs="ig">[0-9][0-9][0-9][0-9][-][0-9][0-9][0-9][0-9]</regex>
</matchOn>
<toolTip>
<actionUrl target="http://10.9.110.200/cgi-bin/db.sh/tools/zimlet.w" xslt="part.xsl">
<param name="module">part</param>
<param name="keydata">${src.objectContent}</param>
</actionUrl>
</toolTip>
</contentObject>
</zimlet>
Any help in determining what is causing this error will be GREATLY appreciated.
Thanks,
Shannon
1 Attachment(s)
Re: Custom zimlet XML parsing error
To hopefully increase my chances of receiving a response, I have attached a screen shot of the XML parsing error I am receiving. I would appreciate any help as I cannot figure out why this worked up until recently, although no changes have been made to the Zimlet package.
Thanks,
Shannon