Doug-O

Some of these threads do not show that any resolution has been achieved for this problem, and there is more than one.. If I find information that I believe helps others, and that information is not included in that thread, then I will post it. You are of course entitled to your opinion, but my posts are constructive.

I am inserting this in every open query on this topic, as it actually solved the problem. This happens because one of the databases gets locked. You have to use PHPMyAdmin tool (available from your host most likely) to review the status of all the databases in use for your site. Select the ‘wordpressblog’ (or whatever set of databases seem appropriate) from the list at left. This brings up all the databases running on your site. The particular database that caused this problem was wp_postmeta – the status in the PHPMyAdmin window was ‘in use,’ and as our databases are small this should never be the case when you can look at them and see them in use – they should be just sitting there. Here it was locked. In the PHP MYAdmin tool, check the particular database that’s in use, then on the drop down box at the bottom select ‘repair table.’ This instantly solved my problem. Thanks to yahoo support rep!

I am inserting this in every open query on this topic, as it actually solved the problem. This happens because one of the databases gets locked. You have to use PHPMyAdmin tool (available from your host most likely) to review the status of all the databases in use for your site. Select the ‘wordpressblog’ (or whatever set of databases seem appropriate) from the list at left. This brings up all the databases running on your site. The particular database that caused this problem was wp_postmeta – the status in the PHPMyAdmin window was ‘in use,’ and as our databases are small this should never be the case when you can look at them and see them in use – they should be just sitting there. Here it was locked. In the PHP MYAdmin tool, check the particular database that’s in use, then on the drop down box at the bottom select ‘repair table.’ This instantly solved my problem. Thanks to yahoo support rep!

I am inserting this in every open query on this topic, as it actually solved the problem. This happens because one of the databases gets locked. You have to use PHPMyAdmin tool (available from your host most likely) to review the status of all the databases in use for your site. Select the ‘wordpressblog’ (or whatever set of databases seem appropriate) from the list at left. This brings up all the databases running on your site. The particular database that caused this problem was wp_postmeta – the status in the PHPMyAdmin window was ‘in use,’ and as our databases are small this should never be the case when you can look at them and see them in use – they should be just sitting there. Here it was locked. In the PHP MYAdmin tool, check the particular database that’s in use, then on the drop down box at the bottom select ‘repair table.’ This instantly solved my problem. Thanks to yahoo support rep!

I am inserting this in every open query on this topic, as it actually solved the problem. This happens because one of the databases gets locked. You have to use PHPMyAdmin tool (available from your host most likely) to review the status of all the databases in use for your site. Select the ‘wordpressblog’ (or whatever set of databases seem appropriate) from the list at left. This brings up all the databases running on your site. The particular database that caused this problem was wp_postmeta – the status in the PHPMyAdmin window was ‘in use,’ and as our databases are small this should never be the case when you can look at them and see them in use – they should be just sitting there. Here it was locked. In the PHP MYAdmin tool, check the particular database that’s in use, then on the drop down box at the bottom select ‘repair table.’ This instantly solved my problem. Thanks to yahoo support rep!

Same issue, no resolution, but I’m calling yahoo hosting as they have had database connection issues all week that they claim are ‘resolved.’

I was on the phone w/yahoo tech support for an hour – he made it clear that it was impossible to create, store, or upload an .htaccess file on their servers – he claimed it was a security issue. Permalinks exist on our site to control the other pages we run in addition to the blog page – they are all permalinked, and they are what break when we try to run from root using the ‘giving wp its own directory’ suggestions. The workaround for now is a ‘permanent redirect’ script in an index.php in root – not what I had in mind, but for the time being…

Well, yes, but why doesn’t the Codex article suggestion work? And since it’s yahoo, I can’t migrate the .htaccess file that seems to be so important to permalinks when moving all the files up to root from current subdirectory. So fonglh, have you migrated the whole thing up one level in yahoo with no problem? Has anyone?