Port request: Field tools

[LucianoGit-x6zeta]

Name of the module, theme, or layout field_tools

Link to the drupal.org module, theme, or layout https://www.drupal.org/project/field_tools

(Optional) Link to an issue in the drupal.org queue asking the Drupal community if anyone is working on a Backdrop port of this project It is a fantastic module with many tools that do not exist in the configuration export. For example the selective export / export of fields from the list of fields of a content type which makes it easy to create a new site from scratch only the code of the fields of interest. I tried the conversion with coder upgrade but a dependency on ctools is not resolved and I am not doing more not being a programmer. Thank you and sorry for my bad English.

[argiepiano]

Ciao, Luciano! Welcome to Backdrop.

This looks like an interesting module that does a lot of things - porting it seems like a big job. Looking at some of the features, some of them are already available in Backdrop, specifically the ability to export selected fields and field instances in admin/config/development/configuration/single

Since this is a large project, perhaps rather than porting the whole module, if you have any specific features you'd like to see included in Backdrop (or as a contrib module) you can do a feature request at the github backdrop/backdrop-issues queue, or work with people to create a custom module. I also suggest you participate in the Backdrop Zulip channels - that's a great way to connect with users and developers.

[LucianoGit-x6zeta]

Hi Argepiano, as you say, field tools offers many features. In fact, I don't even know some of them because I've never used them. However, the functionality that I find really useful and that I would like to find in the backdrop is: -Import and export of fields-. The difference with the single export of the backdrop fields configuration is that it is possible to easily choose the fields to be exported through a single interface, obtaining the cumulative code of all the selected fields. Importing the chosen fields into a new content type (even in a site on another server and completely disconnected with the site from which we are copying the fields) is just as simple by simply pasting the aforementioned code. I would very much like to participate in the Backdrop Zulip channels if I had the ability to make some contribution to the community but, unfortunately, I am not a programmer and my poor knowledge of English does not help

[argiepiano]

Caro Luciano: Interesting. That particular feature shouldn't be hard to accomplish in a separate contrib module. Does this also export all the field instances? Instances are site-related, as they refer to specific content types or bundles...

As for Zulip: everyone is welcome to join! Not just developers. It's a great place to get quick answers (and to also provide answers to questions). As for your English: it seems perfectly fine to me! Many people there including myself do not speak English as their first language.

[LucianoGit-x6zeta]

Hi Argiepiano, a separate module would be fine :) . I hope I understand what you mean by instances. If I understand correctly this tool does not export the instances of the field referring to a bundle or a content type. Instead, it exports field definitions such as label, machine name, field type (e.g. text, node reference, numeric, term reference, serial, etc.) and widget. The exported fields can be imported into a new content type created specifically or to integrate an existing content type. Import is also possible on a site that is completely disconnected from the original site. It is difficult for me to explain the utility well but I assure you that it is really very convenient and fast to create and integrate any content type. Thanks for the interest Argiepiano. Best regards

NB. i will explore Zulip soon ... for my english i have to thank google translate :)