View Full Version : Quercus + Wordpress 3 admin dashboard broken / doesn't render properly

05-08-2010, 01:26 PM

I've been playing around with Quercus and Wordpress 3.0

I'm attaching a screenshot of the WordPress admin dashboard not rendering properly in Firefox, to the point of being unusable. In Chrome, it seems ok.

My platform is:
- XP pro
- Java 1.6.0_18
- Tomcat 6.0.26
- Quercus 4.0.2
- Wordpress 3.0 beta 1
- MySQL 5.1.41

Any ideas?

05-12-2010, 01:10 PM

I've managed to narrow down this fault.

The issue is that Quercus + Wordpress 3 admin dashboard is broken when enabling tomcat compression in tomcat_home/conf/server.xml. With tomcat compression enabled, the wordpress dashboard is totally unusable.

IMHO, I think this is a big issue as enabling gzip over the wire is very important and I don't want to disable this for production systems.

i've posted to Mantis

05-12-2010, 01:25 PM

If the site works perfectly I would recommend excluding the admin pages from GZIP compression for the time being. You could also try and pinpoint the issue yourself using the latest svn code (I use 7119 at this moment which fixed a lot of compatibility issues for me). Another great thing you could try is use the Resin GZip filter (com.caucho.filters.GzipFilter).

Do you get any error messages or just incorrect rendering?

I see that you use Quercus 4.0.2, I prefer 4.0.3 as most stable on Drupal 6.15 + Drupal 6.16 (some issues with rendering as well, DateModule offset is incorrect but this is fixed in 7119)

Good luck!

Best regards,

05-12-2010, 05:27 PM
Hi javaguy44,

Thanks for posting the bug - that's the best way to help us keep track of the issue. As Sebastiaan mentioned, you can also try to use the Resin GZipFilter.


05-14-2010, 02:16 PM
Hi Guys,

We are talking the same thing(gzip compression) but a bit apples to oranges in how we are doing it.

I'm aware of how to use the GZIP servlet filter, but as I mentioned in my post, I'm configuring tomcat compression via server.xml and the Connector

The reason why I'm using the tomcat compression is b/c our tomcat instance is hosting 10+ webapps and counting; and its far easier to configure compression centrally as opposed to add the gzip filter in each webapp(in our case it would be retrospectively).

To my knowledge; its not possible to plug a different compression filter into the tomcat connector.

Am open to ideas if anyone has done it!