Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
By mobabo on
This seems like it should have a post somewhere, but I can't find one.
I royally screwed my DB and need to roll back. I didn't change drupal versions, I just attempted to upgrade panels 1 -> 2. Is importing my mySql backup via phpmyadmin all I need to do besides making sure my filesystem contains the old files? Should I delete the existing tables before importing?
Does drupal live anywhere besides the filesystem and the database?
Updating a module is very confusing to me, especially the role of update.php. I was faced with a huge list of my modules saying they had no updates, but I could still select numerical values for them. What the heck do those mean? Which should I choose?
If you understand how to update a module, please visit this thread and post an explicit list of actions: http://drupal.org/node/142767
Thank you!
Comments
=-=
yes
no. you will be dropping the contents of the DB anyway before importing the backup.
You don't adjust the dropdowns. Ever. Manually adjusting the dropdowns leads you into trouble in a hurry. update.php will scan the modules and adjust the dropdowns based on what modules need updating in the DB.
you can expand the menu and look at which module will be updated. Those that are have a numeric value in the dropdown. Those that don't have a numeric aren't going to be touced. Drupal handles this on its own. all you are responsible for is finishing the steps.
Thanks! Adjusting the
Thanks! Adjusting the dropdowns was what killed me, then. That's rather misleading that they all say 'no updates available'.
Is all that is necessary to update a module, then?
-drag new module to file server, overwriting old module
-backup your db!
-run update.php, do not change the dropdowns
-do not disable the old module at any point
=-=
I delete the old module folder. I don't overwrite.
why ? because if the file structure has changed you can leave behind a file that has nothing to do with the module now.
It is possible that a module doesn't need to be updated through update.php. If there is nothing new to be added to cleared from the DB, then update.php won't be necessary.
Should you disable the old
Should you disable the old module before deleting it?
=-=
sometimes I do , sometimes I don't. depends on whether its a major upgrade or not. AFAIK, it can't hurt to do so. though may be an unnecessary step.
I tend to put mysite in offline module to and clear the sessions table to insure noone is logged in and using any part of the site.
I also always delete the
I also always delete the files before adding the new files, but I'm always thinking, what can an obsolete file left behind can harm? Ok it is unnecessary, but it's likely not going to be a big file, so no problem. But nevertheless I'm always deleting files beforehand, because of habit (I did it that way first and it worked without problems, never wanted to try another way for the possibility of meeting problems)
how to roll back
now here is a tricky question :
i installed a newer version of a module (views) and it broke my website (actually only some views) and i don't have a backup of the database (i didn't suspect that using my webhoster's backup function would mean backup only files and not database ... ooops). So i need to roll back to the previous version of the module ... how do i do that ?
Is this correct :
_erase the folder with new version
_import the folder with old version
_run update.php without changing any values there
?
Thanks in advance for your advice.
=-=
if the update to the newer module altered the DB, than you have manual work to do in the database. you can't just change the files and run update.php, it doesn't work that way.
Admin Panel is not working
Hello i need help admin is not opening the dropdown menu
=-=
your issue is not related to this thread. Please generate your own. forum post