Skip to content
This repository has been archived by the owner on Feb 24, 2022. It is now read-only.

Figure out why deployed site with Smarty Streets disabled is not actually disabled #153

Closed
hartsick opened this issue Jan 14, 2022 · 1 comment
Assignees

Comments

@hartsick
Copy link
Contributor

hartsick commented Jan 14, 2022

See #67

porta just ran a quick validation on the app that has smartystreets disabled:

email address presents as optional (no *)
email address is optional (was able to submit the request and got to confirmation page)
was unable to check to see if on the persisted info, there's a way to discern whether an entry was one run with smarty sheets disabled or enabled. (presume we could detect that via absence of the JSON response).

working hypothesis:

I'm looking at that server and it's not what I expect it to look like if smarty was actually disabled—I suspect the env var isn't set correctly in the environment? will look into in the morning

@rahearn
Copy link
Collaborator

rahearn commented Jan 15, 2022

Closing, as I think this was resolved by #166

@rahearn rahearn closed this as completed Jan 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants