34

If you use Drush you can update all security issues with your site via (this is Core and 3rd party modules): drush up --security-only if you want to see what it will do, but not do any of the actual changes you can issue: drush up --security-only --simulate If you want an easy way to update Drupal Core to the newest release you can use a patch site such as:...


20

Welcome to the land of Features Configuration Management, aka FCM! It is not only about Features, and not about Configuration Management (as introduced in Drupal version 8). Instead, it is a special case of Software Configuration Management, aka SCM. Mostly because Features can be considered as a code generator, whereas that generated code needs to be ...


20

There isn't really a right or wrong answer, it will come down to your situation. Composer themselves have pretty strong feelings that yes, you should ignore it, and in an ideal world that's definitely what you should do, but it's not always that straightforward. It depends mainly on your hosting and deployment process. If, for example, you're on Pantheon, ...


19

After talking a bit with CMI maintainers, the discussion on what's the best approach isn't finished but the following is what makes the most sense at the moment. Trying to keep it terse for now, will try to expand based on questions/when the referenced issue is resolved with an official answer. So, first, the facts... As already mentioned, there's the ...


18

Here are a few links that may help you learn more about patching: Applying a Patch Manually Making a Drupal patch with Git (also covers applying) HowTo: How to apply a patch to a contributed module - Beginner's version (Windows) Apply Patches on Windows (more methods) Apply patches on Mac OS How to apply patches for Drupal modules and files


17

You're almost there - what you need to add to your make file looks like this and you have to specify the git url and commit identifier. projects[path_breadcrumbs][version] = "3.x-dev" projects[path_breadcrumbs][download][type] = "git" projects[path_breadcrumbs][download][url] = "http://git.drupal.org/project/path_breadcrumbs.git" projects[path_breadcrumbs][...


16

It just provide good information about the patch. Here is the proper way to name a patch [project_name]-[short-description]-[issue-number]-[comment-number].patch Why? Here is a list of why these name are useful... [project_name] - We use the project name to distinct the patch from other projects. Sometimes some project have multiples sub-modules and it ...


11

A patch doesn't necessarily apply to a new version of a module: It is enough the patched function is moved to a different line, or the code for that function is changed, and the patch doesn't apply anymore. For the function to be moved to a different line, it is enough another function is re-written to take more lines (or less lines). A better way to alter ...


11

For this you need to create a sandbox project and open up an issue in the issue queue of the existing module, posting a link there and urging the maintainer of that project to have a look. If they wish, they can commit that module as the official 7.x version, or might even add you as a co-maintainer of the module if you are interested. In case they do not ...


10

The Drush make approach, as you've already mentioned, is the version my team is using. Even though you are not currently using drush make for your sites, it should be relatively straightforward for you to move to this workflow if you want as drush also provides drush make-generate which will generate the make file from an existing site. Thus no need to feel ...


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


10

drush dl views-7.x-3.x --package-handler=git_drupalorg Update: True, if there are commits after the dev release was packaged, you will need to run git pull to advance to HEAD after checking out via drush dl. If there is no packaged dev release, and Drush checks out a stable release, then you need to run git checkout 7.x-3.x after drush dl. There is no ...


10

How can I tell if someone used this exploit to hack my site? Your Drupal 7 or 8 site can experience loss or theft of data, data can be removed, deleted or changed, wreaking havoc on the site in many different ways. See this Stack Exchange post for general information on checking to see if your website has been hacked. What can they do with this exploit ...


8

Drupal.org uses just one repository for module, and branches for each module version (for example, 7.x-1.x for module in version 1.x for Drupal 7, 6.x-1.x for module in version 1.x for Drupal 6, 7.x-2.x for module in version 2 for Durpal 7, and so on). Also, if your server and client share code you may use just one Durpal module with submodules, so all code ...


8

PHPStorm patching issues have a long history. I have corresponded with their staff more than once, about a year ago. They told me then, that my issue was taken up to developers, but never actually corrected it. Right now, PHPStorm issues patches incompatible with Drupal.org, and we can do nothing about it. To create a working legit patch, you need git, and ...


8

What could happen I had a personal Drupal site hacked during Drupalgeddon, an exploit of similar severity (though of a different type). In terms of "what could happen," in that case the hacker put several "back door" files into my codebase (I knew very little about development at the time, and had no Git repository), from which he could send out spam email. ...


8

Explanation: The problem is that cweagans/composer-patches is applying patches to Drupal Core after cloning it, leading Composer to believe you've modified the affected files and therefore to prompt you to overwrite them lest you unwittingly lose work in progress. Solution: Configure Composer to discard-changes which "[sets] the default style of handling ...


7

The problem is that the current Rules branch is currently failing an already commited test. While this should obviously not be possible, as tests should be green before they are commited, rare circumstances will cause this to happen from time to time. Since an already existing test does fail, we know that testing with your new patch will also fail, whether ...


7

And if you're using YAML for your make file, the following will allow you to preserve the .git repository info: projects: drupal: type: core version: 8.0.x download: working-copy: true And further, if you don't want drush to add in extra information to projects' .info files, make sure you use the --no-gitinfofile option when running ...


7

Try drush dl module-6.x-1.x-dev --svnsync.


7

git add -A is the simple answer you are looking for. It will add all of the files anywhere inside the current working directory, including any new files that were provided or removed pm-updatecode. (Note: git add . behaves similarly to git add -A, except that it will not include removed files in the commit.) There is one inconvenience with git add -A, ...


7

Turn it into a Feature. Bad thing is, it does not work on built-in custom blocks, so you need to use Boxes to get it work. That way, you can export block as a module, and modules are text files, so GIT accepts them with it's full support. Then, there is Features to Git module. It claims: Features to Git allows trusted users to write features directly to ...


7

Just use the format you say doesn't work. This is the correct format. The URL does matter. (Do not use the format that produces the error.) I.e. to clone branch 7.x-1.x of tb_megamenu, you should use: git clone --branch 7.x-1.x http://git.drupal.org/project/tb_megamenu.git You may skip the --branch option and branch identifier when cloning. This will ...


7

The VERSION constant is defined on line 11 of bootstrap.inc: /** * The current system version. */ define('VERSION', '7.41');


7

No need to deal with tags for the dev branch. Tags are only required for stable releases. Since you have already added your dev branch you just have to add your files, commit them and push them, like this: git add path/to/files git commit -m "Commit message" git push origin 7.x-1.x Then you just wait for drupal.org to reroll a new dev version. It takes up ...


7

Merge conflicts are probably going to be a given when multiple developers are integrating their configuration into a Feature. I wrote up several guidelines for reviewing feature code, but I think the most important is this: Only commit intended code changes. What does this mean? This means that each developer must review code before committing. There is no ...


6

There's a description in every module under the tab version control. Scroll down to the title "Applying a patch" to find a description about applying patches with git.


6

I'm not a Git expert, but as I understand it all of the releases of the dev branch listed on the project page are made directly to the 7.x-3.x branch. Of course you're free to create your own branches locally for your own needs, but the master-like branch, which includes all of the releases pushed to drupal.org, is always going to be that 7.x-3.x branch. ...


6

Use Drush Make. It's built into Drush 5. Your makefile will serve as not only documentation of what patches you're using, but documentation of what versions of everything you're using, where to download external libraries, it's practically guaranteed to be up to date, and it means you no longer have to store contrib and external code in your source code ...


6

If you can shell into the account, you cd /var/www/somewhere/docroot/sites/all/module patch -p1 < /path/to/the/patchfile Depending on how the patch was rolled, you may need to adjust the number after the -p to get it to apply properly. The man page can give you more details. If you can't shell into the host, then you need to downloads the files(s), ...


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