yvanacalcom
Forum Replies Created
-
Forum: Installing WordPress
In reply to: update from 2.0.2 to 2.1 fatal errorI did a restore of my database and got this message in PHPMyAdmin at the end of the restore:
“There seems to be an error in your SQL query. The MySQL server error output below, if there is any, may also help you in diagnosing the problem
ERROR: Invalid Identifer @ 8
STR: 4.3.
SQL: backup-4.3.2007_11-53-36_wellmast/??????????????????????????????Then I realized that the backup I made was for all my databases on the server(some others than WP)which might explain the error.
My real problem is that I do not know how to assign the right database to WP. In wp-config.php the parameters seem to be correct.
When I open the admin center of WP I get the following 2 lines before the opening screen:
“Warning: array_keys(): The first argument should be an array in /home/wellmast/public_html/blog/wp-admin/admin-functions.php on line 1315
Warning: Invalid argument supplied for foreach() in /home/wellmast/public_html/blog/wp-admin/admin-functions.php on line 1315″
So I tried to reupload this file from the upgrade software on my PC hoping that it would solve the problem. To no avail.
I am at a complete loss now. How do I make sure that PW accesses the proper database so that my blog restart working. Any ideas?
Forum: Installing WordPress
In reply to: update from 2.0.2 to 2.1 fatal errorI backed up my database, but restoring seems a painful process. I still have my database with all the tables, prior to upgrading WP, on the server. I just don’t figure out how to assign it to my blog. Can this be done from the WP admin center or from PHPMyAdmin or any other way?
I’ve seen a possibility to directly change the text of wp-config file but I am scared to death to do that as I don’t understand what I will be doing ??
Thanks again for your help.
Forum: Installing WordPress
In reply to: update from 2.0.2 to 2.1 fatal errorI finally succeeded in upgrading WP at least all files have been transfered properly. But now when I access the site I get a message that says:
WordPress database error: [You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near ‘( cat_id bigint(20) NOT NULL auto_increment, cat_name tinyt]
CREATE TABLE ( cat_id bigint(20) NOT NULL auto_increment, cat_name tinytext NOT NULL, auto_toggle enum(‘Y’,’N’) NOT NULL default ‘N’, show_images enum(‘Y’,’N’) NOT NULL default ‘Y’, show_description enum(‘Y’,’N’) NOT NULL default ‘N’, show_rating enum(‘Y’,’N’) NOT NULL default ‘Y’, show_updated enum(‘Y’,’N’) NOT NULL default ‘Y’, sort_order varchar(64) NOT NULL default ‘rand’, sort_desc enum(‘Y’,’N’) NOT NULL default ‘N’, text_before_link varchar(128) NOT NULL default ‘- ‘, text_after_link varchar(128) NOT NULL default ‘
‘, text_after_all varchar(128) NOT NULL default ‘
‘, list_limit int(11) NOT NULL default ‘-1’, PRIMARY KEY (cat_id) )
I have no idea how to change the database and where to change this. Thanks for a new help to a lost soul ??
Forum: Installing WordPress
In reply to: update from 2.0.2 to 2.1 fatal errorSmartFTP says it might be a norton firewall issue. I am trying to fix this. And yes my connection is rather slow today.
Forum: Installing WordPress
In reply to: update from 2.0.2 to 2.1 fatal errorThanks a lot Samboll. I tried a new upload of the wp-includes folder and got a “transfer failed” message from SmartFTP and got this time:
Warning: main(/home/wellmast/public_html/blog/wp-includes/query.php): failed to open stream: No such file or directory in /home/wellmast/public_html/blog/wp-settings.php on line 153
Warning: main(/home/wellmast/public_html/blog/wp-includes/query.php): failed to open stream: No such file or directory in /home/wellmast/public_html/blog/wp-settings.php on line 153
Fatal error: main(): Failed opening required ‘/home/wellmast/public_html/blog/wp-includes/query.php’ (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in /home/wellmast/public_html/blog/wp-settings.php on line 153
I had a similar “transfer failed” message during the first upload. So a bad transfer seems to be the reason, but should I try again to upload until it works? Or can there be another cause of the bad transfer?
I first tried to restore the database so I am not sure what is going on now…
- ‘, text_after_link varchar(128) NOT NULL default ‘