Payments; monetize your community

prosurfer

luceos
This guide makes it sound like it's possible to transfer subs from Paypal to Stripe, what do you think?
https://www.depositfix.com/blog/how-to-migrate-from-paypal-to-stripe

luceos

prosurfer I didnt know that. That's fantastic. Reaching out to Stripe about your options, especially since they do have an integration now, would be a great idea.

akrimony12

Not sure if this is the right place to vent out, but some of the Flarum extensions are exorbitantly priced. $185.90 per year isn't commanded by some of the full-fledged Saas programs out there. This kind of pricing automatically excludes third-world country users like me.

I think there should be some sort of purchase parity calculation done for these extensions.

luceos

akrimony12 understand that this is an extension to make money with, so a) you already profit from its use and b) working with money requires a high level of code quality.

Regardless I'm completely in favor of purchase parity. Send me an email and I'll see what I can offer as a fair price. Email is in my profile.

meihuak

I have bought this extension, but I have not install it. can it let people pay any number of money to my flarum or my stripe?

luceos

meihuak you can set up your stripe plans according to the different payment schemes for the extension. It's very flexible. Let me know if you miss anything.

meihuak make sure to follow the instructions when you install, a token for flarum.org and a repository is required in composer: see https://flarum.org/dashboard/subscriptions (instructions button), for the extension manager see https://docs.flarum.org/extensions#adding-a-composer-repository

meihuak

[InvalidArgumentException]
Could not find a matching version of package blomstra/payments. Check the package spelling, your ver
sion constraint and that the package is available in a stability which matches your minimum-stabilit
y (stable).

meihuak

luceos

Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - blomstra/payments[0.3.0, ..., 0.5.19] require brick/money ^0.5.0 -> satisfiable by brick/money[0.5.0, 0.5.1, 0.5.2, 0.5.3].
    - blomstra/payments[0.1, ..., 0.1.2] require flarum/core ^0.1.0-beta.15 -> found flarum/core[v0.1.0-beta.15, v0.1.0-beta.16] but it does not match your minimum-stability.
    - blomstra/payments[0.2.0, ..., 0.2.3] require flarum/core ^0.1.0-beta.16 -> found flarum/core[v0.1.0-beta.16] but it does not match your minimum-stability.
    - brick/money[0.5.0, ..., 0.5.3] require brick/math ~0.7.3 || ~0.8.0 || ~0.9.0 -> found brick/math[0.7.3, ..., 0.9.3] but the package is fixed to 0.11.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - Root composer.json requires blomstra/payments * -> satisfiable by blomstra/payments[0.1, ..., 0.5.19].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

luceos

meihuak are you in the right directory?

meihuak

luceos

meihuak those deprecation errors aren't an issue. What is the rest of the output of the third image?

meihuak

luceos

meihuak try running the command with -W

meihuak

luceos composer require blomstra/payments:"*" -W

this command?

luceos

meihuak correct.

meihuak

luceos thanks a lot, it works

meihuak

I saw the extension in the dashboard, but there is nothing in the front of my flarum, how can I use this extension

luceos

meihuak clear your flarum cache, edit a tag or group from the admin.

Weird_Unicorn

I plan to start my froum free of charge, but will add a small fee later (with more users and more content) for my members. Is there a chance to use the payment-extension like this: Every member has 14 days to explore the forum and after that automatically gets a prompt to subscribe if he wants to use the forum any longer?

luceos

Weird_Unicorn no that's currently not a feature of this extension.

« Previous Page