he fundamental truth in software industry is that no software is ever final.
Please make sure the patch file you downloaded does not changed somehow at your machine: check the MD5 hash using `md5` or `md5sum`.
Although when it is initially installed, Lightning includes a useful, near-complete default configuration for your website, after it is installed all of that configuration is "owned" by your website.
In almost all cases, these additions and improvements are released as patches. Because of the popularity of Drupal as it powers more than a minion websites, website administrators should make sure that their website runs on the latest version of the software.
There are several reasons why Drupal websites should be updated on regular basis.
It's so easy compared to the method suggested in (download tarball, remove all old files, unzip tarball... If using a custom or contributed theme, switch to a core theme, such as Garland or Bluemarine. diff -Naur drupal-6.14/drupal-6.14-to-6.16.patch drupal-6.17/drupal-6.14-to-6.16.patch --- drupal-6.14/drupal-6.14-to-6.16.patch 2010-03-04 .000000000 0100 drupal-6.17/drupal-6.14-to-6.16.patch 1970-01-01 .000000000 0100 Patch complains it's going to remove it, declaring at the same time it doesn't exist! Fortunately the only remaining items were a few default theme folders, which I manually copied over to my root. I had the same problem with a single site configuration (where the is in sites/default and not in sites/example.com). Today was the first time when I got an error when doing a dry run.
Dick Awesome job friend :) This is a very convenient way to update. But are there any workarounds so that this doesn't happen again? I was wondering because with the --dry-run option I didn't get any error. Currently I'm receiving the following errors: Notice: Use of undefined constant DRUPAL_ROOT - assumed 'DRUPAL_ROOT' in /home1/.../public_html/includes/on line 1971 Warning: require_once(DRUPAL_ROOT../includes/errors.inc) [function.require-once]: failed to open stream: No such file or directory in /home1/.../public_html/includes/on line 1971 Fatal error: require_once() [function.require]: Failed opening required 'DRUPAL_ROOT../includes/errors.inc' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home1/.../public_html/includes/on line 1971 I've been reading all that info and haven't been able to get a good handle on where to set the define("DRUPAL_ROOT", since I dont have an external script, would I make this change in the patch and run it again ? When upgrading 7.0 to 7.2, I get this: Patching file misc/using Plan A...
Now I want to upgrade core to 8.3.2 which comes with composer.
Composer Manager asked me to uninstall this module, as it is no longer supported ...
Being an open source project, anyone could analyze and discover security flaws.
Once found, these flaws are reported in a well-organized manner.
I am trying to update Drupal core version from 7.53 to 7.54 and i am getting following message: Notice: Trying to get property of non-object in entity_get_info() (line 7829 of .../includes/common.inc)....