Features
Field Import module enables you to import fields to a content type from a csv file.
Fields can be imported into an existing content type or a new one which will be created upon import.
Drupal naming conventions should be followed for the fields to be imported.
Basic Installation & Configuration
Refer to the Readme.txt file included with the module which contains additional information.
Dependency
Any field type specified in the csv file should have it's dependent module installed else exception will be thrown.
For example to create a field of type "email" the necessary dependent Email module should be installed.
Git Clone Command
git clone --branch 7.x-1.x https://git.drupal.org/sandbox/jack_ry/2788849.git field_import
cd field_import
Project Page - https://www.drupal.org/project/fieldimporter
Reviews of other project
https://www.drupal.org/node/2756909#comment-11652683
https://www.drupal.org/node/2606194#comment-11677249
https://www.drupal.org/node/2771203#comment-11655739
https://www.drupal.org/node/2683891#comment-11736078
https://www.drupal.org/node/2687695#comment-11829023
Comment | File | Size | Author |
---|---|---|---|
#30 | Screen Shot Fields.png | 60.84 KB | gopagoninarsing |
#30 | Screen Shot -Warning.png | 85.63 KB | gopagoninarsing |
#30 | Screen Shot - cvs used.png | 11.21 KB | gopagoninarsing |
#21 | field_name.png | 14.11 KB | ganesan g |
#21 | template_error.png | 28.17 KB | ganesan g |
Comments
Comment #2
PA robot CreditAttribution: PA robot commentedGit clone command for the sandbox is missing in the issue summary, please add it.
We are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)
Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #3
yogeshmpawarComment #4
jack_ry CreditAttribution: jack_ry commentedComment #5
jack_ry CreditAttribution: jack_ry commentedI have updated with the git clone command
Comment #6
yogeshmpawarComment #7
yogeshmpawarPareview.sh is giving following errors.
http://pareview.sh/pareview/httpsgitdrupalorgsandboxjackry2788849git
Will do a manual review in some time.
Comment #8
PA robot CreditAttribution: PA robot commentedProject 1: https://www.drupal.org/node/2803019
Project 2: https://www.drupal.org/node/2796315
As successful completion of the project application process results in the applicant being granted the 'Create Full Projects' permission, there is no need to take multiple applications through the process. Once the first application has been successfully approved, then the applicant can promote other projects without review. Because of this, posting multiple applications is not necessary, and results in additional workload for reviewers ... which in turn results in longer wait times for everyone in the queue. With this in mind, your secondary applications have been marked as 'closed(duplicate)', with only one application left open (chosen at random).
If you prefer that we proceed through this review process with a different application than the one which was left open, then feel free to close the 'open' application as a duplicate, and re-open one of the project applications which had been closed.
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #9
jack_ry CreditAttribution: jack_ry commentedComment #10
jack_ry CreditAttribution: jack_ry commentedPareview.sh errors are fixed
Comment #11
jack_ry CreditAttribution: jack_ry commentedComment #12
jack_ry CreditAttribution: jack_ry commentedComment #13
jack_ry CreditAttribution: jack_ry commentedComment #14
jack_ry CreditAttribution: jack_ry commentedComment #15
jack_ry CreditAttribution: jack_ry commentedComment #16
jack_ry CreditAttribution: jack_ry commentedComment #17
jack_ry CreditAttribution: jack_ry commentedComment #18
jludwig CreditAttribution: jludwig as a volunteer commentedPlease link to your Project page in the issue.
Automated Review
All Pareview.sh errors are now fixed and it's only recommending setting up tests. http://pareview.sh/pareview/httpsgitdrupalorgsandboxjackry2788849git
Manual Review
The starred items (*) are fairly big issues and warrant going back to Needs Work. Items marked with a plus sign (+) are important and should be addressed before a stable project release. The rest of the comments in the code walkthrough are recommendations.
This review uses the Project Application Review Template.
Comment #19
jludwig CreditAttribution: jludwig as a volunteer commentedComment #20
ganesan g CreditAttribution: ganesan g commentedI tried using this module and found the following errors.
Attaching screenshot(field_name.png). Please convert human readable name to machine name while saving the field.
Edit: Following error i got when i try to import the field which has human readable name.
FieldException: Attempt to create a field field_Demo_two with invalid characters. Only lowercase alphanumeric characters and underscores are allowed, and only lowercase letters and underscore are allowed as the first character in field_create_field() (line 67 of /var/www/html/gango-learning/modules/field/field.crud.inc).
Comment #21
ganesan g CreditAttribution: ganesan g commentedAttaching the screenshot of errors.
Comment #22
jack_ry CreditAttribution: jack_ry commentedGanesan Gopal,
I fixed all the errors you have mentioned. About that template error please have a look into read me.txt file. I have mentioned reasons there.
Comment #23
jack_ry CreditAttribution: jack_ry commentedHi Ludwig,
I have added a custom permission for my module as per your suggestion.
The reason I have added an xlsx file is to reduce the additional effort/skills required by a user compared to when creating them via UI. Beginners may not be aware of field types as they choose field type in UI. That's why I have provided possible field types as a dropdown in xlsx file which is not possible if it were a csv. I am open to your suggestions and alternatives in this.
Comment #24
jack_ry CreditAttribution: jack_ry commentedComment #25
PA robot CreditAttribution: PA robot commentedFixed the git clone URL in the issue summary for non-maintainer users.
I'm a robot and this is an automated message from Project Applications Scraper.
Comment #26
ARUN AK CreditAttribution: ARUN AK commentedfield_import_info_form_submit(): While importing label is not creating properly from field name. If set "My Name" as FIELDNAME in template, machine name of field will be field_my_name as well as Label also same.
field_import_info_form(): As the "Skip Header" checkbox is a required field in form, it should be checked always when executing an import. Either remove it or implement conditional field functionality.
Thanks for your participation, but I'm afraid the reviews you did are not very detailed and not really "reviews". Removing review bonus tag, you can add it again if you have done another 3 reviews of other projects. Make sure to read through the source code of the project. For more detail please go here https://www.drupal.org/node/1975228.
Comment #27
jack_ry CreditAttribution: jack_ry commentedComment #28
jack_ry CreditAttribution: jack_ry commentedHi Arun,
I have fixed the errors you mentioned. Will do the rest of the reviews in sometimes later. For now I am changing the status.
Comment #29
jack_ry CreditAttribution: jack_ry commentedComment #30
gopagoninarsing CreditAttribution: gopagoninarsing as a volunteer and at Azri Solutions commentedHi,
I have tested this module with Drupal 7.53 , below are few findings.
Comment #31
jack_ry CreditAttribution: jack_ry commentedHi Narsing,
I have fixed the warnings & label issue. Thanks for reviewing my module.
Comment #32
jack_ry CreditAttribution: jack_ry commentedComment #33
jack_ry CreditAttribution: jack_ry commentedComment #34
jack_ry CreditAttribution: jack_ry commentedComment #35
jack_ry CreditAttribution: jack_ry commentedComment #36
jack_ry CreditAttribution: jack_ry commentedComment #37
Mario SteinitzSorry, but pushing the priority won't help. The Git admins seem quite busy (the recent years)...
The module itself seems free from obvious code styling issues.
What bothers me is the function doc headers.
When implementing hooks, it's allright to just use "Implements hook_...().". But for your custom callbacks and forms, please add according parameters and return value descriptions.
Also, please add a brief summary to your submit callback
field_import_info_form_submit
doc comment block, telling what it does. So nobody has to read over the inline comments within its 100+ lines function body to understand what's going on inside.Some nice-to-have extras:
I'd suggest placing the admin-link beyond Configuration/Development or Structure instead of the root of the admin menu.
Also, I'm wondering why you provide an *.xlsx file as template, whereas the form is accepting CSV only?
Comment #38
jack_ry CreditAttribution: jack_ry commentedMario,
Thanks for the suggestion. I have made the changes.
Regarding the xlsx file, I have explained it here
https://www.drupal.org/project/projectapplications/issues/2796315#commen...
Comment #39
jack_ry CreditAttribution: jack_ry commentedComment #40
jack_ry CreditAttribution: jack_ry commentedComment #41
sleitner CreditAttribution: sleitner commentedStable releases for this project are already covered by the security advisory policy.
Comment #42
apaderno