Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I faced many issues with the module and found many patches to fix but cannot apply all patches due to missing ones which are not in the last or dev version.
The module needs his maintainer to review and commit the patches, for example, I wrote a simple patch to add Drush command to import content instead of disabling and enable the module and to bypass not imported during installation
Comment | File | Size | Author |
---|---|---|---|
#16 | import_from_module-2783861-16.patch | 944 bytes | yogeshmpawar |
| |||
#8 | import_from_module.patch | 1.08 KB | mhmd |
import_from_module.patch | 876 bytes | mhmd | |
Comments
Comment #2
larowlanThere are no patches RTBC https://www.drupal.org/project/issues/default_content?status=14 so I'm not sure what you mean by 'The module needs his maintainer to review and commit the patches'. The module is a key plank of the agov install profile and is working as expected, with test coverage.
So is this a new issue/feature or a duplicate of an existing one?
Also, I find your tone offensive, we're all volunteers.
Comment #3
larowlanSupport requests cannot be major see https://www.drupal.org/node/45111#major
Comment #4
mhmd CreditAttribution: mhmd as a volunteer and commentedDear Larowlan,
I appreciate the work it's very good and we are all (the community) benefit from it, I am sorry if my words were offensive.
I mean that I found old patches for feature and support requests that give errors when I used them as I need to contribute to the module.
the issues that needs review are:
- The module does not import when to install drupal despite being enabled so I have to disable and enable it again in order to work and import happen.
- The module imports the previously imported content before
Feature requests are :
- Simple drush command to import new content.
- Exported content to be put in /content not in the root for the project.
I realized that many patches date after the last dev version, So we could review patches and commit to the module or the dev version,
If something wrong please let me know.
Comment #5
larowlanAh, so if the patches no longer apply, they need to be re-rolled..
In terms of issues that need review, that doesn't need the maintainer. Anyone can review.
If you review it and it solves your problem - and you're happy with the code, please change the status to 'Review and tested by community', that's the point from which it gets committed.
Comment #6
larowlanThanks for your contribution - new title to reflect what this command provides.
Comment #8
mhmd CreditAttribution: mhmd as a volunteer and commentedNew patch works fine with git apply from the module directory
Comment #11
andypostComment #13
yannisc CreditAttribution: yannisc at Netstudio commented#8 worked for me.
Comment #14
andypostComment #16
yogeshmpawarI have rerolled the patch & its working for me.
Comment #17
keesje CreditAttribution: keesje commentedPowerfull feature with potential to open up a can of worms.
Tested #16 and works the first time. If any of the imported entities already exists, or another entity with the same ID an error "Integrity constraint violation: 1062 Duplicate entry" occurs.
default_content_modules_installed() is designed to run once at installation, there is no check on existing entities. We need a way to update existing entities. How? overwrite and resave? skip? Could be a slippery slope if this is used for nodes with revisions an/or entities with relations to other entities. Existing "lower" entities like paragraphs could easily become orphaned. And what about deletion of previously imported and now removed entities? Maybe this module is not designed for keeping things in sync.
Comment #18
keesje CreditAttribution: keesje commentedouch, this is probly a duplicate of https://www.drupal.org/node/2640734...
Comment #19
ao2 CreditAttribution: ao2 as a volunteer commentedI am going through the issue queue and this really looks like a duplicate of #2640734: Allow manual imports, so I am closing it, I hope the maintainer doesn't mind.
Comment #20
andypostyep, let's focus on that issue!