Carl Thelen

It turns out there is _another_ way to create the same problem. I discovered this the hard way.

The directions are clear: “Add the following to your wp-config.php file in /Applications/XAMPP/xamppfiles/htdocs/wordpress/ above the line reading /* That’s all, stop editing! Happy blogging. */:”

I failed to note the bolded above, and put the lines below it. After futzing about for a bit, I re-read the instructions very carefully, discovered my error, took off my shoe, and kicked myself in the head (didn’t want to damage the shoe). I was in a bit of a hurry, and my haste made waste.

OK, I did all of the above. The errors are gone (yay!), and an initial test seems to indicate that the response time is better too. We’ll do another test tomorrow and see….

Thanks for all your help so far!

it’s got 2.00 GB RAM, hosted with a company called iPower. The Plesk control panel says,

“CPU GenuineIntel, Intel(R) Xeon(R)CPU E5410 @ 2.33GHz
Version psa v8.6.0_build86081001.10 os_Debian 4.0
OS Linux 2.6.18-028stab057.4″

among other things.

Another potentially useful bit: I turned on debugging for a little while, and got tons of “deprecated” errors. For example, “Notice: get_settings is deprecated since version 2.1! Use get_option() instead. in <filepath>functions.php on line 3237” All of the errors point to functions.php. We initially installed 3.0.1 in August (I think) and recently upgraded to 3.0.3. Do these errors imply that we’ve got out-dated plugins? Or is it possible these errors come from WP core?

Would it be useful to disable all plugins, and turn on debugging again, and see if the errors continue to come up?

Cheers!

P. S., many thanks to Andrea_r for answering so many questions!