Upgrade Modification Forms

I have provided my customers with a way of upgrading their membership using the Pro Billing Modification Form and noticed that the form asks (mandatory fields) for Card Start Date or Issue Number under the billing section of the form.

I don’t think anyone knows that information. Are these supposed to be here? If so is there a work around to edit those fields?

Thank you

Those fields are only for a couple of the cards (e.g. Solo), and should not be showing for just any card. You may be having something conflicting with the pro-form’s JavaScript, causing it to behave incorrectly like that.

Could you try these, please? Knowledge Base » Common Troubleshooting Tips

How should I start debugging this? Suggestions?

Do the tests given in the troubleshooting article I linked to earlier, please.

Could you try these, please? Knowledge Base » Common Troubleshooting Tips

Ok, I’ll try that over the weekend and get back to you.

Thanks

Cool, thanks. :)

Went through the trouble shooting tips. The problem appears to be in the design of the page itself. I recreated a portion of the page and it worked fine. I should be able to close the ticket later today.

Thanks

I’m posting this information in case someone else runs into this issue. I created a Customer Center for a simple means for my customers to perform all modifications to their accounts.

The problem, as described in this thread came from trying to place two modification of subscription forms on the same page for any one subscriber.

Since I am not an expert on code, I did use short coding that worked beautifully in displaying the correct content to each subscriber. However, I am probably lacking in advanced html to make two forms display to the same subscriber on a given page.

If anyone knows how to do this please let me know.

Otherwise, simple linking for us dummies works fine.

Ah, thanks for the update. I’m glad you sorted it out. :)

Two pro-forms can’t be used in the same page yet, they’ll conflict. I’ll ask Jason if this can be mentioned in the documentation to avoid a future confusion about it.

Thank you.