65

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.


34

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


17

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 ...


10

It seems from discussion above that your question isn't about fixing your git repo, but about maintaining a Drupal site in git, and how that works with core updates. I think that standard practice is in fact keeping all files in your repository, including Drupal core. The separation of Drupal code from custom code seems like a nice idea, but I don't think ...


7

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

I have not found a better alternative to migrate module till date and I have done lots of migration including ubercart order migration. It has served me well for: ASP.Net (MSSQL server) -> Drupal migration D6 -> D7 Migration Rails (MySQL) -> Drupal Migration There are tons of other modules like node_export, views bonus pack, uuid features, deploy that ...


5

Drupal is very sensitive to the order you do things when doing a major system upgrade. You must follow the instructions in UPGRADE.txt exactly; in particular, if you run updatedb just once, after upgrading your core and all of your contrib code, then the upgrade is sure to go wrong. The symptoms can vary; I would expect that this is probably what is ...


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

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

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

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)....


4

I'm assuming you're on a shared server. Here are some options. Option 1 - Downgrade PHP. Although it might not be the safest choice, as both the PHP and Drupal is probably no longer supported, you can do the following. Some hosts allow to specify a different PHP version in php.ini. Rent a cheap VPS, which will allow you to set the PHP version. Some shared ...


4

Although there is a pear package for Drush-8.x-6.x, if you are going to run this version of Drush I would recommend cloning it from git, and updating it with git pull. You can also check for newer code with git status instead of drush self-update. Discussions on the deficiencies of drush self-update should probably happen in the Drush issue queue. Briefly, ...


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

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 ...


3

It's not necessary. I have migrated one large site from Drupal6+Views2 to Drupal7+Views3 in just one step. You have to take in account that views3 (views_ui submodule) depends on ctools. If you follow this path you have to disable views_ui before the upgrade and activate views_ui (and ctools) once the upgrade has finished.


3

Before upgrading the drupal core, you must deactivate your contrib modules. I think you did not.? Upgrade the core first. Then upgrade any contrib modules. If you have used cck in drupal 6, you will need the cck module to do the migration.


3

The code you should use in Drupal 7 is similar to the following one. function custom_inline_filter_info() { $filters['custom_inline_filter'] = array( 'title' => t('Custom Inline Filter'), 'description' => t('Substitutes @inline tags with the uploaded inline images of the node.', array('@inline' => '<!-- INLINE -->')), 'cache' =&...


3

You can upgrade directly to the new version as it contains all the previous changes as well. But don't forget to follow the backup instructions...


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. ...


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