protechs

My client just got suspended also… for 5.5% of the shared environment CPU. We were notified 2 weeks ago and cannot figure out what happened from the last WP upgrade just before that. Have WP Cache, swapped out one social networking share plugin (Gregarious) for one that doesn’t do email (i-love-s-n), use the Comment Subscribe and that’s it.

Today they didn’t even notify us. They had already moved us to the “troublemaker” server and it must have continued. I got them to turn us back on for a bit so we can troubleshoot. When we’re off, we can’t get to anything for backup or repair.

HELP!!

I just did a delete and then total clean install of version 2.2 and got all those ascii replacements throughout most posts which used many different kinds of punctuation.
It did not matter what theme. I upgraded another blog a few hours earlier and no problems. However…

This time I had USED THE BRAND-NEW CONFIG.PHP FILE (first new one I’ve ever seen and I almost didn’t look at it).

As soon as I read another thread supposedly resolved, I READ THIS LINE he had mentioned there:

Or any other editor, which supports UTF-8,

and remembered seeing that line on the New config.php file.

I deleted the new and put back in the old and everything was perfect again. This is the first ever problem I’ve had with a WordPress install (script-wise) in about 40 installs and upgrades since May 2004.

Whahoppened??

Resolved by using old config.php file without what I’ve bolded below.

<?php
// ** MySQL settings ** //
define(‘WP_CACHE’, true); //Added by WP-Cache Manager
define(‘DB_NAME’, ‘account_name’); // The name of the database
define(‘DB_USER’, ‘account_user’); // Your MySQL username
define(‘DB_PASSWORD’, ‘secretword’); // …and password
define(‘DB_HOST’, ‘localhost’); // 99% chance you won’t need to change this value
define(‘DB_CHARSET’, ‘utf8’);
define(‘DB_COLLATE’, ”);

// You can have multiple installations in one database if you give each a unique prefix
$table_prefix = ‘wp_’; // Only numbers, letters, and underscores please!

// Change this to localize WordPress. A corresponding MO file for the
// chosen language must be installed to wp-content/languages.
// For example, install de.mo to wp-content/languages and set WPLANG to ‘de’
// to enable German language support.
define (‘WPLANG’, ”);

/* That’s all, stop editing! Happy blogging. */

define(‘ABSPATH’, dirname(__FILE__).’/’);
require_once(ABSPATH.’wp-settings.php’);
?>

I just did a delete and then total clean install of version 2.2 and got all those ascii replacements throughout most posts which used many different kinds of punctuation.
It did not matter what theme. I upgraded another blog a few hours earlier and no problems. However…

This time I had USED THE BRAND-NEW CONFIG.PHP FILE (first new one I’ve ever seen and I almost didn’t look at it).

As soon as I read this thread, I READ THIS LINE ABOVE:

Or any other editor, which supports UTF-8,

and remembered seeing that line on the New config.php file.

I deleted the new and put back in the old and everything was perfect again. This is the first ever problem I’ve had with a WordPress install (script-wise) in about 40 installs and upgrades since May 2004.

Whahoppened??

Resolved

<?php
// ** MySQL settings ** //
define(‘WP_CACHE’, true); //Added by WP-Cache Manager
define(‘DB_NAME’, ‘account_name’); // The name of the database
define(‘DB_USER’, ‘account_user’); // Your MySQL username
define(‘DB_PASSWORD’, ‘secretword’); // …and password
define(‘DB_HOST’, ‘localhost’); // 99% chance you won’t need to change this value
define(‘DB_CHARSET’, ‘utf8’);
define(‘DB_COLLATE’, ”);

// You can have multiple installations in one database if you give each a unique prefix
$table_prefix = ‘wp_’; // Only numbers, letters, and underscores please!

// Change this to localize WordPress. A corresponding MO file for the
// chosen language must be installed to wp-content/languages.
// For example, install de.mo to wp-content/languages and set WPLANG to ‘de’
// to enable German language support.
define (‘WPLANG’, ”);

/* That’s all, stop editing! Happy blogging. */

define(‘ABSPATH’, dirname(__FILE__).’/’);
require_once(ABSPATH.’wp-settings.php’);
?>

Some exact same problems on install and use. (Even though I really did follow all instructions, dumping/deleting every single file and folders of files before uploading brand-new 2.1 (from 2.05) I still got the upgrade errors that seemed to indicate 2 versions of files were present (not possible–they were all deleted).
After 3 identical re-uploads, it finally cycled me to a php page that contained a text “upgrade” link which worked.

The categories with, and including, Blogroll (which I renamed as we don’t use a Blogroll) no longer function. The words appear on the sidebar (according to the theme & css) where they should, but no links are retrieved and listed and the other categories added to the theme sidebar with php code don’t show at all.

When I checked the “On-demand backup of your WordPress database. ver. 1.8 By Scott Merrill,” Everything seemed OK except that now the 10th normal WP sql table (there are only 9 now) is to the right and can be checked off to be included in backup jobs as a non-core table. Server is:
PHP version 5.2.0
MySQL version 4.1.21-standard
Theme: Silver Lexus 0.9 [(just graphic/text/colors modified on .css—I don’t do php) Categories *function* on the Default theme, but still missing 10th core table on backup list.]

Is there a help link or is this the place to look for help in what the new Blogroll feature (no longer Link Category area) and missing sql table might be doing? It “appears” that using the Link Category work-around php substitutions I found after the last upgrade don’t work any longer. And from the above programmer talk, maybe the sql table won’t retrieve them anyway now because wp_link2cat is no longer core. ?

Pardon me for not being knowledgeable enough about coding to be very articulate. I know enough to be dangerous and just forget the rest I’d like to do so the blog will function. Most plugins I would choose didn’t work before and their authors are “working on it.” Many users had precisely the same errors I did.

Thanks MUCH! Deb

FYI as others have had to answer up about php.php on their server:
Build Date Jan 23 2007 11:01:18
Configure Command ‘./configure’ ‘–with-apxs=/usr/local/apache/bin/apxs’ ‘–prefix=/usr/local’ ‘–with-xml’ ‘–enable-bcmath’ ‘–enable-calendar’ ‘–with-curl’ ‘–with-dom’ ‘–with-dom-xslt’ ‘–with-dom-exslt’ ‘–enable-ftp’ ‘–with-gd’ ‘–with-jpeg-dir=/usr/local’ ‘–with-png-dir=/usr’ ‘–with-xpm-dir=/usr/X11R6’ ‘–with-gettext’ ‘–with-imap=/usr/local/imap-2004g’ ‘–enable-magic-quotes’ ‘–with-mysqli’ ‘–with-mysql=/usr’ ‘–enable-discard-path’ ‘–with-pear’ ‘–enable-sockets’ ‘–enable-track-vars’ ‘–with-ttf’ ‘–with-freetype-dir=/usr’ ‘–enable-gd-native-ttf’ ‘–with-xmlrpc’ ‘–with-zlib’
Server API Apache
Zend Engine v2.2.0; with Zend Extension Manager v1.2.0; with Zend Optimizer v3.2.2

It works both ways and still no comments. It was set to default and looked fine and then I chose custom template and it was fine. No comments or comment boxes. It appears many are having the exact same problem. I could not have follwed the instructions anymore closely, and exactly. I’m going to try a clean, new install and rewrite the new index.php that comes with that. It will be MUCH FASTER then trying the upgrade instructions.
Thanks though.

Ok.

It is set for default now. Yes. Sleep would be nice.
Thanks.

I’ll go do these things….
[imagine a “PLEASE WAIT”] graphic here.

I’m sorry, I have been trying to understand your question. It doesn’t make sense to me that my new style sheet is being read at all (as there’s no line that points to that resaved as style.css file) ?

I don’t know how the index page reads either the default theme or the carrots themes – it seems it should be reading the default, yet the page appears the way the old default theme with our graphics should appear.

“you need to change the file call in your index.php(?) from wp-comments.php to comments.php as no wp-comments.php exists.”

OK, then you mean alter the one I put back into my main blog. When I put the newly modified index.php into that spot (the main blog folder) then went to test…. the entire page was white/blankness.

Do I need to run the upgrade again after I put the modified index.php from Carrots? Where do the other 3 files go? Do they just stay in Carrots? They’re not dealt with again that I can read in the instuctions.

Thanks.

What now? Should the newly modified comments phps be put anywhere except in the wp-content/themes/Carrots folder
I’ve read thru the above. I’ve made files according to https://www.tamba2.org.uk/wordpress/upgrade/
and they seem to all be in place. I put back my old index.php in the main blog folder since the new one I modified is back in the Carrots folder back in themes/Carrots along with the other 3 files we modified:
index.php
comments.php
comments-popup.php
style.css

I did forget about the plugins part – but I have never dealt with those or changed the default from the original install from last November.

Ran upgrade.php and the site layout, etc. looks OK on the index page (fonts for group headers is Huge now).

The theme is OK it appears. The posts/graphics seem OK, but there is that comment error group at the top of most posts (except the last one –top of blog).

I get the same comments errors at the top of every post and the comments that go with the post and the comment window is not there.

Warning: main(/home/whyjohn/public_html/blog/wp-comments.php): failed to open stream: No such file or directory in /home/whyjohn/public_html/blog/index.php on line 122

Warning: main(/home/whyjohn/public_html/blog/wp-comments.php): failed to open stream: No such file or directory in /home/whyjohn/public_html/blog/index.php on line 122

Warning: main(): Failed opening ‘/home/whyjohn/public_html/blog/wp-comments.php’ for inclusion (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in /home/whyjohn/public_html/blog/index.php on line 122

They were having general problems….
It appears they repaired it.

Thank you again.

What do I tell them they need to do. I had to hand-hold the last time when they upgraded their php version, and send them your comments. Should I send them the link above?

https://codex.www.ads-software.com/Answers-Trouble_Shooting#Error_28

Thank you.

It appears I have the same problem (different specifics) as a previous poster. Everything was fine, then I went to view the blog and I got this error:

Database error: [Got error 28 from table handler]
SELECT * FROM wp_posts WHERE 1=1 AND (post_status = “publish” OR post_author = 1 AND post_status != ‘draft’) GROUP BY wp_posts.ID ORDER BY post_date DESC LIMIT 15
No posts found.

I have NO idea what to do now.

Anyone read “database” ease. I can go and view each post individually if I go to edit comments and “view post” and they’re fine. It just won’t organize them to edit posts or view the blog at all – nothing displays but some color and the error message at the top.

???

Thank you all. We’re back up and running after sending on all the info last night (CST U.S.). The Host hadn’t seen it and indicated that they only did the Zend Optimizer on the server that has WordPress… hmmmmm.

My blog has gone terribly wrong just didn’t “speak” to me.

protechs

THANK you. I’ll send that on to the support group.
What if they won’t do that? Are we dead on that hosting service (Canadian)?