We've been running Drupal 4.7.x for some time, with no problems.
We are using our own in-house LAMP server, so don't have any issues with access or config.
We've been trying to install Drupal 5.1 separately for testing, into a new folder, new database, new everything. IT FAILS TO INSTALL!
NOTE: We are not trying to upgrade 4.7.x. We simply want to install 5.1 from scratch to test.
We hope someone can either identify a (stupid) mistake on our part, or confirm that Drupal 5.1 has a a problem.
Our steps:
1. Copy Drupal-5.1 to NEW folder in HTML webserver root, /srv/www/htdocs/, the same level as the folder with our existing Drupal 4.7.
2. Rename new folder Drupal-5.1 to "d" because that's how we like it, so Drupal's physical location is /srv/www/htdocs/d/.
3. Set properties of "d" and everything in it to 777 temporarily to make sure installation has no access problems.
4. Create a NEW database for this Drupal installation, and give our Drupal username all rights to the database.
At this point, EVERYTHING about Drupal-5.1 is NEW -- new folder, new database, total access to all its folders and files. Install should work, right?
5. In browser, go to the new folder, which launches install.php.
6. First install.php page is where we'd give it all our database info. Except, the top of the page, before we even use the database fields, displays a long list of errors:
Notice: Trying to get property of non-object in /srv/www/htdocs/d/includes/form.inc on line 325
Notice: Undefined variable: edit in /srv/www/htdocs/d/includes/form.inc on line 759
Notice: Undefined variable: redirect in /srv/www/htdocs/d/includes/form.inc on line 268
Notice: Undefined variable: base in /srv/www/htdocs/d/includes/form.inc on line 461
Notice: Undefined index: #value in /srv/www/htdocs/d/includes/form.inc on line 1041
Notice: Undefined index: #value in /srv/www/htdocs/d/includes/form.inc on line 1041
Notice: Undefined variable: no_module_preprocess in /srv/www/htdocs/d/includes/common.inc on line 1467
Notice: Undefined variable: no_theme_preprocess in /srv/www/htdocs/d/includes/common.inc on line 1488
Since we haven't even gotten to the step of setting up a database or user or site, these errors are coming purely from the brand new unmodified Drupal-5.1 script files.
Drupal script install.php is missing something crucial, but we copied (and recopied several times) every Drupal-5.1 file and the complete folder structure that was in the original tarball.
Our best guess is that, while install.php is obviously finding lots of its files in our Drupal-5.1 folder "d" (as stated by the error messages), perhaps somewhere it is not correctly using a relative path so not finding one crucial file. That would qualify as a bug.
Has anyone succeeded in installing Drupal-5.1 from scratch like this?
What now?
Comments
From the System
From the System requirements:
You can set error_reporting in php.ini.
--
The Manual | Troubleshooting FAQ | Tips for posting | How to report a security issue.
Also from system requirements...
The full statement in System Requirements at http://drupal.org/requirements is this:
====================
... we recommend the following settings:
error_reporting set to E_ALL & ~E_NOTICE.
these settings are contained in the default .htaccess file that ships with Drupal, so you shouldn't need to set them explicitly. Note, however, that setting PHP configuration options from .htaccess only works:
* with Apache (or a compatible web server),
* if the .htaccess file is actually read, i.e. AllowOverride is not None,
* if PHP is installed as an Apache module.
====================
That's what it says. I confirmed that Drupal's .htaccess has the recommended statement, and since my server complys with ALL of the above, I don't know why I'm seeing the errors -- and more seriously, I don't know why the errors exist.
UPDATE: Though I can't get rid of the error messages, I went ahead and provided Install.php with the database info, and continued the installation. It eventually declared that Drupal is installed, and so-far, it seems to be. So maybe the problem is behind me.
But why assume that? If the installation script found all those errors, what does it indicate about the state and stability of Drupal once installed?
There are NOTICES
These are notices, not errors, indicating your error_reporting level is to high (ie, php is reporting notices). These are relatively harmless, though they make development harder, and - when output - prevent sending of headers.
The aim is to get rid of notices in Drupal 6.
--
The Manual | Troubleshooting FAQ | Tips for posting | How to report a security issue.
I had similar problems with
I had similar problems with Drupal 5.5 installation after having installed and used another version of Drupal in my server. I solved it cleaning the session data stored in /phpdir/sessiondata.
i can't locate that folder,
i can't locate that folder, where is it?
Similar issue
Don't know if this will help. I had a previous install of drupal (5.3), never having logged in and then tried 5.7. I got a list of similar notices up above my log in prompt on install. Some of the line numbers were a few lines off.
The problem happened after installing Developer Suite from DevSide, which came bundled with php 5.2.5
I'm left like you with the question where that folder is and also how to change notice reporting levels on php, on the one hand, and a spooky feeling that other stuff will be going wrong on the other.
Did you go ahead and operate on the system as you had it, or did you reinstall? For me, I couldn't install because
So I did a little more research. The exact lines referred to, (at least in mine) are
I'm not sure what all this means, but I will be getting to the bottom of it in and updating very soon, just in case anyone else runs into this same issue.
James
Newbie here. Really all I want is to make fast web sites mostly, but with some power features and have the ability to customize, not just design, but processes, such as eCommerce features, and subscription based user levels.
php session dir
Removing the sessions worked for me, here's how to do that:
You can find your session save directory in 2 places: 1) your php.ini file (/etc/php.ini); 2) phpinfo();.
Look for the value assigned to 'session.save_path'.
Here's what mine says:
session.save_path = "/var/lib/php/session"
Go there and delete the sessions, if you can. Note, you may want to stop apache before doing this so it doesn't get wedged.