• Content count

  • Joined

  • Last visited

1 Follower

About IPCommerceorBust

  • Rank

Recent Profile Visitors

5,682 profile views
  1. I'd like to suggest making custom field types the same across the suite. e.g. You can add regex validation to a 'Text' field in Pages, but not Commerce packages. For my purposes, I primarily just need to be able to validate 'Text' fields via regex and length for Commerce packages, however I think unifying the 'custom field' functionality across the entire suite would be a good idea.
  2. Hi, we offer some products in our store which cannot be sold in some states in the US. It'd be nice if commerce packages could be configured to only allow purchases from certain locales, and then enforced at checkout, after the customer enters their shipping address. Something like "The package <insert package title> cannot be shipped to your locale."
  3. I needed this just the other day. It 'just makes sense' in my opinion to offer a discount this way. It is also my understanding, however, that IP.Commerce hasn't quite had its overhaul yet. It is largely still Nexus with a few tweaks. Perhaps Commerce will get its chance once the core functionality and more popular applications are completed, although I would argue that strengthening Commerce first would attract more customers who would be willing to pay more for the immense value it has the potential to deliver. (I've been using Nexus since ~2011, and have been holding out hope for such an overhaul all this time.. lol)
  4. Good to know! Perhaps thats ok though? Having messages imported into the system, and then carrying on via support request could be valuable as well. Appreciate the response Mark.
  5. I really love Commerce and the IP Suite in general because it is an all-in-one solution. Store/Support/Community in ONE software package is downright amazing. For this reason, I'm highly reluctant to switch to some big name ecommerce solution PLUS a 3rd party helpdesk application, PLUS IPS4. My only recourse then, is to suggest the addition of things I love about those other solutions, and hope they can be added to IPS4! One thing 3rd party helpdesks can do that I wish Commerce's support module could do, is integrate with other services like Facebook. e.g. Interacting with customers via Facebook Messenger, all through the Support module in the AdminCP of your IPS4 install: - Customer sends your company's page a facebook message - IPS4 recognizes this via some FB app/API, and sends the message to support in the form of a new ticket (or by some other hocus pocus, matches the FB user to an existing account and/or ticket) - Replying to the ticket calls back out to FB and posts the reply to the FB message with the customer. Seamless! I'm sure this would definitely fall under the category of "easier said than done", but it is just another way IP.Commerce can improve and ultimately increase in value.
  6. I'm sure Commerce will have its day in the sun soon enough, but I've found myself in need of some feed blocks, so here's my formal request. Here are some examples: Package Feed: If I wanted to put a "Popular Products" block on the sidebar that carries on persistently while browsing the store, I'd create a new Block and select Plugin --> Commerce --> Package Feed, with options like whether the package is featured, visible in the store, price range criteria, created date range, whether the product is on sale, which product group(s) to feed from, shipping methods available, payment methods available, custom support fields, sort by Popularity, Date Added, Price, On Sale, Stock Level, etc. Review Feed: In order to create a great testimonials block without having to manually create a custom database managed outside of Commerce, we could just talk to the reviews table with a Review Feed block! Plugin --> Commerce --> Review Feed, options would be hidden/visible/both, star rating, date range, packages, package groups, whether the package has an image, how popular the package is with other customers (similar to above Package Feed), etc. Support Feed: This block would allow us to put a block on the home page or anywhere else showing support requests for the logged in member for quick access. Options would be department, created date range, last replied date range, open/resolved, severity, access to custom support fields, etc. etc. Basically, it'd be great to have a feed for every major component of Nexus/Commerce, with feeds both customers and admins would benefit from.
  7. Any plans to do facebook store integration like bigcommerce and shopify provide? https://www.bigcommerce.com/facebook-shop https://www.shopify.com/facebook I'm sure this is something for down the road as I've discussed this with some team members in the past. Just looking to see whether its on the radar or not. Thanks!
  8. nexus

    It looks like this was added to custom fields for support requests (or it was already there?), but this would still be an awesome addition to custom package fields! P.S. - So far so good testing 4.0.0 with a copy of my live site. I *almost* switched to cs-cart because of missing features like this one, but the complete integration IPS offers is very hard to beat, even in this very early stage.
  9. I don't believe #1 is possible, but here is how to do #2: Go to Admin CP --> Members --> Administrators --> Add Administrator if the Admin you want to restrict isn't already on the list Edit the administrator, then go to the Commerce tab and flip the switch for 'Grant access to Commerce?' Here is a quick video demonstration of this: http://screencast.com/t/JykqSC30p1HE
  10. I encounter the exact same thing, but only when I upgrade from 3.4.6 (copy of my live site, I've repeated this process several times now with the same result). If I do a clean install of Beta 8 it is fine. Also, I do not use cloudflare or any other sort of CDN service. edit: posted this comment to the tracker.
  11. Hi guys, I've finally had a chance to poke around 4.0 (Beta 6), and was wondering about the possibility of adding Custom Input Validation to custom fields in Commerce (specifically regex), similar to how it is available in custom fields for Pages? e.g. - When creating a new custom field, select Text as the field type, and a new option for Custom Input Validation appears where you can enter the validation criteria. It seems to me there should actually be parity across Commerce and Pages custom field type options, at least as far as things like this, field length, and text formatting are concerned. I would love to have a custom commerce field automatically converted to upper case once submitted, as well as limited to a certain number of characters and the option of setting a default value! Thanks!
  12. ^ indeed. This seems like a commonly overlooked option. I think I once asked Adriano to create a hook that does exactly this, only to discover it was already built into the software. lol
  13. Also, apparently the mobile menu blocks the sign in area on my custom skin as well. I believe there should be an option to remove mobile device detection altogether, but there is not. Setting 'Mobile Style min width' to a very small value doesn't seem to work.
  14. Is there a way to make sub-menus open left instead of right? My skin has the primary nav menus on the right side of the page. Thanks!
  15. Sounds like an idea for a custom skin. Default IPB skin with templates broken down into smaller pieces. globalTemplate would essentially just be a short list of calls to display other templates. Whether it would be more efficient would be debatable though. I think once you get the hang of things its not so difficult to find what you're looking for with the way things are now.