CBSubs Plan Invoice: Pre-Populating Information

When my user is prompted to pay for their plan, parts of the invoice are pre-populated and some are not which makes me think that I have my fields set up incorrectly.

Specifically:
First Name
Last Name
State/Province (I currently have it as a text field but I think it should be a drop down)

There's a bug with Name mapping. It only maps the last name if it maps at all. It'll work fine if you use single name field, but if you use first and last name usage like most then only last name maps properly.

State/Province will only map if the value stored in CB matches the exact value that CBSubs expected. In most causes this is the 2 or 3 character country or state code for example. Being a text field users are likely supplying the full country text so it won't map.

Is there a way for my field to match what CBSubs is expecting? Like, am I presenting the field incorrectly? Or is a text field okay and then the person will just have to fill in the missing information for the invoice?

You'd need to use a select fieldtype that has the same values that CBSubs provides. Best way to do this is a CB Query Field and its Query Select fieldtype then use a database query to grab CBSubs exact values from its _comprofiler_provinces and _comprofiler_countries tables. See the below for an example of this usage.

www.joomlapolis.com/support/tutorials/107-use-cases/18377-configuring-a-country-field-with-cb-query-field-plugin

Note you don't need the SQL file in the above tutorial as you'd just be using CBSubs already existing tables. So for example you'd have a query select field with the below.

Query: Value Column: code
Label Column: province
Group Column: country

krileon wrote: There's a bug with Name mapping. It only maps the last name if it maps at all. It'll work fine if you use single name field, but if you use first and last name usage like most then only last name maps properly.

Hi, Just wondered if there was a plan for when a fix for the name mapping would be available? I have looked but couldn't find anything.

Yes, a fix is still planned. No, I don't know when. The ticket is currently scheduled for next bug fix release.