Jump to content

Community

[[Template core/global/global/lkeyWarning does not exist. This theme may be out of date. Run the support tool in the AdminCP to restore the default theme.]]

Mark

IPS Staff
  • Content Count

    36,066
  • Joined

  • Last visited

  • Days Won

    107

Mark last won the day on January 4

Mark had the most liked content!

About Mark

  • Rank
    IPS Developer
  • Birthday 03/04/1992

Profile Information

  • Gender
    Male
  • Location
    Sydney, Australia

Recent Profile Visitors

143,509 profile views
  1. You should see this: And then the form your screenshotted is what appears if you click "Continue as New Member".
  2. I still use an RSS client 😅
  3. PHP 7.1 or higher required (no particular recommendation beyond that other than of course the latest is always a good idea). MySQL 5.5.3 or higher required, 5.6.2 or higher recommended (though again, latest is always a good idea).
  4. There is backwards compatibility so you should be fine 🙂 If you want to update it, we don't have any specific documentation, but if you take a look at one of our login handlers, the methods are all well documented.
  5. Not to the end user. Mostly from people who either didn't read the terms and got their accounts closed or are confused about how chargebacks work (which is not something the gateway has any control over).
  6. End-to-end encryption is not really possible as there is no method for storing the keys in a browser with reliable persistence (unlike in a mobile app). Note that "secret comversations" in Facebook Messenger, for example, can only be created and viewed on their mobile app, not their website.
  7. Not at this time. Most gateways, including Stripe, Braintree, and PayPal, do not allow most types of adult content. It was probably that. Obviously this is out of our control. I have expensive tastes 😂 (also specific purchase amounts trigger certain behaviours when in testing mode).
  8. Yes it is. Just like with Stripe you set up each as a separate payment method (but using the same credentials). This allows you to control where they are available (for example, since Apple Pay cannot handle recurring payments you might want to offer that only for products which don't have renewals). They will automatically hide if the user's device doesn't support them (Apple Pay can only be used on Apple products, for example). You can set the "Available To" setting in a payment method (which controls which countries it is available to) to none of them, which effectively "disables" a payment method. You can keep using Stripe for cards and just switch to Braintree for PayPal. If you wanted to switch everything to Braintree to have everything in one location, you would lose cards customers have stored on file (though this would be handled gracefully - they'll just be sent an invoice like they would if their card had expired).
  9. Other than notifying Commerce about a dispute (which does use a webhook), everything is initiated by Commerce's end. If a user revokes permission for the recurring charges from their PayPal account then the next time Commerce tries to charge it, it will treat it the same as it would a declined/expired credit card: it will try to use any other payment methods they have on their account and, failing that, will send them a renewal invoice.
  10. So if there are two packages: one costing $10 and another costing $30, you want a user upgrading between them to be charged $30? Why would the user not make a new purchase and get a full renewal cycle? Wouldn't $20 (which can be achieved by choosing the "Difference between the purchase prices" option) make more sense?
  11. Braintree is a payment gateway provided by PayPal which provides some great additional features for PayPal transactions including a significantly improved recurring payments model. We are delighted to be bringing full support for Braintree for Commerce in Invision Community 4.4. What is Braintree? Braintree is a payment gateway provided by PayPal which supports taking payments by credit cards (including Apple Pay and Google Pay) and Venmo as well as PayPal, providing a good option for communities wanting to use a single payment gateway, and also brings improved functionality for recurring PayPal transactions. For PayPal transactions, there are no additional fees and the checkout experience uses the normal PayPal experience your customers are used to. Recurring PayPal Improvements Recurring payments / Billing Agreements in PayPal have up until now been initiated by PayPal. Invision Community tells PayPal what the renewal terms of a purchase are, but then it's up to PayPal to take that payment and notify your community when it succeeds (or fails). This comes with a number of limitations and problems. It makes it difficult for you as an admin to modify an existing purchase or for the customer to upgrade/downgrade. It also means the customer has to create separate Billing Agreements for each purchase. Most significantly though, it means if there is a delay in receiving the payment (such as an expired card) it is sometimes unclear what should happen on your community's end, and how it can be resolved if/when the payment is received. Other payment gateways work the other way around. When a customer pays by card, for example, they have the option of storing their card details. Later, if they make another purchase or a renewal invoice is generated, Invision Community can tell the gateway to recharge the same card - and if it fails, allow the customer to provide an alternative payment method. This allow both you and your customers to have much greater control, and is much more reliable. Braintree resolves this by allowing customers when paying with PayPal to save their PayPal account in the same way they would save a credit card on file. When paying with PayPal, users will see a simple checkbox which, if checked, will allow future payments to be taken with PayPal automatically. Storing PayPal Accounts for Recurring Payments Other Features In addition to an improved checkout experience, our integration with Braintree supports: Taking payments by Credit Card, including 3DSecure checking and the ability for customer to store card details on file. Braintree uses a fully PCI-compliant method of taking card details in a way that ensures the card information never reaches your server. Apple Pay and Google Pay Venmo, which also allows storing accounts in the same way as PayPal accounts. Offering PayPal Credit Handling chargebacks/disputes Support for Braintree's Advanced Fraud Tools A Disputed PayPal Transaction Existing Setups and Upgrading The existing PayPal gateway will continue to be available for basic PayPal integration, and your existing set up will continue to work exactly as it does now after upgrading. If you are using PayPal, especially if you are using Billing Agreements, we strongly recommend switching to Braintree after upgrading. While it isn't possible to convert existing Billing Agreements, you can allow existing ones to continue to work and use Braintree for new purchases. Please note that while existing setups will work fine, from 4.4 it will no longer be possible to set up a new PayPal method with either Billing Agreements, or to take payments by card, as PayPal has deprecated the API this was using in favour of Braintree and it can no longer be enabled on new accounts. As mentioned though, this does not affect any existing setups, which, if you do not switch to Braintree, will continue to work as they do now. This blog is about our upcoming release Invision Community 4.4.
  12. We have no plans to remove the \IPS\Ftp classes, which are used by the upgrader. But the ability to set up the system to store uploaded files like attachments on an external FTP server was deprecated in 4.3.0 (i.e. 8 months ago).
  13. It's actually still there so people who were using it wouldn't suddenly end up with things broken. You could add a row to the table in the database where the configurations are stored if you really wanted to.... but I wouldn't recommend it. It was notorious for causing errors where the FTP server's flood protection or other limitations would suddenly block the connection and then suddenly the community would be unable to upload anything and have other issues caused by the communication not working. While some who knew what they were doing were able to configure the FTP server in a way that these issues wouldn't happen, it was used by such a small number of communities (like... less than 0.1%) and the percentage of those it caused irreparable issues to was so high, it just made sense to deprecate it. Especially in today's world where more robust solutions like Amazon S3 are available. Or, as you mention, a virtual drive on the webserver.
  14. Happy New Year from Sydney! 🙂
  15. To clarify since @Joel R mentioned me specifically... 😂 We will be sticking with CKEditor 4 for a little while. While we will presumably move to CKEditor 5 some time in the future, it is currently still very new and maturing (when Joel asked me, it was before 5.11.2.0 was released which is when they re-added paste from word). But most importantly, to move would require a lot of development time (to upgrade our custom plugins) for what will be, to the end-user, very little change. And since CKEditor plans to continue releasing updates to version 4 for the foreseeable future we're not missing out on bug fixes or security patches. Obviously if you're experiencing issues, please submit a support ticket and we can look into that - if you're not seeing the same problems on CKEditor's demo, the problem is likely our end and so it's probable that moving to CKEditor 5 wouldn't resolve it.
×
×
  • Create New...