By zwhalen on

Hello. I've been running a hacked and tweaked 4.6.3 for a while now, and now that my site is finally on the eve of launch, I want to upgrade to the current release.

My concern is that I've put in several little workarounds and hacks here and there, but I'm afraid I don't remember where I put all of them. So when I upgrade, I'm afraid my little hacks will get overwritten. I had planned on just backing up my modules directory and just uploading it into the upgraded version, but I don't know what problems that'll cause with, say, a 4.6.3 node.module interacting with a 4.6.6 core.

Any advice / suggestions / cautions besides 'Comment your code' and 'keep track of things better'? Can anyone give me a sense of where the major differences are between 4.6.3 and 4.6.6 so I can avoid conflicts?

Many thanks.

zach

⋅ Categories: Drupal 4.6.x

Comments

Michael M’s picture

Michael M commented

Well, the first thing that you should do is backup the database. Next, backup ALL of the files.

What I would suggest is that you create and use personal modules instead of hacking the core. There is no need to hack the core, except to make minor modifications.

zwhalen’s picture

zwhalen commented

Thanks. I managed to pull it off; I just backed up like crazt and proceeded very carefully. And I did learn my lesson about hacking the core fairly early on, but it was those undocumented tweaks I was worried about. So far, no problems and 4.6.6 is running fine.

mrb’s picture

mrb commented

I had the same problem. I downloaded a copy of winmerge to compare the original 4.6.3 with my current backup, and see all the differences.

mrb

agentpt’s picture

agentpt commented

I have just upgraded from 4.6.3 to 4.6.6. Everything went smooth up until I ran update.php, which spat out this error, and took the site down:

Fatal error: Call to undefined function: filter_xss_bad_protocol() in /home/username/public_html/smog/includes/common.inc on line 631

Anyone know what the problem might be?

Michael M’s picture

Michael M commented

I remember getting those types of errors when I was developing my website. If I remember, it was due to calling certain functions BEFORE the drupal core got up and running. It could be a bug.

It wouldn't do you bad to search on the forums for that. You can use google, 'drupal Call to undefined function: filter_xss_bad_protocol' or use the drupal search, 'Call to undefined function: filter_xss_bad_protocol'.

----
http://LandCondos.com