Tom Finley

Without a doubt, updating K2’s jQuery file (which actually has a php extension) will fix the admin AJAX issues. Just copy and paste the source of jQuery 1.7.x into this file and all will be well. I can’t supply the relative path b/c I’m on a phone, but it’s easy enough to track down if you search ‘jQuery’ within the theme folder.

Having the same issue with an old K2 theme. Everything I’ve read seems to indicate a jQuery conflict.

Same boat. I’ve seen no solutions thus far.

@sambean: Yes, I used the MT database upgrade utility. The caveat is that I use WP db-manager to carry out backups twice a week and I can rebuild any of my WP sites from scratch with a DB file and my design files within 15-30 min if needed. Luckily, it didn’t come to that. The more I look through phpMyAdmin, the more I’m convinced that the MySQL server version is what is causing issues on MT hosting — our client versions are showing 5+, but the server version being stuck at 4 has to be at the heart of this.

Set up a support request with MT to get access to their MySQL update tool. They’ll try to talk you into starting a new (gs) service, which is just nuts, but ignore that. It will upgrade you to MySQL 5.1.x and then the WP 3.2 update will finish.

It should be noted that one of the Core devs saw my Twitter exchange with MT support and wholeheartedly dismissed the possibility that their MySQL version checking was wrong. I’m not sure who to believe, but the other weird thing that happened was that the MT support rep who was helping me told me I was running MySQL 4-point-whatever. I sent them a screenshot from phpMyAdmin indicating the contrary and “upon further investigation” they then said I was running MySQL 5.0. I have my suspicions about how MT may be handling MySQL server/client versioning and it’s my theory that this is the root of the problem. They were helpful enough getting it resolved (and I must add that contacting them via Twitter and then going through the standard ticketing system speeds turnaround on resolutions dramatically).

I know this is an old post but my hope is that one of you will see it.

Frederick, thanks for adding the fragment caching capability. I’ve had some issues getting it to work, though. Primarily not knowing the proper place to put the fragment code. Admittedly I’m not the most nascent designer when it comes to php.

Using the FAQ I tried a number of places within my various php functions, but only the second method (below) prevented total breakage of the site.

<!-- mfunc -->
<?php

    // calling the header.php
    get_header();

    // action hook for placing content above #container
    thematic_abovecontainer();

?>
<!-- /mfunc -->

However, I did notice for a brief moment when pages were loading in Chrome and IE that a syntax error was being reported. The pages load normally, but still with the cached version of the theme file containing the body class of the most frequently used, and therefore cached, browser.

sareiodata, by any chance have you figured out how to do that or found a way around it in standard settings?