The discussion revolves around a paid task to integrate Stripe with Discourse, as the current inbuilt plugin doesn’t meet the requirements. Chaitanya_Khanna posted the task, offering a budget of $400 and a deadline of 7 days. ashishdungdung asked for clarification on the type of transactions that will be triggered, such as subscriptions or donations.
Moin shared a related feature request on Meta Discourse, which mentions that the CEO plans to implement Stripe payment gateway. merefield advised against proceeding with the custom development, citing the low budget and the potential conflict with the upcoming official implementation. Instead, they suggested waiting for the official version.
pfaffman responded, agreeing that the budget is too low, and shared their own experience trying to create a stopgap solution. They encountered issues with the addressElement not populating, despite adding the necessary code, and are struggling to understand the Ember framework.
What would you like done?
Integrate Stripe with Discourse. Current inbuilt plugin doesn’t work best for us as doesn’t have all credential card associated fields. Need it custom developed.
When do you need it done?
In next 7 days.
What is your budget, in $ USD that you can offer for this task?
$400
Understood the integration part but can you describe for what the transactions will be triggered? Like for subscription or token/gift or donation?
Maybe it helps if you link the related feature request
Which has the CEO stating they are going to implement it?
imho this budget is too low, you are far better to wait and take out a loan in the meantime (the interest is going to be less than the plugin budget?). The CDCK solution will tick all the boxes, cross t’s and dot i’s. Wait for it imho.
Additionally, you don’t want to introduce potential conflict by having a developer start the project, only for the sponsor to abandon it half way because the official version just released?
I thought that for 2-3X the budget I might be able to create something that would function as a stopgap, but I’ve spent a bit on it now and can’t get the addressElement to populate.
I add it here:
and see that it’s there, but when it gets over to
The addressElement is missing. Interestingly, if I don’t set cardElement in the first section, it still shows up as undefined when I log it in subscribe-show.js. I don’t see anywhere else in the code that cardElement that is making it available in this of subscribe-card.js, so there’s still something about Ember that I’m missing, it seems.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.