Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter petegasper

    (@petegasper)

    I figured it out. This is not a bug but a misunderstanding of the functionality. The drop-down is for changing which GF is associated with that Stripe Feed Settings. So there are a group of ‘Stripe Forms’ which can be associated with different individual ‘Gravity Forms’.

    So clearing the settings is appropriate because you’re associating a new form and need to reset stuff.

    It felt like I was just setting up the settings for an individual Gravity Form and could change do different setting’s from within the edit page but its more disjoint than that. You have to go out to the main Stripe Forms page to edit a different one.

    Thread Starter petegasper

    (@petegasper)

    I looked and you are correct, the invoice specific settings still have the old key. I modified the invoice copy and payment succeeded.

    Keeping this many copies of the key floating around seems like trouble.

    Thread Starter petegasper

    (@petegasper)

    On a hunch I tried creating a new invoice and it worked. I had created a number of invoices and had been making changes (including fixing an actual whitespace error) to try and get the invoice payment to work.

    Any new invoice I create can be successfully paid. All old invoices cannot be paid and continue to show the key error. I tried to copy an existing invoice to see what would happen but that functionality doesn’t appear to be working (the form doesn’t pull up any old invoices). But thats a different bug for a different day.

    I am concerned about this error though. This behaves as if when you create an invoice the SW makes copies of the Stripe keys at that time to store/associate with the invoice. If so that not only causes unexpected behavior, but making unnecessary copies of sensitive information increases the chance of a security breach.

    What do you think? Is this known behavior or a potential bug?

    Let me know if you need anything to assist in debugging. This should be fairly easy to replicate: set up a new fresh install, enter a key with whitespace in it (in my case it was a leading whitespace in the private test key). Create some invoices and test. Fix the key white space issue. Test. Create new invoices. Test.

    I’m using the newest WP-Invoice and WP.

Viewing 3 replies - 1 through 3 (of 3 total)