IPCommerceFan

If we really want to modernize things, we should have a "Night Mode" switch in the corner. (I think there's a theme in the marketplace like this, actually) Looks good! Appreciate the attention to detail with things like this. 👍

Any and all Commerce improvements are welcome, IPS. :) Just to show a little appreciation though, we've come a LONG way since the early days of Nexus.

Call me optimistic, but after seeing the other couple posts pop up about this.... if IPS is committed to continue offering and supporting the Support component of Commerce, then actually using a "top tier" helpdesk solution OTHER than their own product should provide excellent perspective for future updates to Commerce.

I ended up writing a plugin to solve this. Hooked into: \IPS\nexus\extensions\core\MemberACPProfileBlocks\Purchases //<?php /* To prevent PHP errors (extending class does not exist) revealing path */ if ( !\defined( '\IPS\SUITE_UNIQUE_KEY' ) ) { exit; } class hook406 extends _HOOK_CLASS_ { /** * Get output * * @return string */ public function tabOutput( $activeTabKey ) { if ( $this->_purchases === NULL ) { $where = array(); $where[] = array( 'ps_member=?', $this->member->member_id ); switch ( $activeTabKey ) { case 'active': $where[] = array( 'ps_active=1' ); break; case 'canceled': $where[] = array( 'ps_cancelled=1' ); break; case 'expired': $where[] = array( 'ps_active = 0 and ps_cancelled = 0 and ps_expire <?', \IPS\DateTime::create()->getTimestamp() ); break; } $this->_purchases = \IPS\nexus\Purchase::tree( $this->member->acpUrl()->setQueryString( 'blockKey', 'nexus_Purchases' ), $where ); $this->_purchases->rootsPerPage = 15; $this->_purchases->getTotalRoots = function() { return NULL; }; } return $this->_purchases; } } I don't have a "View All Purchases" button currently, nor is there pagination which would be ideal, but this solves the immediate issue of having to wait for hundreds of purchases to load. 👍

Great, thanks. 👍

I'd be interested in what metrics are used to determine what features are most used. Some of our favorite things about Commerce aren't really things we've ever had to mention to IPS via ticket, or post about in the forums. To that end, if a mailer asking "what Commerce features do you use?" were sent out, I'd gladly provide feedback. I've stated this in other posts, but our site is entirely Commerce, Pages, and Downloads, so Commerce's growth is important to me.

I really DO appreciate it. 👍

With InvisionCommunity 4.x.x maturing and talks of 5.x.x starting to come up, I'm starting to wonder whether Commerce will survive considering a "simple" feature like this hasn't been given any attention since 2015. It would go a long way for me, and my business, if topics like this could at least be given some token acknowledgement. I understand having limited engineering resources since I deal with this every day as well. Having to triage what gets attention and what doesn't, inadvertently sending the wrong message, etc. It would just be nice to get a "Thanks for the suggestion", or "we're considering it", or even a "no", so that we can stop wondering if posting feature requests are a worthwhile use of time, and perhaps consider other options.

This would be a great way to keep products updated as well, for instance when suppliers change their MAP pricing. Just update spreadsheet, import, and any existing listings could be updated. Granted this is possible via API in some cases, but some suppliers still send pricing updates via spreadsheet.

Hi, We have some customers who have hundreds of purchases on their account, and it can take a really long time just to load their customer page due to, in our case, loading over 700 purchases into view. It'd be great if we could limit the number that are loaded to 15 just like invoices and support requests, and just have an option to "display all Purchases".

I got this working by modifying \IPS\nexus\Package\CustomField (the actual php file that relates to that class)! All I had to do was: - borrow the $form->add statements for pf_max_input and pf_input_format from \IPS\CustomField\CustomField - comment out the "unset" statements for those fields - Add the fields to the nexus_package_fields table in the database It works like a charm! Now to figure out how to do what I did in the form of a plugin or application since I don't really feel comfortable with the fact I edited the source files directly... Still hoping IPS will roll this into the core product, but I'm very thankful for the fact the framework was intuitive enough to allow this workaround!

I just started experimenting with REST along with Commerce Rules: To fire custom PHP when a purchase is generated. I got it to do exactly what I want, which is to create a new support request when there is a purchase, containing further instructions for our customers. The only issue, though, is it seems SR's created this way do not generate an email the way they do when you go to AdminCP Commerce -> Customer -> New Support Request. So I'm reporting this to see if this is the intended functionality (no email notification for REST API created support requests), or if its perhaps a bug/oversight? Heres some context: //<?php //Purchase Data $p_id = $purchase->id; $member = $purchase->member->member_id; $email = $purchase->member->email; //REST API URL and KEY $communityUrl = '<...>'; $apiKey = '<...>'; //Create Support Requst $endpoint_request = '/nexus/supportrequests'; $curl_request = curl_init( $communityUrl . 'api' . $endpoint_request ); $message = '<...>'; $curl_post_data_request = array( 'title' => 'Support request via REST', 'department' => 1, 'staff' => 1, 'account' => $member, 'email' => $email, 'message' => $message, 'purchase' => $p_id ); curl_setopt_array( $curl_request, array( CURLOPT_RETURNTRANSFER => TRUE, CURLOPT_HTTPAUTH => CURLAUTH_BASIC, CURLOPT_USERPWD => "{$apiKey}:", CURLOPT_POST => TRUE, CURLOPT_POSTFIELDS => $curl_post_data_request ) ); $response_request = curl_exec( $curl_request ); // Grab Support Reply ID for firstMessage of Request $request = json_decode($response_request); $request_id = $request->firstMessage->id; // Change Support Request Author to Staff $endpoint_reply = '/nexus/supportreplies/' . $request_id; $curl_reply = curl_init( $communityUrl . 'api' . $endpoint_reply ); $curl_post_data_reply = array( 'author' => 1 ); curl_setopt_array( $curl_reply, array( CURLOPT_RETURNTRANSFER => TRUE, CURLOPT_HTTPAUTH => CURLAUTH_BASIC, CURLOPT_USERPWD => "{$apiKey}:", CURLOPT_POST => TRUE, CURLOPT_POSTFIELDS => $curl_post_data_reply ) ); $response_reply = curl_exec( $curl_reply ); return "action complete";

This is still not available as of 4.3.6: Commerce --> Store --> Custom Fields This is what is needed (specifically Default Value, Max Length, Custom Input Validation, and Apply text formatter): Pages --> Content --> Fields Fingers crossed for 4.4.

To expand on this, packages which are being upgraded TO sometimes may have more custom fields available than the package they are being upgraded FROM. Currently the "Upgrade" process does not give you the option to fill out any fields which may be exclusive to the higher tier product.

Just because we've received a lot of requests for whether we support this payment method, I'm suggesting this as an addition to Commerce. https://docs.affirm.com/