By kyouens on

I just upgraded to 4.7.3 from 4.7.2 and it seems to have gone flawlessly. I am still evaluating my site for certain bugfixes (e.g. the "double login problem"). I created this thread in case people run into difficulty they can mention it here so the rest of us can be on the lookout. Good luck with the upgrade everyone.

⋅ Categories: Drupal 4.7.x

Comments

gopher’s picture

gopher commented

Can I simply copy the user.module from 4.7.3 over the user.module from 4.7.2? Anyone know if that will suffice?

bhlang’s picture

bhlang commented

From what little I know about reading .patch files, it seems that the instructions in http://drupal.org/files/sa-2006-011/4.7.2.patch simply tell you to change one line in user.module. Is that correct?

mo6’s picture

mo6
he/him
Primary language Dutch
commented

This one line patch is only for the security update. There are loads of changes in this new version in a lot of files.

abqaria’s picture

abqaria commented

if someone has a site that already runs 4.7.2, will just uploading the files and replacing the old ones, do the job ?

ethangato’s picture

ethangato commented

below the patch file link, there is a line
"We recommend you do a full upgrade."

is this means there are more then just user.module need to been patch?
would drupal.org offer a full upgrade patch?
I think many people like I am may do some modified in many files and didn't remember where and what.

** add **
for those who has permission to login your server, make your patch file is easier by following this guide
http://drupal.org/node/53798

eugsadhu’s picture

eugsadhu commented

Modified files:

  • database/updates.inc
  • includes/bootstrap.inc
  • includes/common.inc
  • includes/file.inc
  • includes/form.inc
  • includes/locale.inc
  • includes/menu.inc
  • includes/module.inc
  • includes/path.inc
  • includes/tablesort.inc
  • includes/theme.inc
  • includes/xmlrpc.inc
  • includes/xmlrpcs.inc
  • misc/drupal.css
  • modules/aggregator.module
  • modules/archive.module
  • modules/block.module
  • modules/book.module
  • modules/comment.module
  • modules/filter.module
  • modules/forum.module
  • modules/legacy.module
  • modules/node.module
  • modules/ping.module
  • modules/profile.module
  • modules/search.module
  • modules/system.module
  • modules/taxonomy.module
  • modules/upload.module
  • modules/user.module
  • themes/engines/phptemplate/phptemplate.engine
  • ./CHANGELOG.txt
  • ./INSTALL.txt
  • ./LICENSE.txt
  • ./MAINTAINERS.txt

I have taken the liberty of making a zip archive of only the modified files. You may download, extract, and then upload.

http://kizhakethil.net/drupal/4.7.2-4.7.3.zip

calebgilbert’s picture

calebgilbert commented

I've found at least two files in directory misc (upload.js and drupal.js) that were also updated, as well as the blog.module.

Bloggyland.com

eugsadhu’s picture

eugsadhu commented

politicalphysics: You are mistaken.

The blog.module file in modules/ was not updated.
4.7.2: // $Id: blog.module,v 1.245.2.2 2006/05/14 15:17:13 killes Exp $
4.7.3: // $Id: blog.module,v 1.245.2.2 2006/05/14 15:17:13 killes Exp $

As for the misc/upload.js and misc/drupal.js
4.7.2: // $Id: upload.js,v 1.8.2.1 2006/05/05 11:57:19 killes Exp $
4.7.3: // $Id: upload.js,v 1.8.2.1 2006/05/05 11:57:19 killes Exp $

4.7.2: // $Id: drupal.js,v 1.22.2.1 2006/05/29 14:23:32 killes Exp $
4.7.3: // $Id: drupal.js,v 1.22.2.1 2006/05/29 14:23:32 killes Exp $

Note. No changes.

calebgilbert’s picture

calebgilbert commented

Maybe there weren't changes between 4.7.2 and 4.7.3 as downloaded from a full install package. I didn't check a 4.7.2 package...my impression is that 4.7.2 is supposed to be exactly the same as 4.7.0 and 4.7.1 except for the security change (which didn't effect these files). Maybe they did just update those files between 4.7.0 and 4.7.2. I don't know. But from the 4.7.0 to 4.7.3 I've got sitting on my desktop - those files are definitely different.

Bottom line if someone wants to be sure of what they got, they're probably good to do the due diligence themselves and make sure they're not adding/taking away something important. If something goes wrong they won't have anyone to blame but themselves.

Bloggyland.com

sepeck’s picture

sepeck commented

We go through this every release actually. The correct answer is probably not. The probably is conditional on what you've done to any files, etc that makes them not core standard. Here we fall back to test sites and such.

Of course the 'probably' comes in if you can use and understand the patch/diff tools. If you follow the develop list and understand the php and the why of the patches that were implemented.

If you have a standard install, do not worry about just one file. The new update.php stuff and for the next Drupal version with the installer 'just the one file' will probably get you into more trouble then if you just updated your site.

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

abaryudin’s picture

abaryudin commented

So, what is actually new in 4.7.3, aside from the security fix? The CHANGELOG.txt doesn't elaborate...

--
http://www.baryudin.com

sepeck’s picture

sepeck commented

It's a security and bug fix release. No new functionality or features.

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

mo6’s picture

mo6
he/him
Primary language Dutch
commented

Does a list of bugfixes exist for this release? I'm pretty good in reading diffs (and coding assembler with /bin/cat ;) but matching the diffs with the fixed issues from drupal core is tedious.

ciric@drupal.org’s picture

ciric@drupal.org commented

It seems to me that running update.php is not needed to upgrade from 4.7.2 to 4.7.3.

I do not see any database change when comparing the two releases.

May someone confirm please?

Riccardo

Update: I did not read carefullly the 4.7.3 page: http://drupal.org/drupal-4.7.3, that says:

No API or database changes have been made since Drupal 4.6.8 and Drupal 4.7.2 so all contributed themes and modules should continue to work.

Therefore to upgrade it is enough to replace the files in the drupal directory without running the update.php, as explained here: http://drupal.org/upgrade/upgrading-without-a-db-upgrade

abaryudin’s picture

abaryudin commented

I think the release notes explicitly tell there were no database changes.
--
http://www.baryudin.com

incandescant’s picture

incandescant commented

I've recently registered a copy of Ecto for posting content to my Drupal site.
Since I updated to 4.7.3 (from 4.7.2) I am having problems with the XML-RPC interface.

If I try add or edit a post I get an error
"This content has been modified by another user, changes cannot be saved."

If it is new content it appears on my site as unpublished. If it is an edit of existing content I get a new unpublished post that duplicates the original entry with the modifications as well.

Is anyone else seeing this and can anyone advise on how to fix?

It's only been a couple of days and I'm already missing Ecto...

eugsadhu’s picture

eugsadhu commented

http://kizhakethil.net/drupal/xmlrpcs.inc.htm

mxc4’s picture

mxc4 commented

If you follow the upgrade instructions will simply copying over the modules directory be ok to keep all the non-standard modules that one has installed?

http://www.jumpingbean.co.za/php/development
http://www.cyberdesigns.co.za/content/view/22/40/

thumb’s picture

thumb commented

Perhaps we shouldn't say that it's broken, but it's certainly not working. This is the second issue I've had with a Drupal upgrade and ecto and I feel your pain. I realize that there may not be many ecto users of Drupal, at least when compared to Windows desktop blog clients, but I'm hoping someone will accept my offer to help test updates to xmlrpc.php.

incandescant, did you roll back to the previous version or find a fix for this?

incandescant’s picture

incandescant commented

Thumb; I ended up doing a roll-back.
I'm not 100% happy with that solution but haven't got any spare time to look into the problem (especially as I don't know PHP).

I'd be more than happy to help test updates as well!

drbill’s picture

drbill commented

Is this going to be addressed in the next release?

I upgraded directly from 4.6.x to 4.7.3, so I don't think I can easily roll back. Can I just download 4.7.2 and replace my 4.7.3 install since there are no DB changes?

I would like to keep using ecto.

spyjournal’s picture

spyjournal commented

has anybody done any upgrades from 4.6.x to 4.7.x
i want to be able to do that to a site. i cant find any guides on how to go about it

drbill - you say you did - how did you go about that?

dcypl’s picture

dcypl commented

I'm thinking of upgrading, would like to know if this is included