- Issue created by @speckles
- πΊπΈUnited States jdleonard Austin, TX, USA
I feel like the status message could get overwhelming if it includes links for each Contact Type.
What if we added two buttons to the Contact add form?
- "Save and add another [Type]" -> /crm/contact/add/[type]
- "Save and add another Contact" -> /crm/contact/add
- Merge request !98Draft: Add "Save and Add Another [Type]" and "Save and Add Another Contact" buttons.... β (Open) created by Unnamed author
- πΊπΈUnited States jdleonard Austin, TX, USA
Created a draft MR to add those buttons. Both buttons were working for me, but now only one of them is and I can't figure out why. Could use some fresh eyes!
- πΊπΈUnited States bluegeek9
Maybe this should be the same as add Taxonomy term form:
'Save' and 'Save and goto list'. - πΊπΈUnited States bluegeek9
bluegeek9 β changed the visibility of the branch 1.0.x to hidden.
- πΊπΈUnited States jdleonard Austin, TX, USA
I like the idea of following an existing pattern. However, a key difference here with adding a taxonomy term is that from the list of taxonomy terms, there is one button to get back to the term add form whereas for contacts, the button takes you to `/crm/contact/add`, which then requires you to make another selection (a bundle).
I agree with @speckles that creating contact after contact will be a common pattern and is worth optimizing for. The two additional buttons optimize for the sub-scenarios of 1) creating another Contact of the same type; and 2) creating another Contact of a different type.
Sub-scenario 2 could perhaps be eliminated if the contact add form were to provide a way to create an associated contact e.g. while creating a Person, create an Organization with a corresponding Relationship (I would think that creating a related Contact would be the most common cause of sub-scenario 2), but there's much more complexity there so I'd propose deferring consideration of that.
Changing IS and title to reflect my proposed solution (but seeking input from @speckles too).
- πΊπΈUnited States jdleonard Austin, TX, USA
This is now working. Maddeningly time consuming to figure out what the problem was. Placeholder variable needed to start with @ rather than % so as to not introduce HTML into the button label, which was silently causing a no-op.