If you are happy to update continue with the update. Over time it is a good thing to do this as you can see new features added or if you had patched the module for a bug you may see that the issue has been fixed and thus the patch is no longer needed. Read the release note if you feel the urge. To update using the GUI is as simple as following these steps. Okay, with that out of the way we can move on with the updating of our site modules. Check the Updating Drupal core article's preparation section for more details on that. PreparationĮven if your staging site is an exact copy of your current production site I would still suggest making a backup of both the files and the database. I won't cover this here as this is an advanced topic and this article is aimed at smaller sites. I will also mention, as your site becomes more complex as your business grows you may update your production site using a Git workflow and the built-in configuration management. htaccess directives if you have your site set up in a sub-directory. To create a staging site you will need to copy the site files and duplicate the database to a new database, and then change the settings.php database configuration. Before we update our live site or production site however we need to make sure we have first tested the update or updates on what is commonly known as a staging site. In this article, we will be looking at both ways. Updating Drupal Module is a fairly painless process whether you manage your website using the GUI or using Composer.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |