By kosh-1 on

I've just upgraded my installation from 4.6 to 4.6.6, having followed instructions to the letter. My site though looks exactly the same, and I can find no differences anywhere! How can I be sure I didn't do anything wrong and that perhaps I'm still running the version with the bugs?? Sorry for sounding paranoid!

Maha

⋅ Categories: Drupal 4.6.x

Comments

chx’s picture

chx commented

the changes are very small. really. if you really want to know, check your session id (in cookies.txt) before and after login. they will differ.
--
My developer blog. | The news is Now Public | Ask not what Drupal can do for you -- ask what you can do for Drupal.

--
Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.

alanburke’s picture

alanburke commented

Pardon my ignorance, but where is that file, cookies.txt, located?
I can't see it in my Drupal root.

Regards
Alan

Drupal development and themeing, Galway, Ireland

dww’s picture

dww
we/he/they
commented

i think this question (and others like it) revolve around the issue of answering this question:

"how do the admins know that the upgrade/patching was successful?"

after a quick look through the admin pages (and grepping through the core source tree) it doesn't appear that drupal provides any mechanism for site admins to view the currently installed version. that seems like a handy feature for the 4.8 series (since 4.7 appears to be in feature-freeze now, only bug-fixes will be made to 4.7 at this point).

so, while chx's comments are certainly true... the user-visible changes between 4.6.5 and 4.6.6 are practically nil, i think the real answer to this question is "no, there's no way to view your current version, but that functionality might be worth adding to a future version of drupal".

-derek

___________________
3281d Consulting

LateNightDesigner’s picture

LateNightDesigner commented

While I for one have asked the question before of what version exactly I'm running, I usually just make sure I upload the current changelog.txt file. One of the most common ways to do version handling is to either offer a update/install scirpt, or to display the version via a database entry. Small, cosmetic/security changes would need a databse edit, via script or no, but I can see this being added via a simple admin hook.

For now, just make sure to keep track of your changelog files or right a little admin block, page, or script on the template that can read the simple flat file root/changelog.txt

I dunno something simple like:

<?php
$fp = fopen('changelog.txt','r');
if (!$fp) {echo 'ERROR: Unable to open file.'; exit;}
 
while (!feof($fp)) {
$line = fgets(1, 25);
echo '
<tr>
<td>'.$field1.'</td>
</tr>';
}
fclose($fp);
?>

This is in no way the correct code to use, and I'm sure someone will try it anyhow and complain but it's a start. I'm no where near a good php programmer, but a dabbler and just offering a direction for people to head. This is loosely pieced together from what I remember of a book I had that talked about flat file reading. :-D

Maybe someone can clean it up or make it a snippet or something.
Just my 2 coppers.

//---------------------------------------
Latenightdesigners.com- Giving IMD a Fighting Chance

grcm’s picture

grcm commented

It's hard to find an obvious place which says the Drupal version. It would be useful if the administration pages had this information.

In the meantime, if you use version control for your Drupal sites, you can easily confirm there have been multiple changes to your installation.

-- Version Control your Drupal web site with The File High Club