a strong suggestion from under the hood: if you happen to use wordpress + google gears + custom WP quicktags… when you update quicktag.js – don;t forget to update google gears at the sane time… or else!!
on Tribalism, Open Source and the Unexpected
tingting bilong yu…
From shisha on What comes in threes?
From David on Kickboxing @ Lae
From David on Kickboxing @ Lae
From adrian on An example of religious propaganda
From noah yalla on How to get a passport in PNG?
From Rex on Kickboxing @ Lae
From Rex on Kickboxing @ Lae
From Anon ymous on How to get a passport in PNG?
From Robert Williams on Papua New Guineans and trust
The question then becomes how to ensure the custom quicktags is updated for Gears? I’ve disabled and re-enabled Gears with WordPress and ensured the update occurred to the best of my knowledge, and yet I still get the old quicktags…unless I refresh the edit screen, then the updated quicktags appears. But I have to do that every time. I wasn’t getting any performance boost using Gears so I disabled it, but still…what’s the secret, chief?
Are you:
1) Disabling Gears.
2) Updating /wp-includes/js/quicktags.js?
3) Re-enabling Gears.
4) Downloading all files.
5) Refreshing browser cache?
This is what I have done and the added quicktags stick.
R
I actually assumed that Gears would be smart enough to realize that the quicktags.js on the server was more recent than the Gears copy on my system and update it accordingly, so I didn’t have Gears disabled while I updated, but that may have been a bad assumption on my part. (Although if you’ve got multiple users, this seems terribly inconvenient–”Hey, everybody, turn it off for five minutes, BRB.”) Thanks for the tip, tho–I’ll give it a shot.
Perhaps version 2.8 or 2.9 or….?
R