rockhauler
Forum Replies Created
-
Forum: Installing WordPress
In reply to: Question about User Field in User Table in MySQLWhen you log in to your blog, and go to the dashboard, then manage, and then users what do you see there?
Do you see the same user names that you see in your MySql database table?
Forum: Installing WordPress
In reply to: Install.php generates blank page AND source.Work around:
In this thread was the hint I needed to work around the blank html document returned by install.php when it should have been the generated password for the admin account during installation.
The install script stores a generated password, in the MySql database table as a MD5 function. Thus it is possible to enter into that database table, a known password with this MySql command entered from the MySql command line interface to your blog’s database:
MySql>update wp_users set user_pass=md5(‘password_of_choice’) where user_login=’admin’;
Then, when logging into your blog, as ‘admin’, with password ‘password_of_choice’, you will have control of your blog. Unless something else has failed.
This, of course, presumes that you have access to your MySql database, either via command line, or mysql client.
This only addresses the situation in my previous post where step two of the installation returns a document stating (more or less) entering data into database, and which should also return the admin account password, and the keyword ‘finished’ but fails to return that password.
If you have access to your MySql blog database you can see the generated data for the admin account with:
mysql>select user_login, user_email, user_pass from wp_users;
If your tables are not created, or there is no data, this work around won’t help you.
Forum: Installing WordPress
In reply to: Install.php generates blank page AND source.I’m having a similar problem.
wp-config has been edited.
The install script generates the data base tables, enters the admin user, and password into wp_users.
At the point where the install script should generate an email to the admin email address, nothing happens. The remaining part of the html page generated by the install script, the part that displays the admin user account and password are not present in the generated html page. Nor does the word ‘finished’ appear.
At first I thougt it was because this was being installed on my LAN which does not have a working smtp Mail Transport Agent. That has proven to be false. I see no evidence that the wordpress install script has generated the email to that admin email address.
Forum: Installing WordPress
In reply to: index.php is not opening by default..In your .htaccess file add this line;
DirectoryIndex index.php
And see if this helps.wp scripts don’t always append the index.php filename to the end of the url, and presume that the webserver is configured to supply it automagically.
good luck
Forum: Installing WordPress
In reply to: MySQL Problems…What version of MySql are you running? Do you have a command line interface (to MySql) available? If yes, try setting your mysql user account password (in mysql) with old_password().
Example:
set password for ‘someone’@’somewhere = old_password(‘passphrase’);When wordpress scripts like wp-install attempt a connect to mysql, and that connect fails, strange things happen.
I just recently worked through something like this.
The key here is wp-install, and others go bonkers when a mysql_connect() request fails unexpectedly.
Good LuckForum: Installing WordPress
In reply to: Install Bug? setup-config.php?step=2Apparently something to do with failed mysql_connect, or mysql_open call.
setup-config will not connect to mysql version 5.0.15 on ‘localhoast’, but when I specify a different host, on my home LAN, which is running mysql version 4.1.16, everything works!the host (on my LAN), that I wanted wordpress installed on apparently has a conflict between php4, and myqsl ver 5.
It is not a wordpress issue, other than failing to handled the failed open, or connect in wp-db properly.
It’s kinda interesting to see wordpress storing its documents on a host different from the host which is serving the documents to the user, and the host that is actually running the php scripts!
Forum: Installing WordPress
In reply to: Install Bug? setup-config.php?step=2I am having the same problem.
Runing MySql ver 5.0.15
PHP ver 4.3.10-16
Apache2 2.0.54test.php bundled with php reports
MySQL_api 4.0.24
Before running the wordpress install.php script, the expected MySql database was created. This is a new install, there are NO TABLES CREATED YET! No instructions for doing so, none have been discovered. Looking through the wordpress scripts, I haven’t yet found where these tables will be created. In wp-settings.php these table names are listed, but no columns defined/declared.No previous version of wordpress has ever been installed, so no existing database/tables present. The blank database expected in the 5 minute install was created, but no tables. (This is on a home LAN, not public.)
Running the install script with wp-config.php properly edited to provide hostname, user, password, database name results in “Can not connect to database error”. MySQL user tables with correct privileges are present. Both “OLD_PASSWORD”, and “PASSWORD” have been tried. WordPress can not connect with either password format.
(Yes, I am sure that MySql is running.)Running the install script with wp-config.php not present, setup-config.php properly detects the missing file, and offers to create one. After filling in the necessary entries for hostname, user, password, database, and “submit”ing the data, setup-config.php fails at step 2 with this same error.
Warning: Cannot modify header information – headers already sent by (output started at /storage/Debian/wordpress/wp-admin/setup-config.php:22) in /storage/Debian/wordpress/wp-includes/wp-db.php on line 308
I have seen the previous tip about white space, missing php tags, etc. Looking at setup-config.php I’m having trouble decrypting the nested code blocks in the three cases present.
Note Appended: Looking at the scattered headers coded into various php scripts it occurs to me that it might be a better coding practice to have ONE FUNCTION that builds/outputs the required html header, and that ONE FUNCTION be called in each case when a header is appropriate, rather than having headers hand coded into various scripts multiple times.
Just a thought.