paperlion

Developed by…
Powered by WordPress

at the bottom changes between both lines displaying and one line as I refresh the screen. Maybe it’s only on my screen?

Actually, I saw a post about 1.7 and did it – seems to work okay – note that the only changes done to make 1.6 work were to WP’s own edit.php file.

I’ve got to put a plug in for the greatest webhost – Thomas at livehost.net. He found the problem Skippy, and I thought I should post it to save any future anguish. He installed a tool called mod_dosevasive that is trying to prevent Denial of Service attacks. It’s designed to allow only so many hits to the server in an elapsed period of time by the same user. It was set to allow 150 hits to the server in a second, more than that, and it would block the IP for 5 seconds.

Here’s what he did:

The script would backup one table, and rerun the same script over and over… Each time probably accessing some of the same components twenty or thirty times. Since the problem was too many accesses to the same objects per second, the script just needed to be slowed down.

wp-admin/edit.php started like this:
<?php
require_once(‘admin.php’);
$title = __(‘Posts’);
$parent_file = ‘edit.php’;
require_once(‘admin-header.php’);

I added two sleep statements and it works great. And the same first lines of edit.php look like this:

<?php
sleep(1);
require_once(‘admin.php’);
sleep(1);
$title = __(‘Posts’);
$parent_file = ‘edit.php’;
require_once(‘admin-header.php’);

Now if I can get the encoding straight.
thanks for your help everyone.

FWIW, this is a new upgrade: 1.5.0 –> 1.5.1.3. Deleted all files except /content and config.php and uploaded the upgrade. Any issues here maybe?

Skippy thanks, but this wasn’t enough. /backup is set to 777, but your 1.6 hangs about a third of the way through the backup (for that matter 1.5 hasn’t been an honor student lately either).

A gz file, appropriately named, was saved to /backup, but it was just 2kb! I decompressed it, and opened it in Notepad++. It looked good until its last line, which was this:

# End of data contents of table wp1_linkcategories
<line>

There seems to be plenty of disk space on the server – I checked at the host.

One interesting piece: the file properties of the .gz file created in /backup shows itself as 644. Don’t know how it incarnated this way or if this has anything to do with the problem, but it seems suspicious enough to mention.

thanks everybody for your help.

skippy: thanks. I kept my ftp s/w open during the ‘backup’. No files ever made it to /backup even before I clicked the ‘save to disk’. Actually, they may have – but they’re essentially empty (3k for what are normally 25mb+ files). Any ideas?

Also, any answers on the other stuff, esp. re: encoding details utf-8 vs latin1 on a phpmyadmin restore and how it works -getting shifted between utf on the blog and latin on the backups? thnx.