[SOLVED] Logging user bugs ???

[nicc777]

Hi - We are currently testing Zimbra for a potential massive deployement in an ISP environment. However, our testing so far pointed to some potential problems on the web browser interface (AJAX).

Where is the best place to log these or search for solutions?

Thanks

Nico

[phoenix]

Welcome to the forums.

Bugs and RFEs are filed in bugzilla and you can also post your problems here to see if anyone else has hit the same problem. If you don't find any reference to the same problems by search the forums or bugzilla please contact support and open a case.

[nicc777]

Thanks phoenix - here is a quick run down of our problem: we have several installations of Firefox on Windows and Linux, out of the box. The problem is that on some of the clients the AJAX appears to be broken some what in that drag and drop is not working, certain buttons is not working etc. The problem does not appear to be OS specific, and we do not know yet if there are something browser specific we are missing.

BTW - on the machines where it does not work on Firefox it also does not work on IE.

OS tested: Windows XP, Windows Vista, Ubuntu 7.10

Thanks

Nico

[phoenix]

Which operating system is Zimbra installed on? I assume this is the current version (5.0.4) of Zimbra that's installed and is it single server?

I'd be very surprised if those functions didn't work, the ajax client is well developed and not likely to have that sort of problems. That said, which browser versions are you using and do you have any pop-up/script blockers or add-ons that may be causing problems? We'd also need more explicit details of the problems you're describing.

[nicc777]

Server is installed on Linux OS (Centos 5).

Here is a simple test we are doing:

Test set-up:

Create more then one calendar. Book a meeting. Now try to drag the meeting from the one calendar to the other calendar.

Results:

On some Firefox browsers it works 100%. On other it doesn't (drag and drop does not work at all). As far as we can tell, the client OS and Browser is exactly the same (unless we are missing some obscure setting).

I hope that helps.

[Klug]

Beuh.

I have two laptops on my desk : one is running Vista (Pro, french) and the other is running Ubuntu 7.10 (french too).

I'm running FF2 (last stable) and FF3 (last beta) on both plus IE7 on the Vista laptop (and Safari 3.1 too).

On the desk next to mine there's an CoreDuo iMac running Tiger (french) with FF2 (last stable) and Safari (last stable).

ZCS works flawlessly on all of these platforms.
We only use the AJAX client and everything is working (d'n'd to put an email in a subfolder, d'n'd an email to the mini-calendar, d'n'd in the calendar).

Are the client OS really out of the box (with basic upgrades, obviously) ?
Nothing to interfere on the network (such as filtering or transparent proxying) ?

[Klug]

Originally Posted by nicc777

Create more then one calendar. Book a meeting. Now try to drag the meeting from the one calendar to the other calendar.

That's not _that_ basic usage 8)

Is the other calendar a shared calendar or another calendar from the same user ?

[nicc777]

Originally Posted by Klug

Nothing to interfere on the network (such as filtering or transparent proxying) ?

We sit behind a Windows proxy, but still it works on some and not on others...

We are doing some more research - if I find the solution, I will post it here. As far as I can tell, it must be settings (OS and/or Browser).

Thanks !

[nicc777]

Ok - it seems to be PROFILE related. On the same computer, one person logs on and the tests fail. If another person logs on (who's testing worked on a different computer), the test passes.

So now we are going through a step by step comparison of all our profiles. Will let you all know on this thread what we find.

Cheers

[nicc777]

We finally tracked it down to corrupt profiles. After creating a new profile and moving all mail and calendar items to the new profile, it worked 100%

The profiles in question happened to be ones we created when we just started testing, so obviously we broke something there.

Cheers