I installed (or downloaded) drupal 8 via:  composer create-project drupal/drupal my_site_name 8.0.*  Which, at the time I ran it, downloaded Drupal 8.0.1.  Now drupal 8.0.2 is available and I'd like to update to this version.  I'm not sure how to update core but I decided to try running composer update from my drupal site's root directory.  This updates many packages (e.g.):  $ composer update Loading composer repositories with package information Updating dependencies (including require-dev)   - Removing composer/installers (v1.0.21)   - Installing composer/installers (v1.0.22)     Loading from cache  &gt; Drupal\Core\Composer\Composer::vendorTestCodeCleanup   - Removing symfony/class-loader (v2.7.6)   - Installing symfony/class-loader (v2.7.9)     Downloading: 100%  &gt; Drupal\Core\Composer\Composer::vendorTestCodeCleanup   - Removing symfony/console (v2.7.6)   - Installing symfony/console (v2.7.9)     Downloading: 100%  (...)  &gt; Drupal\Core\Composer\Composer::vendorTestCodeCleanup   - Removing twig/twig (v1.23.1)   - Installing twig/twig (v1.23.3)     Downloading: 100%   However I don't see anything about updating drupal/drupal.  And when I visit my site's status report it still shows 8.0.1.  So how do I actually update core via composer?
122855
I want to use composer to manage Drupal 8 dependencies, but I'm not sure what is the right core update workflow. At the moment I'm using drush to update core to latest beta release, but I also have some dependencies in my composer.json file, so after the update I'm using composer install to install all the contrib vendor dependencies. It appears that running composer install overrides some files in the core directory, although I've just updated core to latest version.  I've also tried to manually edit the composer.json file and replace the "drupal/core" line with the specific beta release, e.g. "drupal/core": "~8.0-beta14",, but it still overrides files in the core directory.  What is the right workflow?
97575
I'm currently using precise. I need to upgrade a certain package (namely  and it's dependencies) to a newer version, which is currently found in raring (alfa at the time of writing this). How to do it ?  What will happen if I just add to my sources.list:  deb http://archive.ubuntu.com/ubuntu raring main   Will the next apt-get update / apt-get upgrade, upgrade most of my system to raring then ?
96856
I'm on an old Ubuntu version (Ubuntu 6.06.2 LTS Server) which isn't really supported any more. So the automatic updates don't work. I have ISPConfig installed to manage a few web sites.  What's the best course of action? I'd like to upgrade to something current, but I can't figure out how to go about doing this, given that the apt-get scripts don't really work any longer.
53671
The new  is pretty neat to get the patches created/reviewed/merged. However, if you are using the patch via , we have a few options. Option 1: we can use the MR  to add the patch like this: &quot;drupal/message&quot;: {   &quot;3186091&quot;: &quot;https://git.drupalcode.org/project/message/-/merge_requests/1.patch&quot; }  but it means any new change pushed to the fork/branch, would get automatically added. As the patch file gets pulled on composer install. Option 2: We could use the fork's  and commit hash to keep the patch static, but once the MR merged, the fork might get deleted and breaks the build. Option 3: Obviously we can generate the patch from the MR and upload to the issue comment, but it seems a duplicate effort and hard to keep up with an active core issue (right now, we just need to update the patch file in composer.json or composer.patches.json) Is there a way to have the current patch file behavior in the new fork based issue queue? UPDATE: Both option 1 and (probably) option 3 are documented on
8139
I have a Drupal site 8.6.10 on an Ubuntu server 18.04 with MySQL 5.7.25  I want to update MySQL to version 8.0  Here are the steps I followed :   I backed up my database. I uninstalled MySQL from my server with the commands :  $ sudo systemctl stop mysql $ sudo apt remove mysql-* $ sudo apt purge mysql-* $ sudo apt autoremove $ sudo dpkg -l | grep mysql | grep ii  I added the repository with the command :  $ wget https://repo.mysql.com//mysql-apt-config_0.8.12-1_all.deb  I installed the package with the command :  $ sudo dpkg -i mysql-apt-config_0.8.12-1_all.deb            My problem :   I install MySQL with the command :  $ sudo apt update $ sudo apt install mysql-server    When I do step 5, it installs MySQL 5.7 why does not it install version 8 ?
85552
I am performing an update and its failing on the following:  The repository 'http://ppa.launchpad.net/izx/askubuntu/ubuntu xenial Release' does not have a Release file..   Running a local Ubuntu server 16.04
105202
How to install latest Code::Blocks using codeblocks_17.12-1_amd64_stable.tar.xz?  Software center has an old version and I am not able to configure. How to install? Why is there no documentation for installing?
38412
I did  step by step ( also finally rebuild the cache) but yet my changes in twig files not take effects without rebuild the cache.  sites/default/services.yml :  parameters:     session.storage.options: { gc_probability: 1, gc_divisor: 100, gc_maxlifetime: 200000, cookie_lifetime: 2000000 }     twig.config: { debug: true, auto_reload: true, cache: false }   sites/default/settings.php :   if (file_exists(__DIR__ . '/settings.local.php')) {    include __DIR__ . '/settings.local.php';  }   sites/default/settings.local.php :  $settings['container_yamls'][] = DRUPAL_ROOT . '/sites/development.services.yml'; $config['system.performance']['css']['preprocess'] = FALSE; $config['system.performance']['js']['preprocess'] = FALSE;   sites/development.services.yml :  services:   cache.backend.null:     class: Drupal\Core\Cache\NullBackendFactory parameters:   twig.config:     debug: true     auto_reload: true     cache: false   Where is the Problem?
111046
I offered a friend to help translate from English some parts of his (mostly) Hebrew install. Then he told me two things:   1) That he's running 2.8 (he was worried about updating because he didn't want the design to break)   and 2) That he has reason to suspect that the site is infected with a trojan horse since it gets blocked by some antiviruses.  1) What is the best way to go about upgrading? is it even feasible to start on a fresh installation and still have everything intact? including redirects? or will I have to go about it as per WP's documentation: step by step upgrading.  2) What can be done about the trojan horse? this is why I'm contemplating a fresh install, which I know is probably not recommended.  Thank you in advance
65330
I'm trying to find a copy of 6.20 to run a diff on a client's Drupal install. I believe there's been changes to core.   How can I get version 6.20? Additionally, how can I download any older Drupal versions?
117397
I went through my usual server package upgrades today and discovered that ppa:ondrej/php5-5.6 has been depreciated and we must now upgrade to ppa:ondrej/php.  The basic provided instructions are to run:  sudo add-apt-repository ppa:ondrej/php   And then:  sudo apt-get update sudo apt-get upgrade --show-upgraded   Looking at the new repository, the names do not seem to completely line up so I think I'll need to do some apt-get installs to get all the right packages installed.  It also appears that the sub-packages (ie php-gd) will install for all php versions and may also install php 5.5 and php 7.0 ()  So my question is, what is the cleanest way to "switch" ppas and clean up the existing packages considering that this is a production server?  Should I try to remove all the packages installed from the previous PPA and/or remove the PPA from my system?  It's not yet in the main page for the PPA but the upgrade message gave deprecation as June 2016 so it's not a very long timeline to rebuild our server image.  I did find this page, which provides instructions for switching out the PHP version apache uses:
23806
I've been using Drupal for several years, but only just dipping a toe in with Drush - I've bought an ebook tutorial and working my way through. I've installed Composer, and used it to install Drush. The tutorial book specified a particular build of Drush to install (7.0.0-alpha5). I've navigated to a drupal folder and run   drush st    to get installation info which works fine. The tutorial explains that you don't have to navigate into the drupal folder to do this, instead using  drush --root=PATH-TO-DRUPAL-SITE st   however this brings an error:   Fatal error: Call to undefined function conf_path()   Googling this error suggests this a problem with the version of Drush and to upgrade.  SO I've navigated into the .composer/vendor/drush/drush folder and run      composer global update but composer says nothing to update, confirming the version as 7.0.0-alpha5 - I assume this is not the latest 7.x version, so do I need something changing in the composer.json file?
34508
In a current project I have had to patch the life out of a few modules (node hierarchy, workbench access and a few more). These modules are now absolutely perfect for the project's needs and are very unlikely to break with future updates to core.  That being said, when the app is handed over the clients will have full (user 1) access to the system and will therefore be warned when these modules have available updates. And they will update them, no matter how many times I beg them not to (oh how easy life would be without clients!).  Is there a way (perhaps in the modules' .info files) to persuade the update manager not to check for updates for these modules?  EDIT  I'm aware of the project status url key that's available for the .info file so I guess I could set that to a non-existent URL but I'd much rather do this in a clean way if possible.
114941
In Drush 8, my site aliases are loaded correctly from ~/.drush/mysite.aliases.drushrc.php.  E.g.  $aliases['dev'] = array(   'root' =&gt; '/var/www/html/mysite.dev/docroot',   'uri' =&gt; 'mysite.prod.acquia-sites.com',   'remote-host' =&gt; 'mysite.ssh.acquia-sites.com',   'remote-user' =&gt; 'mysite.dev',   'path-aliases' =&gt; array(     '%drush-script' =&gt; 'drush' . $drush_major_version,   ), );   However these aliases aren't loaded in Drush 9.  $ drush site-alias {  }   How I should define site aliases in Drush 9? Is there any migration process?
111788
I'm pretty new to running linux, but I know that 19.04 was released today and I wanted to upgrade from my current 18.10. However, when I follow the release notes here:  I get the message "The software on this computer is up to date". I made sure that my update settings are set to "any new version" and "normal" in the /etc/update-manager/release-upgrades file.   What am I doing wrong?  Thanks for the help!  Side note: I had to disable this PPA:  because it would cause errors in apt updating. Do I need to re-add it? If so how do I do so without it giving me an error?  Edit: I have followed the procedure recommended in the documentation which is identical to the suggested duplicate, but I am not given the option to upgrade. I have not yet tried the   do-release-upgrade -d    option as I don't want to upgrade to the developer version.
88284
How can I install the latest  FileZilla from its official ?  I can find FileZilla from my software centre and install it. But it is version 3.24.0. While the latest is 3.25.2.  Can I upgrade the version 3.24.0 that I have already installed to 3.25.2?  I always wonder how to install from its official site, but it is not a .deb. It looks like the source files of FileZilla that you need to compile or build. But how can I do it?  Any ideas?  This is from the site but it is just not very helpful to me:     Installing on GNU/Linux and other Unix(-like) systems      It is recommended that you use the package manager of your   distribution. If you're using GNU/Linux, you can also try using the   precompiled binaries. After extracting the files to any location   (location does not matter, FileZilla can detect its own installation   prefix), you can start the program using the filezilla executable in   the bin/ subdirectory. Please note that due to differences in   distributions, the provided binaries might not work on your system.   Alternatively you can also compile FileZilla from source.
65935
I have a shared hosting account on which i have created sites using joomla 2.5 and drupal 7.  I want to use drush to apply patches to existing modules for my drupal 7 site.   Can any one guide me as to how can i install this drush and use it for these drupal 7 sites on my shared hosting ?  Step by Step Guide would be highly appreciated (New here)   Thanks