Hi Made4U0, thanks so much for continuing to help.
Yes sure, I can copy and paste the code, I just wanted to send you an image so you can see the formatting well.
This is the original Newsletter code
{% comment %}
{% render 'newsletter-form', unique: unique, text: block.settings.button_text, style: block.settings.button_style, color: block.settings.button_color %}
{% endcomment %}
{%- liquid
assign style = style | default: 'btn'
assign color = color | default: 'btn--secondary'
assign translation = 'general.newsletter_form.submit' | t
assign text = text | default: translation
assign class = 'newsletter--default-messages'
if success_text != blank
assign class = ''
endif
-%}
{%- if unique -%}
{% form 'customer', id: unique, data-newsletter-form: '', class: class %}
{% if content != blank %}
{{ content }}
{% endif %}
{% if success_text != blank %}
{{ success_text | newline_to_br }}
*{{ 'general.newsletter_form.error_message' | t }}*
{% else %}
{% if form.posted_successfully? %}
*{{ 'general.newsletter_form.subscribed' | t }}*
{% elsif form.errors %}
{% for field in form.errors %}
*{{ field }} - {{ form.errors.messages[field] }}*
{% endfor %}
{% endif %}
{% endif %}
{% endform %}
{%- endif -%}
Right now, the functionality is that when a customer enter his email and clicks submit, a new customer is created here.
The phone number doesn’t do anything because I created that as a copy, and it doesnt work right now.
One change between the original newsletter code, and my code is that I removed the fact that it’s
a
{% form customer %}{% endform %}
Because when that was active, it acted like you describe, where clicking the submit button would try to use the phone number field as an email, and it would error out on both boxes.
My ideal final solution is to link it to Attentive API
https://docs.attentivemobile.com/openapi/reference/tag/Subscribers/
Where I take the customer email and phone number, and create a new Subscriber through the Attentive API, using our unique signUpSourceId.
If you can tell me how to make the Join button work for the phone number field individually, I think I would be able to figure out the API portion myself. I think if a customer only puts in a phone number, or only puts in a email, I would still want to make the API call. So idk if the best solution for that is to have individual buttons, or somehow link everything to one button and remove the required field.
Once again, thanks a lot, and this is extremely helpful.
