-
-
Notifications
You must be signed in to change notification settings - Fork 247
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Patch not executed with new Drupal 8.8 composer structure #300
Comments
This plugin changes directories appropriately to the location that the composer package was installed to. Give it a try and if it doesn't work, please post a complete composer.json that reproduces the problem that you're having. |
Thank you for your answer. We try it and it was not working. How you see is the composer.json outside the webroot (web). So that means if you try to execute a patch it is not working, because the path of the patches are allways inside webroot. Bellow you see an example of the new composer.json. Inside this I have put a patch https://www.drupal.org/files/issues/2019-06-12/2822720-51.patch but it is not possible to execute this patch.
|
Can you also do a |
of corse this is with new composer structure
and this is with old structure. you see, here the patch is working. the versions of drupal/shield are exactly the same.
is strange, looks like the path is change correctly to execute the patch. On both I use 1.6.7 from your module |
What OS are you running? And what version of |
both examples are on same server, with same composer-paches version. one is working the other not. os: FreeBSD 11.3 |
for me is strange, why is one version working and the other not (on same serve with same release)? I try right now and remove --no-backup-if-mismatch and now is working. |
i have no idea why it's working in one install but not another. it could be any number of things, but it's not a problem with this plugin. things to check:
FreeBSD in general has been a weird thing to support for this project. Unfortunately, it's probably not something that's going to be well supported in the future. |
i dosen't understand it, because this is the same server, only another folder....
Did we need the --no-backup-if-mismatch parameter? |
it was important to not have .bak files all over the place. not sure how freebsd handles it. the two issues i linked above have more info about freebsd issues specifically. i don't think this is a composer-patches plugin issue though -- it's a difference in how |
thank you for your answer, how I see is this still an issue with freebsd. I have contact my hosting provider to update the patch module. https://www.drupal.org/project/lightning/issues/2911843#comment-12560493 but another question, is not possible to add a quick check which OS is used and if freebsd execute patch command without --no-backup-if-mismatch? |
I missed it before, but it looks like a patch was being applied to
|
Hi all
In Drupal 8.8 it is recommended a installation like this https://github.com/drupal-composer/drupal-project
That means that composer runs outside the Webroot. Drupal is inside a subfolder (i.e. web). The main problem, the composer runs outside this folder and the patch cannot be applyed, because all patches (from drupal.org) are core/XXX and not web/core/XXX.
So my question, is it possible to take care about the new recommanded Drupal Composer structure? That means is needed to put a path where the "webroot" is. Drupal itselfs have implement this for scaffold module like bellow. So the scaffold module know where the webroot is.
https://github.com/drupal-composer/drupal-project/blob/8.x/composer.json
The text was updated successfully, but these errors were encountered: