I love this plugin, but wish there was a 'proposed way with best practices' to get the custom plugin showing up.
Is it best to copy the example custom plugin (good start)
Should I disable the original plugin?
How can I overwrite fields that are already in the base model (e.g. what if I don't want the subject line to show up?)
I know 'everyone' does it differently, but I would really love a plugin that is easy to install and covers many use cases. Maybe it's even better to include a few different use case that are ready to plugin pluggable. I know it's hard for model-based apps, but how many different contact-form variations are out there? Usually I need no more than 3 fields displayed to the end user, mine just happens to be:
name
e-mail
message
And the default here is:
e-mail
subject
message
I'm thinking: keep 4 fields (or more) and use and admin template choice to display only some.
I'm happy to help out where I can. Just wanted to start a discussion.
I love this plugin, but wish there was a 'proposed way with best practices' to get the custom plugin showing up.
I know 'everyone' does it differently, but I would really love a plugin that is easy to install and covers many use cases. Maybe it's even better to include a few different use case that are ready to plugin pluggable. I know it's hard for model-based apps, but how many different contact-form variations are out there? Usually I need no more than 3 fields displayed to the end user, mine just happens to be:
And the default here is:
I'm thinking: keep 4 fields (or more) and use and admin template choice to display only some.
I'm happy to help out where I can. Just wanted to start a discussion.