Adding New Fields (ToolKit) and Making Them Required

[pixeljuice]

Using Toolkit and MIVAs custom customer fields, I've successfully added fields into the ACAD form. I now need to require that some of these new fields have a value entered. Here's an example asking for a user's Resale Number:

<label class="required" for="resale-number">Resale Number:</label>
<input type="text" name="resale-number" id="resale-number" value="&mvte:global:resale-number;" class="textfield" />

Using the ToolKit function "systemaction" I'm trying to require this field. I've added the following just below my code for the custom field:

<mvt:item name="toolkit" param="systemaction|resale-number|ACAD|A Resale Number is Required." />

I've also created a template called ACAD_SYSTEM, activated the Toolkit item and pasted the following into this new page template:

<mvt:if expr="resale-number EQ ''">
<mvt:item name="toolkit" param="mvassign|tkmessage|encodeentities(g.tkmessage)" />
<mvt:item name="toolkit" param="mvassign|tkscreen|encodeentities(g.tkscreen)" />
<mvt:item name="toolkit" param="vacreate|error_message|g.tkmessage|," />
<mvt:item name="toolkit" param="sassign|Error_Message_Count|1" />
<mvt:item name="toolkit" param="vassign|Error_Messages|l.all_settings:error_message" />
<mvt:item name="toolkit" param="vassign|Screen|g.tkscreen" />
</mvt:if>
<mvt:exit>

It's not working. All of the MIVA fields are outlining in red to show that they are required, but I don't see the error message

[PCINET - Andreas]

Re: Adding New Fields (ToolKit) and Making Them Required

Why don't you use ACAD's module settings to make it required?

[pixeljuice]

Re: Adding New Fields (ToolKit) and Making Them Required

Hi

Andreas,

That would be ideal. Is there a published article that would allow me to learn to do that?

Timothy

[PCINET - Andreas]

Re: Adding New Fields (ToolKit) and Making Them Required

Timothy, Sebenza's ACAD module comes with doc and has a link to the docs in the module settings. This should be what you are looking for.

[pixeljuice]

Re: Adding New Fields (ToolKit) and Making Them Required

Thanks for the info. I'll check it out, but wonder if I'll be able to make sections within this as I've done with ToolKit.

ChromeScreenShot.jpg

Timothy

[pixeljuice]

Re: Adding New Fields (ToolKit) and Making Them Required

Just checked and Sebenza doesn't seem to have an ACAD module. Were you thinking I could use the Additional Data Collection at Checkout module on the ACAD page?

[PCINET - Andreas]

Re: Adding New Fields (ToolKit) and Making Them Required

Oops, I was under the impression you are using Sebenza's additional checkout data module to collect additional checkout data. You are actually trying to collect customer data when they create an account.
Looking at your code, it looks like you missed a step in Bill's docs to get the error message.

[pixeljuice]

Re: Adding New Fields (ToolKit) and Making Them Required

Don't see that I missed anything, unless something is required to create the "action" Bill refers to as the 2nd parameter.

<mvt:item name="toolkit" param="systemaction|SHIP|OSEL|Please select a different shipping method" />

The 2nd parameter is the "action" to check. In this example we are going to check for a shipping method being selected. If the customer does not select a method, we are going to reload the page identified with the 3rd parameter. The 4th parameter is the message. No html allowed in the message.

[PCINET - Andreas]

Re: Adding New Fields (ToolKit) and Making Them Required

Try to contact Bill. he is usually around and helps on the forum if it is about toolkit or related items.

[nottheusual1]

Re: Adding New Fields (ToolKit) and Making Them Required

For some reason it sticks in my mind that the dash in your custom field code may be causing the problem. Replace it with an underscore and see if things work better.

[pixeljuice]

Re: Adding New Fields (ToolKit) and Making Them Required

For some reason it sticks in my mind that the dash in your custom field code may be causing the problem. Replace it with an underscore and see if things work better.

Given that I've already collected data using "resale-number" with the dash in my custom field code, do I run the risk of losing all of that customer data by changing the existing code to resale_number? Or, is this field actually assigned an ID in the database and I'll still be able to see all the Resale Number entries if I do make this change?

Timothy

[wcw]

Re: Adding New Fields (ToolKit) and Making Them Required

The data is actually kept in a record that tracks by ID number. So changing the code or name won't lose the data. However, if you have coded some page templates to look for resale-number, you'll need to go back and change the - to _.

[nottheusual1]

Re: Adding New Fields (ToolKit) and Making Them Required

Modifying the field code won't bother anything unless you've hard-coded it into a template somewhere. The reason it sticks in my mind is that, as a practice, we don't use dashes in naming anything Miva-specific and I remember having problems sometimes when we did.

Hope it makes the difference. Easy fixes are good.