[FIXED] Vm 1.1 b1 required fields

[DMA]

Virtuemart 1.1 b1

Frontend:
Account Maintenance/Shipping Information /Add Address

Field Phone_1 is required no matter what I do.
I tried to remove it from Manage userfields in vm backend but it did not work.

Can anybody tell me in which file I can set/change required fields?

/DMA

[aravot]

Using VM 1.1 r928

Admin -> Manage User Fields -> phone_1 unpublish required filed.
Tried during registration works as expected.

However it doesn't work in Frontend -> Account Maintenance / Shipping Information / Add Address

DMA, thanks for reporting

[DMA]

No problem 
Can anybody tell me which file to edit to get phone_1 optional?

/DMA

[aravot]

Q&T note; tracker URL -> http://dev.virtuemart.net/cb/proj/tracker/itemDetails.do?task_id=1425

[macallf]

Shipping fields in the frontend relate to the template

..pages/account.shipto.tpl.php

But this does not relate to manage userfields section.

Would need to edit ps_userfield and account.shipto.php so that the getuserfields list is used to generate the shipto info. Then if a field is set as required or published it would follow the correct behaviour.

Will have to look into further.

[DMA]

I'm sorry but which part of account.shipto.tpl.php do I need to edit to make the fields required or not in the current version?

/DMA

[macallf]

I thought my previous reply answered that!

account.shipto.tpl.php displays the form for adding new shipto addresses. It does not at present relate to the managed userfields.

Hence the quote of

Will have to look into further.

As this is still a beta  release I will have to look into this problem and rectify it so that it works correctly.

[DMA]

Maybe I'm saying this correctly since english is not my mother tongue. 
I don't want to offend anybody.

What I was meaning to say: I know now that the account.shipto.tpl.php form is not related to managed userfields.
So my question is, can someone please tell me what makes the field phone_1 in account.shipto.tpl.php form required and where can I change it?

/DMA

[macallf]

What I am saying is that there is a fundamental flaw in the way this achieved and that there is no easy answer as to one file that needs changing.

As I see it there could be 3 or more files that need editing to make this work correctly.

Hence I am not giving you a simple answer as there is not one.

Changes need to be made into way this whole operation works, once this has been done it will be incorporated into the nightly build.

As VM1.1 should not be used as a production site this is something not to worry about. It will be corrected before the final release.

If you are using this for a live site then you will have major problems when upgrading.

1. There will be no upgrade path from previous Beta versions, which could include major DB changes.
2. This could result in the complete reload of all relevant data for your site.

As I have said I am looking into it.

[DMA]

Thanks Macallf, I just thought all required fields in in the account.shipto.tpl.php form

Address Nickname*:
First Name*:
Last Name*:
Address 1*:
City*:
Zip/Postal Code*:
Country*:
Phone*:

were set to required in one place.

/DMA

[macallf]

Shipping fields in the frontend relate to the template

..pages/account.shipto.tpl.php

But this does not relate to manage userfields section.

Would need to edit ps_userfield and account.shipto.php so that the getuserfields list is used to generate the shipto info. Then if a field is set as required or published it would follow the correct behaviour.

Will have to look into further.

That is what I stated here. The required/published fields are not working or designed to work with the additional shipto addresses. Hence some major reworking needs to be done so that it does.

[aravot]

Implemented in build 1228

[wakoko]

i think this cannot be done to in 1.0.13 ecommerce edition

[wakoko]

my bad! it could be done in ps_user_address.php