Zimbra Forums

I am using the following urls on a website to load the zimbra application and open the mail, contacts and calendar tabs inside: /zimbra/h/search; /zimbra/h/search?st=contact; /zimbra/h/calendar; after I pre-authenticate with an existing user account.

Inside the preferences of the zimbra account, if the Ajax display mode is selected instead of the HTML one, the interface of each tab is more visually appealing if you load Zimbra with the home url, which is /zimbra; and then select other tabs. However, if you load any of the above urls, a less visually appealing interface is used, even after you switch between tabs.

I would like to know what is the difference between having an url like /zimbra/h/...; and /zimbra; and if specific urls exist for each tab in the form /zimbra/...; (without the /h/ ), which would display the more appealing interface that I'm talking about.

I hope that I was clear about my problem and I would very much appreciate if someone can explain to me these differences and how to overcome them. Thanks!

I have solved the problem. Apparently, the urls needed to display the ajax interface of Zimbra are the following: /zimbra/?app=contacts; /zimbra/?app=calendar; /zimbra/?app=mail;

After searching a lot, I've found this information here: Departement Computerwetenschappen - Zimbra Calendar

Looks like you found the answer, but just wanted to elaborate more. The /h in the URL refers to the path to the HTML client, where each application is served on a separate JSP page which can be targeted via the URL path. The AJAX client only exists as a single page, so the targeting of individual applications there is done via arguments for the "app" value as you noted. Hope your problem is fixed.

Thanks a lot for the explanation. Yes, the problem is fixed.