Skip to content
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

[Import] Consolidate DataSource.tpl for Custom import #23458

Closed

Conversation

eileenmcnaughton
Copy link
Contributor

Overview

Consolidate DataSource.tpl for Custom import

Before

image

After

image

Technical Details

  1. this change Does move the field set chooser below contact type - which is marginally less good - but I think it might make more sense when I figure out how to bring in the contact import into the same tpl.

  2. the original displayed an error message if you tried to access the form, absent having any multple record fields. I switched to a statusBounce - but @colemanw I wonder if we could somehow just exclude from the navigation menu?

Comments

@civibot
Copy link

civibot bot commented May 13, 2022

(Standard links)

@civibot civibot bot added the master label May 13, 2022
@eileenmcnaughton eileenmcnaughton changed the title Consolidate DataSource.tpl for Custom import [Import] Consolidate DataSource.tpl for Custom import May 25, 2022
@eileenmcnaughton
Copy link
Contributor Author

@colemanw I'm thinking maybe the statusBounce is enough here - but would be good to get this merged - I'm expecting to have to resolve a conflict with #23456 (whichever is merged first)

@eileenmcnaughton eileenmcnaughton force-pushed the import_more_cust branch 2 times, most recently from 83af9ab to 088dc2c Compare May 26, 2022 14:44
@eileenmcnaughton
Copy link
Contributor Author

@colemanw I'm trying to figure out a sane way to make this form unavailable when there are no multiple custom data sets on the site.

It used to be a message in the middle of the template & then it would fail form validation on submit

I thought a statusBounce would be better - but then it would up in a loop. So here I've tried an access_callback - which works (in that the page doesn't loop but you can't use it due to permission denied) but it doesn't remove it from the navigation menu as I'd hoped it would when disabled. Any ideas? This is the last of the DataSource.tpl files other than the merge with the contact one so getting this merged gets me close to being able to use the same method for all

@eileenmcnaughton
Copy link
Contributor Author

test this please

@eileenmcnaughton
Copy link
Contributor Author

Closing this as will re-visit the import - not much movement on this one...

@eileenmcnaughton eileenmcnaughton deleted the import_more_cust branch June 4, 2022 22:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant