66

In this case, it looks like you need to do drush rf # pm-refresh before you do drush up drupal This will refresh the list of available updates so Drush knows there is a new release for Drupal.


38

Worth mentioning is $ drush up --security-only Only update modules that have security updates available. That includes Drupal core.


18

I guess the best place to search for upgrade process is UPGRADE.txt file. Here you can find the step-by-step approach to follow in upgrading the site from Drupal 6/7 to Drupal 8. Drupal 8 core will include a robust data migration API: https://drupal.org/node/2121299, part of the IMP initiative: https://groups.drupal.org/imp . Also you can check the recently ...


9

drush up drupal Appending the project you want to update makes drush to only update that project.


7

Please also keep in mind there are '0-day' vulnerabilities out there, which can be used to compromise your website even before Drupal publishes a security advisory and corresponding patch. And that even if you use an automated update for Drupal core, there still will be a time window in which your site was vulnerable. The best way to deal with these kind of ...


6

Yes, upgrading from Drupal 8 to 9 is scheduled to be an incremental update from the last minor version of Drupal 8. It seems the main thing to consider is to remove any usage of deprecated functions to ensure a smooth upgrade. Contributed project developers, as well as those maintaining custom integrations, should follow the deprecations when possible ...


5

You can build a site totally with git to help manage this process. The process is basically Git clone into your DOCROOT: git clone --branch 7.x http://git.drupal.org/project/drupal.git /var/www/mysite/docroot Rename the remote: git remote rename origin drupal Checkout the latest tag, and make a site branch for your site: git checkout 7.26 git branch -b ...


5

To figure out what was the problem, thanks to this post I opened include/error.inc and replaced print theme('maintenance_page', array('content' => t('The website encountered an unexpected error. Please try again later.'))); with print theme('maintenance_page', array('content' => t('The website encountered an unexpected error. Please try again ...


5

Simply put, you cannot unless you are willing to rewrite a lot of Drupal 7 parts. One thing you can do, is to implement cron jobs to export changes in version-independent format like XML on source site, and import them from XML at target site. Alternatively, you can use Services module and make one page call the other to perform certain tasks, like user ...


5

No. The old method of upgrading Drupal through update.php has been dropped in Drupal 8 in favor of the Migration framework & UI. The idea here is to provide a clean way into a new database schema without any problems of update.php trying to accommodate many diverse scenarios (as it was prone to do with moving complex sites from D5 to D6 & D6 to D7)....


5

Sounds like Composer doesn't know about Drupal's packages, which suggests you're missing a reference to the repository in composer.json. Add this and you should be good to go: "repositories": [ { "type": "composer", "url": "https://packages.drupal.org/8" } ]


4

The Hacked! module is exactly what you're after: This module scans the currently installed Drupal, contributed modules and themes, re-downloads them and determines if they have been changed. Changes are marked clearly and if the diff module is installed then Hacked! will allow you to see the exact lines that have changed.


4

One way to solve this, is as follows: Create a set of patches that patches any altered files (i.e. .htaccess, robots.txt, and other files where you're have added customization). After downloading the new minor release of the core, apply the patches. Check if there are any conflicts. If there are no conflicts, great - you're done! If there are conflicts, ...


4

One way to do it would be to pore through the CRM/Upgrade/ directory in the new version, looking for schema changes. However these are distributed across multiple files, depending on which alpha or beta version the change was introduced in. E.g. the next_sched_contribution_date change was introduced in this file: civicrm/CRM/Upgrade/Incremental/sql/4.4....


4

An easier way of doing it from a pure structural perspective is to use a mysql schema diff tool, something like: http://adamspiers.org/computing/mysqldiff/ However that might not give you all the changes, but i suspect will catch most changes. A lot better to do it in an automated way, IMO :)


4

Another option would be to diff the xml schema between versions. The xml schema files are not shipped in the tar.gz releases, only in git, so it's not exactly the most user-friendly method, but it could be a good starting point. You could also try: git log -w -p tag1..tag2 xml/schema For example: git log -w -p 4.4.5..4.5.2 xml/schema Not perfect, but ...


4

Is it possible to update the PHP version of an existing Drupal site that is installed on a local server on Ubuntu? Yes, upgrading server software for existing applications is common practice both inside and outside of the PHP/Drupal worlds. If your operating system supports a newer version of php than you currently have, and Drupal (plus the contrib ...


4

Normally you should never hack the Drupal core. However, there are few exceptions: you're applying patch downloaded from Drupal.org which has been QA tested, you're applying patch implemented by people who're extremely familiar with the Drupal code base, development practices, and security model, you've tested the patch using unit tests (SimpleTest) ...


4

Prior to newer version of Media, media_wysiwyg_filter should be used instead which will perform media markup filter. This can be found in modules/media_wysiwyg/includes/media_wysiwyg.filter.inc. The code is: /** * Filter callback for media markup filter. */ function media_wysiwyg_filter($text) { $text = preg_replace_callback(MEDIA_WYSIWYG_TOKEN_REGEX, '...


4

Yes, replace the core and vendor directories and run update.php. Note: Also please follow the instructions from upgrade.txt. There are several other necessary instruction so that you can recover from any mishappening. Drupal treats 8.0.x and 8.1.x as 8.x.x.


4

You could try drush pm-updatestatus drupal and see if you get any results.


4

With version 9.1.0 (release notes) Drupal Composer templates no longer use minimum-stability dev as in the past this occasionally produced unexpected results, such as upgrading to newer unstable releases. This is what's currently happening to you. Raised minimum stability will not affect existing projects; this has to be done manually. For production ...


4

In theory you should update to the latest recommended version of your current site's minor release. So in this case you should update to version 8.9.13 then you should be good upgrade. Remember to also make sure you do the same for all contributed modules and themes. You might find using the Upgrade Status module helpful before upgrading. As with everything ...


3

I can see there is some jquery script adding the string 'Test' for each view row . Look into your code base for the string '.view-id-blog .views-field-body' and you'll find out from what file is it coming. You may also want to disable javascript aggregation for sometime, and then see the exact file name in the developer tools directly.


3

It depends of your Simpletest tests. Upgrade your site in a test environment (stagging ideally) and then run your Simpletest tests. If tests are ok you can be sure that everything covered by your tests is ok. If your question is if Simpletest can create nodes, yes, it can. What Simpletest can't do is test Javascript. If you need to test Javascript you ...


3

taxonomy-term.tpl.php is used in Drupal 7. You can find it in ROOT_DIRECTORY\modules\taxonomy\taxonomy-term.tpl.php. To override this template, copy it, place it in your theme template directory, and modify it. Don't forget to clear the cache to see the output from the modified template. Do not modify any core files (including template files), in any case. ...


3

The best practice is to find some way to implement your feature that does not require patching the original core. You should try to read - Why don't we hack core? Anyway, if you still want (or need) to maintaining your Drupal Core with a patch you can use any of this projects to manage your patches. https://github.com/davereid/drush-patchfile This ...


3

drush dl drush downloads the obsolete version of Drush from drupal.org. Drush was never intended to be used to download Drush via the pm-download command, even when it was hosted on drupal.org; the fact that this works is more of an anomaly or coincidence than design. To update to a newer Drush, follow the usual instructions in the Drush documentation. ...


3

I've spent the past few months doing a lot of D7 -> D8 upgrades. I haven't used sub_name (or even seen it), so I cannot comment on that, but as for the path, it's the same path you declared as the array key in your hook_menu definition - however note that with D8 you need to include the preceeding forward slash. So if your D7 hook_menu() definition for a ...


3

Is it possible to full upgrading with solely Drupal/PHP? In the sense that anything is possible given enough time/effort, yes. Should you? Not unless you want to spend a lot of time building a bespoke, error-prone (especially if you're scoping in any modules, themes, etc.) process that will only work under the narrow scenario in which you developed it. To ...


Only top voted, non community-wiki answers of a minimum length are eligible