@leevigraham@CraftCMS Also handy when using global fields inside emails, where specific style information needed for proper email rendering might get stripped out by the CMS or accidentally deleted by the author.
Issue with paying via Stripe -- getting Unable to normalize payment token: tok_1Hf4##########, because Expired API Key provided. However, the secret key has not expired and creating a new secret key on the Stripe admin still shows same error. Help! #craftcms#craftcommerce
@JayBox325@lukeholder I had issues when trying to have two Stripe accounts (one for test and one for prod). Switched up method to use single and store keys in the .env file. Means if we want to test a production real test on dev then have to edit the keys but not too bad.
brain is fried and trying to figure out updating a craft commerce stripe payment form to payment intent to avoid the dreaded “No such source: tok_xxxxxxx”. Anyone around that could assist? #craftcms#craftcommerce
@Michael55698384 I have not yet — rolled back using backup composer file and did a composer update which resolved the issue of accessing the site. Will just wait on updating commerce from 3.1.12 for a while.
All was going swimmingly with CraftCMS update to 3.5.0 but then commerce update crapped the bed afterwards and even composer rollback failed. Exception 'yii\base\InvalidConfigException' with message 'Failed to instantiate component or class "yii\shell\Bootstrap".' #CraftCMS