“Prefix is a required field” on logged in checkout Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?Redirect in OnePage Checkout during checkout in “Shipping Method” to shipping provider's web (onepage)Billing address not being saved to quotecheckout broken after removing required fieldsHow to change the required field of Zip/Postal Code with “not required”?How to make address fields not required in checkout?Get shipping address in onepage checkout sessionIs there a way to edit the pre stored address in the Onepage checkout page?Checkout progress not changing status when skippedCheckout remains 80% blank Magento 2.0.7Magento checkout - Address option
An adverb for when you're not exaggerating
Generate an RGB colour grid
Denied boarding although I have proper visa and documentation. To whom should I make a complaint?
What do you call the main part of a joke?
What is the meaning of the new sigil in Game of Thrones Season 8 intro?
What would be the ideal power source for a cybernetic eye?
Is it a good idea to use CNN to classify 1D signal?
Can an alien society believe that their star system is the universe?
What does the "x" in "x86" represent?
How can I use the Python library networkx from Mathematica?
How to deal with a team lead who never gives me credit?
Is it fair for a professor to grade us on the possession of past papers?
Dating a Former Employee
How to tell that you are a giant?
Is there a kind of relay only consumes power when switching?
Can a new player join a group only when a new campaign starts?
If u is orthogonal to both v and w, and u not equal to 0, argue that u is not in the span of v and w. (
First console to have temporary backward compatibility
Withdrew £2800, but only £2000 shows as withdrawn on online banking; what are my obligations?
How do I find out the mythology and history of my Fortress?
2001: A Space Odyssey's use of the song "Daisy Bell" (Bicycle Built for Two); life imitates art or vice-versa?
Is grep documentation wrong?
Trademark violation for app?
Do square wave exist?
“Prefix is a required field” on logged in checkout
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)
Announcing the arrival of Valued Associate #679: Cesar Manara
Unicorn Meta Zoo #1: Why another podcast?Redirect in OnePage Checkout during checkout in “Shipping Method” to shipping provider's web (onepage)Billing address not being saved to quotecheckout broken after removing required fieldsHow to change the required field of Zip/Postal Code with “not required”?How to make address fields not required in checkout?Get shipping address in onepage checkout sessionIs there a way to edit the pre stored address in the Onepage checkout page?Checkout progress not changing status when skippedCheckout remains 80% blank Magento 2.0.7Magento checkout - Address option
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I have a magento with a default onepage checkout.
When a fresh registered, active customer tries to checkout I get the message "Prefix is a required field" no matter if the customer has already given his prefix or not.
As the prefix is mandatory for the project, setting it to "not required" is not an option.
How do I get magento to use the already given prefix and not throw this error?
See screenshot for the full situation. This happens no matter if the customer already has an address or not.
onepage-checkout prefix
edited Mar 20 '17 at 15:09
Nicolas D
1617
asked Dec 15 '15 at 9:30
Bernhard PrangeBernhard Prange
487318
add a comment |
I have a magento with a default onepage checkout.
When a fresh registered, active customer tries to checkout I get the message "Prefix is a required field" no matter if the customer has already given his prefix or not.
As the prefix is mandatory for the project, setting it to "not required" is not an option.
How do I get magento to use the already given prefix and not throw this error?
See screenshot for the full situation. This happens no matter if the customer already has an address or not.
onepage-checkout prefix
edited Mar 20 '17 at 15:09
Nicolas D
1617
asked Dec 15 '15 at 9:30
Bernhard PrangeBernhard Prange
487318
add a comment |
I have a magento with a default onepage checkout.
When a fresh registered, active customer tries to checkout I get the message "Prefix is a required field" no matter if the customer has already given his prefix or not.
As the prefix is mandatory for the project, setting it to "not required" is not an option.
How do I get magento to use the already given prefix and not throw this error?
See screenshot for the full situation. This happens no matter if the customer already has an address or not.
onepage-checkout prefix
edited Mar 20 '17 at 15:09
Nicolas D
1617
asked Dec 15 '15 at 9:30
Bernhard PrangeBernhard Prange
487318
I have a magento with a default onepage checkout.
When a fresh registered, active customer tries to checkout I get the message "Prefix is a required field" no matter if the customer has already given his prefix or not.
As the prefix is mandatory for the project, setting it to "not required" is not an option.
How do I get magento to use the already given prefix and not throw this error?
See screenshot for the full situation. This happens no matter if the customer already has an address or not.
onepage-checkout prefix
onepage-checkout prefix
edited Mar 20 '17 at 15:09
Nicolas D
1617
asked Dec 15 '15 at 9:30
Bernhard PrangeBernhard Prange
487318
edited Mar 20 '17 at 15:09
Nicolas D
1617
asked Dec 15 '15 at 9:30
Bernhard PrangeBernhard Prange
487318
edited Mar 20 '17 at 15:09
Nicolas D
1617
edited Mar 20 '17 at 15:09
Nicolas D
1617
edited Mar 20 '17 at 15:09
Nicolas D
1617
1617
asked Dec 15 '15 at 9:30
Bernhard PrangeBernhard Prange
487318
asked Dec 15 '15 at 9:30
Bernhard PrangeBernhard Prange
487318
asked Dec 15 '15 at 9:30
Bernhard PrangeBernhard Prange
487318
487318
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
I realize this is almost a year old, but I came across this looking for an answer myself; best I can offer at the moment is that the problem arose on the site I'm developing when I imported the customer and sales tables from an older site. The new site was an upgrade to a newer version of Magento (1.7 (IIRC) --> 1.9.2.4) and it appears that the columns in the database don't line up correctly. As a result, the validation fails when there is an attempt to insert the values into the database, even if the frontend validation may succeed.
answered Nov 27 '16 at 20:46
spencerreadyspencerready
285
I just turned the "required" off and made a onsite js validation. As this was a new 1.9.2.4 setup it can't be upgrade problems.
– Bernhard Prange
Nov 30 '16 at 20:09
Fair enough. In my case, I ultimately removed a duplicate field that had appeared in eav_attribute (might have been put there intentionally by the original developer of the site, can't be sure). After the field was removed, the attribute ids lined up as expected. In addition, I had to update a few rows in customer_eav_attribute because apparently the upgrade script failed to set is_visible according to the configuration, which wasn't being updated regardless of configuration in the admin panel.
– spencerready
Dec 4 '16 at 15:56
add a comment |
I had same issue which i fixed in a stupid way on my side :
update customer_eav_attribute_website cea left join eav_attribute ea on ea.attribute_id = cea.attribute_id
set cea.is_required = 0
WHERE attribute_code = 'prefix'
My prefix field was well in is_required = 0 on eav table, but overriden on website table.
The more surprising thing was for me the validator error : "Customer email is required" on OneStepCheckout.
All that for a prefix..
answered Mar 20 '17 at 15:48
Nicolas DNicolas D
1617
add a comment |
If anyone else stumbles upon this:
The problem is caused by a missing value for the prefix field on customer entity level, not customer address entity.
When activating and requiring the "prefix" field in a shop where there are already existing customers those won't have any value stored for the prefixattribute for either customer entity nor customer address entity.
During checkout the customer can choose to create a new address and enter a value for the now required prefix attribute there but the value will still be missing for the customer entity leading to the error described above.
The only way to fix this is to either set the prefix attribute to not be required in the admin interface or assign a value to the prefix attribute for each customer (for example via a simple php script).
answered Jan 18 '18 at 8:58
RindaRinda
812
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "479"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f93852%2fprefix-is-a-required-field-on-logged-in-checkout%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
I realize this is almost a year old, but I came across this looking for an answer myself; best I can offer at the moment is that the problem arose on the site I'm developing when I imported the customer and sales tables from an older site. The new site was an upgrade to a newer version of Magento (1.7 (IIRC) --> 1.9.2.4) and it appears that the columns in the database don't line up correctly. As a result, the validation fails when there is an attempt to insert the values into the database, even if the frontend validation may succeed.
answered Nov 27 '16 at 20:46
spencerreadyspencerready
285
I just turned the "required" off and made a onsite js validation. As this was a new 1.9.2.4 setup it can't be upgrade problems.
– Bernhard Prange
Nov 30 '16 at 20:09
Fair enough. In my case, I ultimately removed a duplicate field that had appeared in eav_attribute (might have been put there intentionally by the original developer of the site, can't be sure). After the field was removed, the attribute ids lined up as expected. In addition, I had to update a few rows in customer_eav_attribute because apparently the upgrade script failed to set is_visible according to the configuration, which wasn't being updated regardless of configuration in the admin panel.
– spencerready
Dec 4 '16 at 15:56
add a comment |
I realize this is almost a year old, but I came across this looking for an answer myself; best I can offer at the moment is that the problem arose on the site I'm developing when I imported the customer and sales tables from an older site. The new site was an upgrade to a newer version of Magento (1.7 (IIRC) --> 1.9.2.4) and it appears that the columns in the database don't line up correctly. As a result, the validation fails when there is an attempt to insert the values into the database, even if the frontend validation may succeed.
answered Nov 27 '16 at 20:46
spencerreadyspencerready
285
I just turned the "required" off and made a onsite js validation. As this was a new 1.9.2.4 setup it can't be upgrade problems.
– Bernhard Prange
Nov 30 '16 at 20:09
Fair enough. In my case, I ultimately removed a duplicate field that had appeared in eav_attribute (might have been put there intentionally by the original developer of the site, can't be sure). After the field was removed, the attribute ids lined up as expected. In addition, I had to update a few rows in customer_eav_attribute because apparently the upgrade script failed to set is_visible according to the configuration, which wasn't being updated regardless of configuration in the admin panel.
– spencerready
Dec 4 '16 at 15:56
add a comment |
I realize this is almost a year old, but I came across this looking for an answer myself; best I can offer at the moment is that the problem arose on the site I'm developing when I imported the customer and sales tables from an older site. The new site was an upgrade to a newer version of Magento (1.7 (IIRC) --> 1.9.2.4) and it appears that the columns in the database don't line up correctly. As a result, the validation fails when there is an attempt to insert the values into the database, even if the frontend validation may succeed.
answered Nov 27 '16 at 20:46
spencerreadyspencerready
285
I realize this is almost a year old, but I came across this looking for an answer myself; best I can offer at the moment is that the problem arose on the site I'm developing when I imported the customer and sales tables from an older site. The new site was an upgrade to a newer version of Magento (1.7 (IIRC) --> 1.9.2.4) and it appears that the columns in the database don't line up correctly. As a result, the validation fails when there is an attempt to insert the values into the database, even if the frontend validation may succeed.
answered Nov 27 '16 at 20:46
spencerreadyspencerready
285
answered Nov 27 '16 at 20:46
spencerreadyspencerready
285
answered Nov 27 '16 at 20:46
spencerreadyspencerready
285
answered Nov 27 '16 at 20:46
spencerreadyspencerready
285
285
I just turned the "required" off and made a onsite js validation. As this was a new 1.9.2.4 setup it can't be upgrade problems.
– Bernhard Prange
Nov 30 '16 at 20:09
Fair enough. In my case, I ultimately removed a duplicate field that had appeared in eav_attribute (might have been put there intentionally by the original developer of the site, can't be sure). After the field was removed, the attribute ids lined up as expected. In addition, I had to update a few rows in customer_eav_attribute because apparently the upgrade script failed to set is_visible according to the configuration, which wasn't being updated regardless of configuration in the admin panel.
– spencerready
Dec 4 '16 at 15:56
add a comment |
I just turned the "required" off and made a onsite js validation. As this was a new 1.9.2.4 setup it can't be upgrade problems.
– Bernhard Prange
Nov 30 '16 at 20:09
Fair enough. In my case, I ultimately removed a duplicate field that had appeared in eav_attribute (might have been put there intentionally by the original developer of the site, can't be sure). After the field was removed, the attribute ids lined up as expected. In addition, I had to update a few rows in customer_eav_attribute because apparently the upgrade script failed to set is_visible according to the configuration, which wasn't being updated regardless of configuration in the admin panel.
– spencerready
Dec 4 '16 at 15:56
I just turned the "required" off and made a onsite js validation. As this was a new 1.9.2.4 setup it can't be upgrade problems.
– Bernhard Prange
Nov 30 '16 at 20:09
I just turned the "required" off and made a onsite js validation. As this was a new 1.9.2.4 setup it can't be upgrade problems.
– Bernhard Prange
Nov 30 '16 at 20:09
Fair enough. In my case, I ultimately removed a duplicate field that had appeared in eav_attribute (might have been put there intentionally by the original developer of the site, can't be sure). After the field was removed, the attribute ids lined up as expected. In addition, I had to update a few rows in customer_eav_attribute because apparently the upgrade script failed to set is_visible according to the configuration, which wasn't being updated regardless of configuration in the admin panel.
– spencerready
Dec 4 '16 at 15:56
Fair enough. In my case, I ultimately removed a duplicate field that had appeared in eav_attribute (might have been put there intentionally by the original developer of the site, can't be sure). After the field was removed, the attribute ids lined up as expected. In addition, I had to update a few rows in customer_eav_attribute because apparently the upgrade script failed to set is_visible according to the configuration, which wasn't being updated regardless of configuration in the admin panel.
– spencerready
Dec 4 '16 at 15:56
add a comment |
I had same issue which i fixed in a stupid way on my side :
update customer_eav_attribute_website cea left join eav_attribute ea on ea.attribute_id = cea.attribute_id
set cea.is_required = 0
WHERE attribute_code = 'prefix'
My prefix field was well in is_required = 0 on eav table, but overriden on website table.
The more surprising thing was for me the validator error : "Customer email is required" on OneStepCheckout.
All that for a prefix..
answered Mar 20 '17 at 15:48
Nicolas DNicolas D
1617
add a comment |
I had same issue which i fixed in a stupid way on my side :
update customer_eav_attribute_website cea left join eav_attribute ea on ea.attribute_id = cea.attribute_id
set cea.is_required = 0
WHERE attribute_code = 'prefix'
My prefix field was well in is_required = 0 on eav table, but overriden on website table.
The more surprising thing was for me the validator error : "Customer email is required" on OneStepCheckout.
All that for a prefix..
answered Mar 20 '17 at 15:48
Nicolas DNicolas D
1617
add a comment |
I had same issue which i fixed in a stupid way on my side :
update customer_eav_attribute_website cea left join eav_attribute ea on ea.attribute_id = cea.attribute_id
set cea.is_required = 0
WHERE attribute_code = 'prefix'
My prefix field was well in is_required = 0 on eav table, but overriden on website table.
The more surprising thing was for me the validator error : "Customer email is required" on OneStepCheckout.
All that for a prefix..
answered Mar 20 '17 at 15:48
Nicolas DNicolas D
1617
I had same issue which i fixed in a stupid way on my side :
update customer_eav_attribute_website cea left join eav_attribute ea on ea.attribute_id = cea.attribute_id
set cea.is_required = 0
WHERE attribute_code = 'prefix'
My prefix field was well in is_required = 0 on eav table, but overriden on website table.
The more surprising thing was for me the validator error : "Customer email is required" on OneStepCheckout.
All that for a prefix..
answered Mar 20 '17 at 15:48
Nicolas DNicolas D
1617
answered Mar 20 '17 at 15:48
Nicolas DNicolas D
1617
answered Mar 20 '17 at 15:48
Nicolas DNicolas D
1617
answered Mar 20 '17 at 15:48
Nicolas DNicolas D
1617
1617
add a comment |
add a comment |
If anyone else stumbles upon this:
The problem is caused by a missing value for the prefix field on customer entity level, not customer address entity.
When activating and requiring the "prefix" field in a shop where there are already existing customers those won't have any value stored for the prefixattribute for either customer entity nor customer address entity.
During checkout the customer can choose to create a new address and enter a value for the now required prefix attribute there but the value will still be missing for the customer entity leading to the error described above.
The only way to fix this is to either set the prefix attribute to not be required in the admin interface or assign a value to the prefix attribute for each customer (for example via a simple php script).
answered Jan 18 '18 at 8:58
RindaRinda
812
add a comment |
If anyone else stumbles upon this:
The problem is caused by a missing value for the prefix field on customer entity level, not customer address entity.
When activating and requiring the "prefix" field in a shop where there are already existing customers those won't have any value stored for the prefixattribute for either customer entity nor customer address entity.
During checkout the customer can choose to create a new address and enter a value for the now required prefix attribute there but the value will still be missing for the customer entity leading to the error described above.
The only way to fix this is to either set the prefix attribute to not be required in the admin interface or assign a value to the prefix attribute for each customer (for example via a simple php script).
answered Jan 18 '18 at 8:58
RindaRinda
812
add a comment |
If anyone else stumbles upon this:
The problem is caused by a missing value for the prefix field on customer entity level, not customer address entity.
When activating and requiring the "prefix" field in a shop where there are already existing customers those won't have any value stored for the prefixattribute for either customer entity nor customer address entity.
During checkout the customer can choose to create a new address and enter a value for the now required prefix attribute there but the value will still be missing for the customer entity leading to the error described above.
The only way to fix this is to either set the prefix attribute to not be required in the admin interface or assign a value to the prefix attribute for each customer (for example via a simple php script).
answered Jan 18 '18 at 8:58
RindaRinda
812
If anyone else stumbles upon this:
The problem is caused by a missing value for the prefix field on customer entity level, not customer address entity.
When activating and requiring the "prefix" field in a shop where there are already existing customers those won't have any value stored for the prefixattribute for either customer entity nor customer address entity.
During checkout the customer can choose to create a new address and enter a value for the now required prefix attribute there but the value will still be missing for the customer entity leading to the error described above.
The only way to fix this is to either set the prefix attribute to not be required in the admin interface or assign a value to the prefix attribute for each customer (for example via a simple php script).
answered Jan 18 '18 at 8:58
RindaRinda
812
answered Jan 18 '18 at 8:58
RindaRinda
812
answered Jan 18 '18 at 8:58
RindaRinda
812
answered Jan 18 '18 at 8:58
RindaRinda
812
812
add a comment |
add a comment |
Thanks for contributing an answer to Magento Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f93852%2fprefix-is-a-required-field-on-logged-in-checkout%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
