spherical

Any other plugins related to post editing running? I’ve had a couple that messed with my code like this.

Also, do you switch back and forth between the Visual and HTML editors? Unsure if it’s better in WP3 but it wasn’t recommended to do that in earlier versions. Code gets messed up. I just turn the Visual editor off completely in Profile Settings. Life’s been a lot smoother since.

Yes. Yesterday was the renewal date.

jQuery would have to be loaded for .animate to work. *May* not make a difference but the line I use in the theme functions.php is:
<?php wp_enqueue_script('jquery'); ?>
single quotes around jquery.

As a debugging step, you might try specifically loading jquery in header.php. Use the Web Developer toolbar in Firefox to look at the JS libraries that are/aren’t loaded.

Also, I just had a go-round myself getting something to work and found that the theme footer.php was missing:
<?php wp_footer(); ?>

</body>
</html>
were missing, too, so the page wasn’t closed properly. Once those were in place, everything worked.

jCarousel or similar would be what you might need.

Check whois:

Relevant dates:
Registered on: 08-Jul-2008
Renewal date: 08-Jul-2010
Last updated: 02-Jun-2010

Registration status:
Renewal required.
*** This registration has been SUSPENDED. ***

When you say you “reset everything” what does that mean, exactly?

The BASE line should look like:
$base = '/';
unless your location is different from the norm.

The NONCE_SALT line should not go at the bottom of the file. Put it in with all of the other similar looking key lines.

Network works great.

I’ve been using google-ajax-libraries-api-plugin. Lean code – 68 lines. Works in mu-plugins/, so no site-wide or per blog activate. Even though it is vintage 2008, it plays with WP3 just fine. Moved to it when Use Google Libraries gave some trouble; can’t remember now what it was–perhaps wasn’t v3 ready at the time.

Just looked at the code of Use Google Libraries again and it has more checks/fallbacks and swaps out more libraries, so will give it another go to compare.

If your web server is set correctly, through rules in .htaccess that provide Cache-Control and/or Expires headers, jQuery is downloaded once and that’s it. All subsequent accesses on other pages get a 304 Not Modified response and no download happens, so there is no extra added to those pages at all. The browser has it cached locally. Additionally, if the Google-hosted jQuery is specified to be used instead of the one that WP installs, it is more than likely that a visitor’s browser has cached it already by visiting another site prior to visiting yours.

If you are talking about the:

Welcome to the Leading Lines tutorial section! Here you will find information on taught courses that I offer as well as a range of free on-line tutorials. Everything is aimed at making you a better photographer through clear and effective teaching. If you are just starting out I would recommend thinking about one of my beginner courses, or reading this post in the mean time. This is an area of the site that I intend expanding greatly, so sign up to the feeds to be alerted to new posts. If there is a subject that you'd like a tutorial on then let me know through the comments and I'll shuffle it up the list!

that shows up when hovering over the Tutorials menu, for instance, those are the title tags that you entered into the HREF for every

• that you have in your menu.

IT WORKS! I applied those two Trac DIFFs, as well, and all’s good so far on that front. Thanks, Andrew!

There’s a further tweak for efficiency. Read about my results here. I could use the blog traffic. ??

Hi Andrew. Thanks for the explanation and for looking at this issue. I applied the patches. We’ll see what happens.

Did DL and take a look at Core Control. There isn’t a way to modify the cronjobs but I did so using wp-crontrol; setting sub-blog theme, plugin and version checks to non-repeating, just to see if it sticks. May not, as the jobs are called by other sections of WP and they probably will reappear, but it’s worth a shot.

So you’re saying that cron is triggered by feed and spider accesses or it just looks that way? The pattern is so darn reproducible; indicating that it is the former.

I’m just trying to determine what caused the 100% CPU, physical RAM exhausted, swap space nearly full problem. The Yandex bot visited, FeedBurner vistited, wp-cron ran and BOOM 6.74 load (normal 0.00-0.35), Error Connecting to Database. This got my attention.

Update:

I revisited the setting page on the install that wasn’t emailing backups, changed a setting, committed it, changed it back to what I wanted, committed and a backup email from that database arrived this morning, along with the one from the other install. Guess it just needed a wake-up call.

Emailed DB backups are working for me on one WP3.0.1 install but not on another that is on the same server. Actually, the email never worked on the first install, which started out at WPMu v2.7 and then upgraded through each version that came along to current.

The other install started with WPMu v2.9.2 and upgraded through 3.0 to 3.0.1 and it always sent emailed backups. This alerted me to the fact that the first install wasn’t sending them. Thought that I’d not set the first install to do that but settings in both are identical.

unstyled subfolder blogs ?

force mod_rewrite to read the htaccess file ?

Completely unsure about the first and I thought that mod_rewrite read htaccess by default. That’s where it gets its rules; or do you mean make WP internal rewrites use htaccess instead? If the latter, just in case it’s needed someday, how does one tell WP to do that?

Hi Andrea.

Seems like it might be. I’m surprised no one else has noticed this. Of course, someone has to be first, I guess.

Messing around with minimizing DNS lookups after reading a thread where you instructed where to change the domain in SuperAdmin > Sites > Edit, I found that if there are CSS files out in blogs.dir/ID#/files/land that they, too, inherit the wrong Cache-Control headers; same as the images. So, it appears that anything out there suffers the same fate.