Should have mentioned that I did this also (sorry, it was late) along
with disabling Gears in Chrome. Gears was enabled for the site when
using IE 8.0 beta 2 by the way, with no problems. I also tested this in
my local Sandbox (the latest XAMPP on Windows XP SP3) with no plugins
installed at all with the exception of "WP Widget Cache" and of course,
the Amazing Grace theme...same problem as described below.
All browsers are running "Shockwave Flash 10.0 r12" and Java(TM)
Platform SE 6 U10 (required for Chrome). I was thinking along the lines
that both of these are pre-release and might be causing these anamolies
(leaning more towards the Java version causing the widgets glitch) but I
really can't quite fathom why it would manifest on Firefox and Chrome
and not on the others and why only with this one plugin and theme? I did
contact both authors last night to see if they could shed some light on
this.
Oh yeah...despite minor rendering glitches at 1024x768, I'm lovin' the
new Admin UI.
On 10/4/2008 10:02 PM, Matt wrote:
Are you using Google Gears in Firefox? If you are, try disabling it.
On Sat, Oct 4, 2008 at 6:55 PM, Kirk M<[EMAIL PROTECTED]> wrote:
On using the core auto upgrade to the latest 2.7 revision (r9082?) I've
noticed that the Widgets page is completely non-functional. The widgets page
comes up but nothing can be clicked in either the "Available Widgets" column
or "Current Widgets" column. Everything outside of these two columns still
functions correctly. [removed last line]
Anyone else seeing this?
*Update*: On further testing (arrgghh!) I've found that the Widgets page
functions correctly in IE 8.0 Beta 2 in both "Standards" and "Compatibility"
(IE 7.0 emulation) modes and Opera 9.6 beta. The Widgets page does not
function as stated originally in Firefox 3.0.3 (fresh profile) and Google
Chrome version 0.3.154.0 (Official Build 2776--latest Dev build).
The kicker to all this is that it's Vladimir Prelovac's "Amazing Grace"
theme and/or Andrew Zhang's "WP Widget Cache" that's causing this to happen
and of course I use both. It doesn't prevent either the theme or the plugin
from functioning properly nor does it throw any errors. Why this "anomoly"
happens only when using Firefox or Chrome as described above is beyond me
though.
_______________________________________________
wp-testers mailing list
[email protected]
http://lists.automattic.com/mailman/listinfo/wp-testers
_______________________________________________
wp-testers mailing list
[email protected]
http://lists.automattic.com/mailman/listinfo/wp-testers
