-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
Configure your link types in settings #52
Comments
I understand the workflow frustration when using in Matrix fields (or just lots of Hyper fields in general), but not quite sure how global settings would work at the moment, without annoying people who do want tailored fields. But probably adding a drop-down in the field settings to pick from the Plugin settings would work. Which would also allow you to create multiple “default settings” for fields, which could work nicely. |
Yep, would love that approach! |
@engram-design just wondering if you have a rough timeline on this feature. I'm putting of CMS set up to avoid a lot of duplicate work & possibly a lot of mistakes in matrix fields. |
I can't provide an ETA, but it would be a reasonably-sized new feature and is probably a few months away. |
Clear, thanks for the quick response! |
With Craft 5 lurking around, it would be nice to revisit this topic. I see two possible routes for this problem (and maybe configured in one project dozens links fields 😵):
|
@gglnx still digesting these new features from the Craft 5 alpha (and waiting for the APIs to settle), but that’s certainly an option. |
What are you trying to do?
When using Hyper within a page builder setup you have to do a lot of setup over and over again, since often time you want to reuse the hyper config (link types & linked fields) over and over again for multiple block types.
What's your proposed solution?
Would be nice if you could configure those link types on a plugin settings level, just like entry types, that you can drag & drop or enable & disable, but don't have to manually reconfigure for every instance of a Hyper field.
Additional context
No response
The text was updated successfully, but these errors were encountered: