Had a little hiccup. Webpack ran into an issue after Bootstrap updated from 4.1 to 4.2. It was a breaking update and had me cussing a little. It turns out there was a line in my code that required the module "./" I see now why it didn't want to play nice.
-
Show this thread
-
Sidenote: I hate Bootstrap. Gimme something completely unstyled and let me handle it. Working backwards from Bootstrap is a nightmare.
5 replies 0 retweets 0 likesShow this thread -
Back to designing and building out the app now after a break to go explore some of the Incredible sights Bali has to offer. Here's the design I just knocked up for the first part of User registration.pic.twitter.com/fOV9QuQNUK
1 reply 0 retweets 1 likeShow this thread -
One BIG lesson I learned from when I started https://givewithella.com is that charities just don't have the time or resources to give you any attention. Getting meetings was tough, and ultimately became the downfall of the project.
1 reply 0 retweets 0 likesShow this thread -
So with Impact Inbox I'm going to take a different approach. I'm not going to ask the charities for permission before I take donations for them. What this means is that I have to be completely transparent so users are sure there's no funny business going on. Trust is key.
1 reply 0 retweets 0 likesShow this thread -
And with time (if the project grows in popularity) the project will prove its worth and getting charities on board won't be such a challenge. For the time being though, I'm going to choose the charities we'll support.
1 reply 0 retweets 0 likesShow this thread -
After all the money is collected and split between the charities in a given month, I'll film myself donating to the charity on behalf of Impact Inbox subscribers. I'll likely add these videos to the users dashboard so they have an easy way of finding them.
1 reply 0 retweets 0 likesShow this thread -
The design is now down for the rest of the registration process. Time to dive back into the code.pic.twitter.com/nikhIW5Zrx
1 reply 0 retweets 0 likesShow this thread -
Problem No 2 It occurred to me that I had setup
@stripe, but not tested it. So I ran a test. It failed. Well, Stripe didn't. There are no errors in my Stripe admin, and I can see the transaction succeeded. But@laravelphp gives me a 500 error & no further information on why.1 reply 0 retweets 0 likesShow this thread -
This gets weirder. So everything is actually working. The transaction goes through and Laravel recognises that - A refresh shows the plan that Laravel previously told us it could not process is active. I'm not sure how to debug this one.
2 replies 0 retweets 0 likesShow this thread
Feel free to reach out to us at support@stripe.com and we can take a look!
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.