As designed Payment Profile and xf_payment_profile Table

[sip]

Affected version

2.0.0 RC 3

If we create and delete payment profile, the table xf_payment_profile still contains all the entries that were added (even for testing). Wondering if this is a bug or by design.

 

[Liam W]

If we create and delete payment profile, the table xf_payment_profile still contains all the entries that were added (even for testing). Wondering if this is a bug or by design.

This is by design. Deleting a payment profile only marks it as inactive, presumably so any existing payments will still work.

If you check the payment profile entity, you’ll see that trying to delete it will throw an error.

It would be useful to be able to fully delete them in development mode though.

Liam

 

[Chris D]

Indeed, this is intentional.

It would be useful to be able to fully delete them in development mode though.

I think at that point most developers would just delete it from the database. We wouldn't want people to not realise that debug mode is enabled and then mistakenly delete an active payment profile.