Mark

IPS Staff
  • Content count

    34,009
  • Joined

  • Last visited

About Mark

  • Rank
    I dropped the "iggy"
  • Birthday March 04

IPS Marketplace

  • Resources Contributor Total file submissions: 5

Profile Information

  • Gender Male
  • Location Colchester, UK

Recent Profile Visitors

131,703 profile views
  1. Gravatar Size too small (80x80)

    system/Member/Member.php The photoUrl() method. Change this: $url = \IPS\Http\Url::external( "https://secure.gravatar.com/avatar/" . md5( trim( mb_strtolower( $memberData['pp_gravatar'] ?: $memberData['email'] ) ) ) )->setQueryString( array( 'd' => (string) $defaultUrl ) ); To: $url = \IPS\Http\Url::external( "https://secure.gravatar.com/avatar/" . md5( trim( mb_strtolower( $memberData['pp_gravatar'] ?: $memberData['email'] ) ) ) )->setQueryString( array( 'd' => (string) $defaultUrl, 's' => 125 ) );  
  2. 4.1.8.1

    This is a very small release to fix a few rather annoying issues from 4.1.8. Sorry about that   Fixes an issue where incoming emails were not being received correctly. Fixes an issue where guests could do a partial account registration which could cause some confusion to the administrator when editing. Fixes an issue where the AdminCP dashboard may incorrectly report tasks aren't running when they actually are.
  3. An issue has been identified in IPS Community Suite where in certain rare circumstances, the toolbars on the editor when making a post may be disabled and not functional. This only happens when editing content which contains spoilers created on older versions that have no content. The issue has been resolved in IPS Community Suite 4.1.9. In the meantime, you can workaround the issue by manually editing the affected content: Go to the edit form of the content Force IPS Community Suite to fallback to the plain HTML editor by disabling JavaScript in your browser Refresh the page and you should see a plain text box with the content's raw HTML Find the spoiler which is causing the issue and remove it. It will be something like this, though there may be content inside: <blockquote class="ipsStyle_spoiler" data-ipsspoiler=""></blockquote>   Save the form Re-enable JavaScript in your browser and refresh the page. The editor should now be working If the issue persists, or you require assistance, please submit a support request.
  4. An issue has been identified in IPS Community Suite 4.1.8 and below where secondary groups awarded by a Commerce purchase may be incorrectly removed. The details of the issue are: This issue has been resolved in IPS Community Suite 4.1.9. If your community is affected by this issue, you can apply a patch by uploading the following file to the specified location: applications/nexus/sources/Package/Package.php
  5. 4.1.8

    This is a maintenance release to fix reported issues.
  6. Hi Mike, Go to Admin CP > Statistics > Sales. You can use the "Filters" dropdown to limit to whatever products you're interested in - this will show you how many of each product you've sold in a specified date range. For referrals - if is handled automatically, and you can see the commission earned on the customer page.
  7. It has come to our attention that some users are experiencing an issue with PayPal Billing Agreements where, after checking out, the user may see a loading icon for some time and after a while the transaction is held for manual approval. If the user closes the page before this process, there may be no transaction logged at all. The issue only occurs at certain times. PayPal have advised us that, at certain times when batches are running on their systems, even though the Billing Agreement is created (and so the user is returned to the site), there can be a delay in taking the initial payment which is what is causing this issue (because IPS Community Suite is waiting for PayPal to provide the details of the initial transaction). PayPal have advised us that their development team is working to reduce this delay to no more than 10 seconds, however they are unable to provide an ETA at this time. We have made a change to accommodate for this in IPS Community Suite which will be in version 4.1.9. In the meantime, if your community is affected by this issue, you can patch the issue by uploading the attached files to the specified locations, overwriting the files that are already there: applications/nexus/interface/gateways/paypal.php applications/nexus/sources/Gateway/PayPal/PayPal.php Note that since this patch isn't in 4.1.8, you may need to re-apply the patch after upgrading to 4.1.8.
  8. Or disable invoices expiring (the purchase will still expire if they don't renew in time, but they'll always be able to pay the renewal invoice). Or set the product to allow customers to renew themselves.
  9. Separate forum for REST API

    I think back when we did that people rarely posted or (other than us) read the non-IP.Board forums.
  10. Terminology

    Products Products are the things which are available in the store for users to buy. Most Products are Normal Products, but if you want to sell Advertisements or Hosting Plans, these are also types of Products. For more information about how to create Products, see Products & Purchases. Invoices Invoices, or Orders as they are called on the front-end, are the things that say a particular user is buying particular things. They can be created in 3 ways: When a user clicks "Checkout" in the Store, an Invoice is created. If a member has any Purchases which have renewal terms, an Invoice is created automatically when the renewal payment is due. An administrator can create Invoices manually in the AdminCP. An Invoice is made up of items which will usually be Products but could also include paid files from the Downloads application, donations, or anything else a user can pay for. Any shipping costs, adjustments for coupons, etc. will also be shown on the Invoice. Invoices will always have one of the following statuses: Paid - the user has paid the invoice (using Transactions) or the invoice has manually been marked as paid by an administrator. Pending - the user has not yet paid the invoice. Expired - the user did not pay for the invoice within the time period set by the "Invoices must be paid within" setting (AdminCP > Commerce > Invoices > Invoice Settings) and so the invoice is expired and they cannot submit payment. An administrator could resend the Invoice in the AdminCP to put it back to Pending. Canceled - either the user, or an administrator, manually canceled the invoice. Payment may have never been submitted, or may have been refunded. Transactions A Transaction is how a user pays for an Invoice. For example, when a user submits their card details, that creates a Transaction. An Invoice may have more than one transaction, for example, if their card is declined and then they use a different card, the Invoice will have two Transactions associated with it: one failed, and one approved. Transactions are usually associated with a Payment Method which processed (or attempted to process) the payment (for example PayPal, Stripe or Authorize.Net). However, if the user chooses to use credit on their account to pay, this will also show as a Transaction with Account Credit if specified as the method. In addition to Transactions created by the user checking out, they can also be created automatically. If a user has Purchase with renewal terms and also has a credit card on file, a PayPal Billing Agreement, or account credit when the renewal term is due, a Transaction to take that payment will be generated automatically when the Invoice is generated. Transactions will always have one of the following statuses: Approved - the payment was received successfully. Held for approval - usually means that the payment was received successfully, but was halted by a Fraud Rule. An administrator will need to manually approve or void/refund*. This status is sometimes also used if there was an error in the Payment Method and the system is not sure whether the payment was received or not - an administrator will need to confirm and either approve or refund the Transaction. Under review - the Transaction was previously Held for approval and an administrator has marked it for review. An administrator will need to manually approve or void/refund*. Failed - the payment was unsuccessful (for example, their card was declined for insufficient funds) or was voided by an administrator. Refunded - the payment has been refunded by an administrator. Partially Refunded - the payment was successful, however the user has been given a partial refund, so it's status is partially Approved and partially Refunded.  Waiting - the user has indicated they will pay via a manual method (for example, post a check or send a bank wire). The administrator should mark this as approved once they receive payment, or cancel it if payment is not received. Pending - it is unusual to see this status, but indicates that the user submitted payment and the payment method has not yet confirmed or denied receiving it. It will automatically change to one of the above statuses or be deleted automatically. * Sometimes you will see a "Void" option for a Transaction and other times, "Refund". When a user makes a payment, most Payment Methods will first authorize the transaction (meaning they are holding the funds), but not capture it until it has passed the Fraud Rules check. This is to avoid unnecessary refund fees for you. In this state, you will see the "Void" option, which will cancel the payment completely, while the "Approve" option will capture and complete the payment. If the transaction has already been captured (some Payment Methods don't support separate authorize and capture, and some have a limit on how long a Transaction can be in this state for) you will see a "Refund" option. Shipments If an Invoice contains physical Products which need to be shipped, then once the Invoice is paid, Shipments are generated. These contain the items and quantities to be shipped, the Shipping Rate to ship them by, and the shipping address. Sometimes more than one may be generated, for example, if the user is purchasing two different Products with different Shipping Rates. Shipments will always have one of the following statuses: Shipped - the shipment has been sent. Pending - the shipment is waiting to be shipped. Once it has been sent, an Administrator should mark is as Shipped. Canceled - the shipment has been canceled, it is possible that payment was refunded (and therefore the Invoice was no longer marked Paid) before the shipment was sent, or it has been manually marked Canceled by an administrator. Purchases Once an Invoice has been marked as Paid, the details of any Products, and certain other items (for example, Files in the Downloads application) are stored as a Purchase. A Purchase may have an expiry date and renewal term, which will cause renewal Invoices to be generated automatically.
  11. Upgrade system :)

  12. 4.1.7

    This is a maintenance release to fix reported issues. Please note that in this release we have updated the copyright data in many source files. This means that if you are upgrading through the Admin CP the update will take slightly longer to download and extract than normal.
  13. Please add Emoji support

    We would like to do this but we don't have an ETA. utf8mb4 is a superset of utf8 so converting should be simple - it's just the indexes are a pain. If you feel up to doing it manually, MySQL does have a guide on their site, or you could use a script like the one @Tracy Perry mentioned.
  14. 4.1.6.1

    This is a maintenance release to fix reported issues.
  15. No change was made for asking for an address, but customers can now be charged automatically.