Results 1 to 2 of 2

Thread: How to troubleshoot zimlet deployment ?

  1. #1
    Join Date
    Jul 2012
    Location
    Algiers
    Posts
    55
    Rep Power
    3

    Default How to troubleshoot zimlet deployment ?

    Here are a couple of tips that were really helpful to me that I thought I'd share with others :

    * Add this to /path/to/zimbra/conf/log4j.properties

    Code:
    log4j.logger.zimbra.zimlet=DEBUG
    and restart the server via /path/to/zimbra/bin/zmcontrol restart. You'll have better debug informations in the logs if something goes wrong with the zimlet, mainly javascript errors or proxy errors.

    * Run the web client with "?dev=1" on the request to run in "Development Mode". That way, the zimlets + zimbra web client JS code won't be obfuscated and you'll get more descriptive function/parameter info than "r=e[c]".


    My zimlet deploys correctly but won't show up ?

    * log into zimbra admin
    * Check that it's listed in zimlets section
    * If it is, check that it is listed and activated for the appropriate CoS
    * If it is, check that is listed and enabled for the appropriate domain(s)
    * If it is, log into the user account, go to preferences > zimlets and see if it's not disabled at user level



    My zimlet deploys and shows up correctly but doesn't work ? firebug show a network Error 500 Compilation produced xx syntax errors


    Sometimes, your zimlet works fine in dev mode, but when you deploy it compilation may fail. Javascript compilation consists of minimizing (compressing) and obfuscating all the javascript source code files into one, small gzipped javascript file. The compression tool used by Zimbra is YUI Compressor (Yahoo's). What you should do is :

    1/ Produce a file containing all the javascript files of your zimlet (via cat *.js > all.js)
    2/ Uploaded that file to the online YUI compressor tool, found here http://refresh-sf.com/yui
    3/ compressor tool gives syntax errors along with line number

    Fix, upload and run again until you find all the errors. In my case it was the usage of the "class" as a javascript identifier, which is maybe forbidden in new javascript specs (?)


    Code:
        var component  = {
            status : "CONF",
            fb     : "B",
    >       class  : "PUB",
            allDay : 0,
            draft  : 1,
            transp : 0,
            name   : appt_details.title,
            loc    : appt_details.location,
            s      : {d:appt_details.date_start.toJSON()},
            e      : {d:appt_details.date_end.toJSON()},
            or     : {a:"ychaouche@feeder.fr", d:"yassine chaouche"}
        };
    Last edited by ychaouche; 11-28-2012 at 08:57 AM. Reason: compilation errors

  2. #2
    Join Date
    Nov 2012
    Posts
    4
    Rep Power
    2

    Default

    Thanks nice share..

Similar Threads

  1. Not sure how to troubleshoot
    By ravenswood1000 in forum Administrators
    Replies: 3
    Last Post: 01-02-2012, 10:57 PM
  2. Zimlet deployment failure
    By rd_bhatnagar in forum General Questions
    Replies: 3
    Last Post: 12-22-2009, 03:22 AM
  3. Replies: 2
    Last Post: 03-04-2009, 05:34 PM
  4. Replies: 0
    Last Post: 11-24-2008, 03:25 PM
  5. How to troubleshoot problems...
    By aceinc in forum Installation
    Replies: 9
    Last Post: 08-01-2008, 09:37 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •