Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By tflmike on
This blows... I just installed the update status module and it told me I had about eight modules I should update. So I did and now every thing's broken on my site! Well, actually only a few things...
I updated the following modules:
Global Redirect, Views Slideshow, Path Auto, JQ, ImageField, fckeditor and I think a few more.
Here's what happened:
1. My Views Slideshow stopped working. Now only the first image is displayed and it fades into nothing. I tried commenting out different .js calls but it didn't work. I also tried turning off different modules, re-installing 'Views Slideshow' etc... etc... I'm not sure what the issue is. Could there be a jQuery conflict of some sort?
2. I can't use the Global redirect module any more either. This is because when it's turned on, it replaces the contents of a slider I made with jcarousel with some random links... I have no clue why it's doing that!
Man if I would've known that updating the modules was going to break my whole site, I wouldn't have done it!
Has anyone else had issues like this?
Comments
Did you run update.php?
Did you run update.php?
Yep... so now I'm thinking I
Yep... so now I'm thinking I must have some javascript conflicts or something.
Yep... so now I'm thinking I
Yep... so now I'm thinking I must have some javascript conflicts or something.
yes
http://www.linnovate.net/en/node/117
---
Work: BioRAFT
Heavens
Heavens above, all you have to do is restore from your backups. What a fuss over nothing!
Yup, I know... Seriously, the way I do it is to keep a clone of the site locally, and try out my upgrade procedure on that first, so if it all goes wrong, it doesn't matter. Then I make fresh backups of the main site and repeat the already-tested upgrade actions.
Yes... this is definitely
Yes... this is definitely one of those experiences that will change the way I work. I'm a new developer (self-taught) so I didn't really have those safe guards in place. Time to google "best practices" and get some learn on!
I still haven't figure out why everything's messed up BTW... I think there's some sort of jQuery/Javascript conflict going on, but I can't seem to nail down what it is.
Oh yeah... Thank you CVS!
Ok... I updated some modules and jacked-up my site. I didn't back up my previously working modules, so that was my fault, but I figured out my problem and fixed it! I just thought I'd let people know, just in case someone winds up in the same situation I did.
• If you didn't back up your modules you can usually find your previous working version by clicking on 'View all releases' below the current versions.
• If you updated a 'dev' version of the module it's going to be a bit harder but it can be fixed! Here's what you do:
1. On the module page, scroll down to and click on 'Browse the CVS repository' -- here's where you'll find all the past versions of the module. You can even find some of the past 'dev' versions.
2. Click on the names of the current module's files to find it's revision history. Here you will find all the previous versions of the code.
3. Take the folder for your updated module (the one that's buggy) and then you have to replace the contents of all the files in that folder with the contents of the previous version (the one that used to work). It's easy. Just find the revision you're looking for and click 'download'. The code will appear in your browser window and you can just cut and paste it to rebuild each file.
4. Upload back to your server and install the module... it should work!
5. Vow to never update your modules without backing up the working ones first! Chalk it up to experience and move on to creating your sweet site!
Note: this will not work if
Note: this will not work if your modules have updated their database schema (which they're totally entitled to do). When you make your backups, take a dump of the database at the same time.