Incorrect Drupal Version

[Dave Smith]

Yes, that was the question I was answering.

I hope I followed the steps you were asking. What I did was:

1. edit the file drupal/install/index.php by adding in the following three lines of code where you indicated:

echo "$drupalVersionFile<p>";
echo "$drupal_version<p>";
exit( );

2. ran the install process and copied the resulting message.

Hope this is what you were wanting.

Dave

[Donald Lobo]

There is a mistake with where u made the changes (i think). My changes would just print the drupal changelog file, and the derived drupal version and exit. it should not run the installer. Can you double check the place where u made the changes (install/index.php) and ensure that we exit after the two echo's

thanx

lobo

[Dave Smith]

I think what you may be looking for is this:

/domains/u/n/uniondata.net.tt/public_html/CHANGELOG.txt

unknown

Does this take us any further forward?

Dave

[Donald Lobo]

yes:

1. can u check if this file exists: /domains/u/n/uniondata.net.tt/public_html/CHANGELOG.txt

2. can u cut-n-paste the first 30 lines (approx) of that file. What version of drupal are you running?

lobo

[Dave Smith]

Sorry to be a bit slow about this but I am learning as I go along ...

1. where would I find this file?
2. I am using Drupal 5.1

Dave

[adrianrf]

came here with the same question.
my problem was that as a reflex after installing Drupal, I zapped the unnecessary files, including the changelog. (it was a clean install; why would I care about the change history?)

so, this is a feature that isn't very robust.
you do a version check on Drupal that
  a) depends on a documentation file resource, CHANGELOG.txt, vs. executable code or on database content
  b) does not preflight the presence of that same doc file resource
  c) consequently does not announce the absence of the resource upon which the version check relies
  d) consequently generate support traffic
happily, it's easy to resolve; by putting another copy of the file where the Installer expects to find it. but it's a glitch in the workmanship of what otherwise looks like a slick Installer. (I just wish my host of choice was ready to support PHP5, or that your Installer code could be back-ported to PHP 4.7.x.)

[Donald Lobo]

Thanx for the comments. I have fixed the error message in the installer to let folks know that we use CHANGELOG.txt for the version check.

Yes, i agree it is a total hack and not a great solution. However drupal does not store version information either in code or in the database. If you know of an alternative better solution, please let us know

lobo

[Dave Smith]

Does this mean the the problem is fixed?

Do I need to install an amended version of install.php?

Dave

[Donald Lobo]

No. The error message has been clarified. There is no code change

Most likely your CHANGELOG.txt is missing in the drupal folder at: /domains/u/n/uniondata.net.tt/public_html/CHANGELOG.txt

lobo

[Dave Smith]

Does this help?

/domains/u/n/uniondata.net.tt/public_html/CHANGELOG.txt

// $Id: CHANGELOG.txt,v 1.173.2.3 2007/01/29 21:51:53 drumm Exp $ Drupal 5.1, 2007-01-29 ---------------------- - fixed security issue (code execution), see SA-2007-005 - fixed a variety of small bugs. Drupal 5.0, 2007-01-15 ------------------------ - completely retooled the administration page * /admin now contains an administration page which may be themed * reorganised administration menu items by task and by module * added a status report page with detailed PHP/MySQL/Drupal information - added web-based installer which can: * check installation and run-time requirements * automatically generate the database configuration file * install pre-made 'install profiles' or distributions * import the database structure with automatic table prefixing * be localized - added new default Garland theme - added color module to change some themes' color schemes - included the jQuery JavaScript library 1.0.4 and converted all core JavaScript to use it - introduced the ability to alter mail sent from system - module system: * added .info files for module meta-data * added support for module dependencies * improved module installation screen * moved core modules to their own directories * added support for module uninstalling - added support for different cache backends - added support for a generic "sites/all" directory. - usability: * added support for auto-complete forms (AJAX) to user profiles. * made it possible to instantly assign roles to newly created user accounts. * improved configurability of the contact forms. * reorganized the settings pages. * made it easy to investigate popular search terms. * added a 'select all' checkbox and a range select feature to administration tables. * simplified the 'break' tag to split teasers from body. * use proper capitalization for titles, menu items and operations. - integrated urlfilter.module into filter.module - block system: * extended the block visibility settings with a role specific setting. * made it possible to customize all block titles. - poll module: * optionally allow people to inspect all votes. * optionally allow people to cancel their vote. - distributed authentication: * added default server option. - added default robots.txt to control crawlers. - database API: * added db_table_exists(). - blogapi module: * 'blogapi new' and 'blogapi edit' nodeapi operations. - user module: * added hook_profile_alter(). * e-mail verification is made optional. * added mass editing and filtering on admin/user/user. - PHP Template engine: * add the ability to look for a series of suggested templates. * look for page templates based upon the path. * look for block templates based upon the region, module, and delta. - content system: * made it easier for node access modules to work well with each other. * added configurable content types. * changed node rendering to work with structured arrays. - performance: * improved session handling: reduces database overhead. * improved access checking: reduces database overhead. * made it possible to do memcached based session management. * omit sidebars when serving a '404 - Page not found': saves CPU cycles and bandwidth. * added an 'aggressive' caching policy. * added a CSS aggregator and compressor (up to 40% faster page loads). - removed the archive module. - upgrade system: * created space for update branches. - forms API: * made it possible to programmatically submit forms. * improved api for multistep forms. - theme system: * split up and removed drupal.css. * added nested lists generation. * added a self-clearing block class. Drupal 4.7.5, 2007-01-05 ------------------------ - fixed security issue (XSS), see SA-2007-001 - fixed security issue (DoS), see SA-2007-002 Drupal 4.7.4, 2006-10-18 ------------------------ - fixed security issue (XSS), see SA-2006-024 - fixed security issue (CSRF), see SA-2006-025 - fixed security issue (Form action attribute injection), see SA-2006-026 Drupal 4.7.3, 2006-08-02 ------------------------ - fixed security issue (XSS), see SA-2006-011 Drupal 4.7.2, 2006-06-01 ------------------------ - fixed critical upload issue, see SA-2006-007 - fixed taxonomy XSS issue, see SA-2006-008 - fixed a variety of small bugs. Drupal 4.7.1, 2006-05-24 ------------------------ - fixed critical SQL issue, see SA-2006-005 -

[Donald Lobo]

yes. It is the right file and has the right version. I have no idea why it is not working on your site. You might want to ask a PHP developer in help with debugging this.

sorry about that

lobo

[Piotr Szotkowski]

Yes, i agree it is a total hack and not a great solution. However drupal does not store version information either in code or in the database.

If I go to http://drupal/admin/logs/status in my local install, I do get the Drupal version in the first line of the status table. After some looking around, it seems modules/system/system.module has the following:

Code: [Select]

<?php
define('VERSION', '5.1');
?>

Could we grep for this?

[Piotr Szotkowski]

(We could even use PHP’s version_compare() to simply check whether it’s greater or equal to 5.)

[Piotr Szotkowski]

Lobo and I worked on using modules/system/system.module instead of CHANGELOG.txt and it landed on the v1.8 branch (commits 11233-11237), so this will make the next 1.8 tarball build, hopefully later today.

[adrianrf]

nicely done!