PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

Export tool ads CREDIT CARDS for each entry - looks like a bug..

  1. obvio
    Member

    Hi,
    Exporting a form pushed the creditCards xml node to each field, don't it should be there and maybe slightly redundant.

    <field id="25" type="text" size="small" dateType="datepicker">
    	<label><![CDATA[Monday]]></label>
    	<adminLabel><![CDATA[Exec Special Monday]]></adminLabel>
    	<creditCards>
    		<creditCard><![CDATA[amex]]></creditCard>
    		<creditCard><![CDATA[visa]]></creditCard>
    		<creditCard><![CDATA[discover]]></creditCard>
    		<creditCard><![CDATA[mastercard]]></creditCard>
    	</creditCards>
    	<cssClass><![CDATA[gf_inline]]></cssClass>
    </field>

    Thanks!

    Posted 13 years ago on Wednesday November 2, 2011 | Permalink
  2. The creditCards node is not duplicated, just each individual creditCard (singular). Is that not correct?

    Posted 13 years ago on Thursday November 3, 2011 | Permalink
  3. obvio
    Member

    it repeats itself for each field node, so next field node also had a nested credit card node..
    even if it doesn't repeat itself, why credit card stuff apear on any regular most simple text field?
    Thanks.

    Posted 13 years ago on Thursday November 3, 2011 | Permalink
  4. Ah, got it. You did not post the repeated part. I was going off what you posted. I will bring it to the developers attention and see what the explanation is. Thanks obvio.

    Posted 13 years ago on Thursday November 3, 2011 | Permalink
  5. Thanks for the heads up @obvio. The creditCards node should only be added to the credit card field. I have made an adjustment to resolve this issue. Email me to alex@rocketgenius.com if you are interested in helping us test it.
    If you are curious about the credit card field, it will be activated by the Authorize.net Add-On that we will release as Beta in the near future.

    Posted 13 years ago on Thursday November 3, 2011 | Permalink

This topic has been resolved and has been closed to new replies.