Ask, reply and learn. Join the community of Akaunting.
So I have a blade file that injects a custom field into the customer profile. In my on-premise version, it saves the field. But on what I submitted to the cloud version, it doesn't. I run an API call to FluidPay when you save the customer record to take the custom field I have called fluid_pay_customer_id and its supposed to write to a custom DB table. But it's not doing that. Whats interesting is on the portal when the customer pays, it calls the API to write the card info and returns a vault ID. Then saves the vault ID and customer ID to my custom table and on the customer profile, it displays the results, but when manually entering the customer ID into the customer profile, and hitting save, it doesnt appear to be running the custom commands. I have a /Listeners/Common/SaveFluidPayCustomerId.php.
use Illuminate\Support\Facades\Http;
use Modules\FluidPay\Models\FluidPayVault;
use Modules\FluidPay\Support\Config;
in my class file. As I said, it works on the on-premise version. But doesnt work on the cloud version I submitted. So yeah, I did all my tests "locally" before submitting a release to my github. So am I missing something? Does the cloud version handle saving customer profile differently?
Showing 1 to 1 of 1 discussions