I am creating this feature request to introduce a new feature in this module. The feature is about providing a universal backend form, let us assume in settings, where one can select the content bundles to be excluded or included in link fields all across the site at once that will help users that want to exclude some bundles from being referenced in link fields across all sites.

The default functionality will work as it is. we can combine current functioanlity with the universal config that can work in a way say if the user wants a content type A where he/she wants the link field to include all bundles and on rest of the content types he/she wants some bundles to be restricted.

I am willing to contribute this to this functionality and wants to be co-maintainer also.
Thanks

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

Comments

whitedevil created an issue. See original summary.

jmuxf’s picture

I can see why this might be useful, if you have a huge amount of link-field instances, and in order not to have to navigate to each field configuration form to make adjustments. I think it would be best to simply make a system config form page, where you list all the link-field uses with the same radio buttons as in the field config form. You only need to read the system configs for each field instance and make a GUI to adjust them.

Since your feature is very independent of the code of Link Field Autocomplete Filter, I suggest implementing this as an additional module. Since all you need to do is read/write system configurations, this can happily reside in a separate module with a dependency on Link Field Autocomplete Filter. Once it is stable and running, I will be happy to include a link to your module on my module page.

whitedevil’s picture

Thanks for the reply but the feature you suggested is a little bit different from the one I am requesting.
My feature is about to create a single config form with all content-bundles and whatever the settings saved on the form will work on all link field instances at once. I think this is quite dependent on your module's code. So can you please have a thought on it again.

The one you suggested above is also useful, will look on how i can achieve that.

jmuxf’s picture

I don't think I want to include that in the present model, just in order to keep things simple. Some users had mentioned they would like configurations via views. This seems to be more sensible to me.
However, if you want to write your own module, and need a hook to override something in mine, I can add the hook.

whitedevil’s picture

Ok Thanks.
Will create a separate module for this.

jmuxf’s picture

Status: Active » Closed (outdated)