Jump to content

Community

Lindy

Management
  • Content Count

    4,159
  • Joined

  • Days Won

    258

Lindy last won the day on August 26

Lindy had the most liked content!

About Lindy

  • Rank
    That Lindy Character

Contact Methods

Profile Information

  • Gender
    Male
  • Location
    Forest, VA

Recent Profile Visitors

106,539 profile views
  1. Have the background tasks completed? The tasks convert all of those old tags to proper HTML. If everything is done and the posts still aren't right, it's important you contact us as soon as possible to investigate. In the event a restore and reupgrade needs to be performed, you obviously do not want to let too much time lapse.
  2. This is a known issue that will be patched next week.
  3. Probably best to take this sort of thing to PM. I can confirm this as a valid alt account and purchase though.
  4. Thanks for reaching out. Somebody else might "get" this before I do, but I'm having a difficult time visualizing what you're after. When this functionality was created, we assume if there's no payment, there's no sale as such and thus, there is no "checkout" / payment. While we can consider a suggestion to provide some sort of "$0 confirmation" - often, there's a different or better way to meet the goal. So, if you could please explain your use-case and workflow, it would help us better understand what exactly you're after.
  5. It's likely you have only opted to restrict new content. You have other options available to control accounts you've flagged as spammer. It sounds like you want to just tick the 'ban member' setting and you should no longer have this issue. 🙂
  6. I’m sorry to hear that you’re frustrated. With thousands of customers across the globe, we try our very best to provide the stellar support that is consistent with our 17yr+ reputation while still maintaining an efficient workflow. Like most companies, we admittedly don’t always hit the mark and when such occurrences are due to a breakdown on our side, we do our best to make it right. With that said, your comments about support and the product are a bit confusing. You’ve submitted 4 tickets this year (not including the “your support sucks” ticket - which we will gloss over as I know emotions can run high.) All tickets were promptly answered - one within 30 minutes. Another within 12 hours - on a weekend. Another submitted on Saturday evening was addressed first thing Monday morning. I’m unable to find any indication that you’ve actually experienced any technical issues that are due to software “faults” based on your ticket history. One ticket was related to branding removal, two were due to third party customizations which, when you said you removed/reinstalled, resolved the issue and finally, the other that seemed to push you over the proverbial edge was our inability to help you change HTTP status codes and customize your server-side error messages, via a support ticket. Your latest issue you’ve posted about elsewhere, but haven’t brought up in a ticket, suggests you may have a rewrite issue. I realize you didn’t get the outcome you were looking for and you have an expectation that we should provide third party / customization support. In a perfect world, we would have the luxury of being everything to everyone, but unfortunately, our product support team are not developers and unfortunately, traversing server systems, debugging code we didn’t write (third party plugins/apps) and pinpointing line numbers to change code for HTTP status codes is simply not a reasonable expectation of base/included support. It’s always disheartening to disappoint a customer and it’s something we take seriously, however, sometimes expectations don’t always fall in line with what can reasonably be provided. Finally, while I have never subscribed to the customer is always right philosophy. I do firmly believe in approaching every service issue individually, ensuring I understand the customer concerns, reviewing the background and identifying where the breakdown occurred. With me personally, approach is everything and as a consumer, I practice what I preach. If my Internet service goes down, I do not call Comcast and berate the agent for I know it is not their fault personally and I find people are much more receptive to a calm, respectful exchange vs rants and insults — treat others like you wish to be treated. Likewise, if a customer approaches and says “I know things happen, but I’m having this issue and not getting anywhere. Can you please help?” I personally guarantee the results will be far more favorable than “you guys suck”, “this is a _____ joke”, “I’m going to sue you”, “I’m starting a social media campaign against you.” The latter will never yield any positive results here. We prefer positive relationships with mutual respect and courtesy; we’re all on the same side and your success is our success. If you’re ever unhappy with a support interaction, please ask for it to be escalated. At this point, I suggest taking a couple of days and then I would absolutely welcome you to contact me personally for further discussion — in hopes of “rebooting” and working towards more positive interactions. Thank you for taking the time to provide your feedback.
  7. Brent, We appreciate the feedback! I certainly understand there are still some niche sites - notably certain techy/dev sites that still rely on to BBCode both because they find it easier and it’s what they know. The (comparatively) few still using it are very passionate about using it and we can definitely appreciate that. At the same time, the BB in BBCode stands for Bulletin Board. It was created long before WYSIWYGs in the 90’s by UBB. The web has since long evolved and with the advance of proper WYSIWYG technology, so BBCode is really rare to encounter. Be it Google Docs, email or virtually any modern editor, we all use buttons or shortcut keys like command-B as second nature, which works even with markdown. The real issue is the fact that it’s simply not native to any modern editor (that I am aware of) - including the one we integrate with, CKEditor. We have a backend “parser” that converts your BBC tags to HTML upon submission, but there is no way to convert that back for editing or any other purpose. To maintain overall stability as well as compatibility with editor updates, our only intention with Invision Community 4 was to ensure some degree of backwards compatibility for those who still use tags when submitting content. The software in fact does that and while BBCode will be deprecated (which simply means it will not be further developed) in a future release, we have no immediate plans to remove it entirely. While there are still traditional software packages that have legacy BBCode support, you will find that most modern community platforms have no native (built-in) support for BBCode and I think it’s extremely unlikely we will ever see it make a comeback (although I said the same thing about bellbottoms.) We are always open to ways to improve your experience with the editor and if you’re struggling to get things formatted properly using native functionality, we would welcome you to open a support ticket so we can see what you’re trying to achieve and try to offer some help. Thanks again for taking the time to share your concerns!
  8. Confusing, right? 🙂 As we’ve been around for nearly two decades, things have evolved and changed. When IPS was founded, there was really only one product to speak of - Invision Board (IBForums) - the company was legally formed as Invision Power Services, Inc. and the product was then called Invision Power Board (IPB.) As the product line evolved and licensing changed, we referred to the products collectively as “IPS Community Suite.” Some called us IPS, some called us IPB, some called us Invision - so when IPB was discontinued several years ago, we began branding as “Invision Community.” The parent company remains Invision Power Services (IPS) - we call the platform itself Invision Community. The package names in the client area is a fair point - we’ll get those updated. Thanks for your continued interest as well as your referrals. Hopefully this helps clear up our identity. 😉
  9. Some companies charge per major upgrade. Some charge a monthly subscription fee. Some charge an up-front license fee and then periodic renewals. We've opted to do the latter. This means you're not paying per version; when you renew, you'll have access to the current versions for as long as your license is active. Because we don't sell on a per-version basis and we typically only support the current major release series, we do not maintain a previous version archive this is true whether you have an active or expired license. I can certainly understand why it might be handy to have access to the last version that was available at time of license expiration and we appreciate your feedback, but this isn't likely we will accommodate, unfortunately. As previously mentioned, I will explore ways we can improve upon clarifying expectations in pending expiration emails so folks such as yourself can be sure to download software for archive purposes and make any last minute license changes before the license becomes inactive. I'm sorry you feel you've wasted your money and hope you change your mind in the future. If so, we will be waiting. 🙂 Thanks for your business.
  10. I am sorry for your frustration. As this is the way the system has always worked, we would welcome the opportunity for feedback on how we could make it clearer in terms of what happens upon license expiration, so you have the opportunity to archive your download and/or make any last minute changes. We want you to renew based on the inherent value in continued development of the software, new features, services such as spam mitigation, support, etc.; it is not our intent to force you to renew under duress and it's most disheartening that you feel otherwise. When you purchase an initial license, the software is indeed yours to use under the terms of the EULA and SoS. The terms dictate that you may use the software as-is, at time of expiration, indefinitely. Unfortunately, as you've noted, reinstallation and downloads do require an active license. There are a few reasons we don't provide downloads of previous releases. Beyond the security and liability implications of providing known-vulnerable software for download, it is also logistically difficult to do so. When you click download in the client area, your download is actually dynamically generated real-time from our release repository. We do not actually maintain downloadable archives (in fact, even internally, sometimes a staff member will need to get an old version from another staff member quickly) and because of the endless app configurations, it's not particularly feasible to do so without a major overhaul to our client systems, our development process, how we use git, etc. Your installed version is recorded as 4.3. Even if you had an active license, we no longer maintain 4.3 in our release repository and there's no way to download it. We don't take away what you've paid for; We simply do not maintain a readily-usable archive of old releases and again, that is the case even if you renew and have an active license and for the aforementioned reasons, it's not something we would be particularly interested in changing. As I said, however, if there's an opportunity to make that clearer, we would absolutely welcome the feedback. Once again, I'm very sorry for your frustration and disappointment.
  11. Is there a reason you're opposed to following the recommendation?
  12. Please submit a ticket if you suspect any issues with your community. Thank you.
  13. I'm very confused, unfortunately. Your original suggestion was asking for the ability to force a credit card to be saved and to force recurring billing. You now appear to be asking for the Stripe subscriptions via checkout method. We do not have support for Stripe "subscriptions" because Commerce handles all recurring billing and Stripe checkout would be redundant. We're certainly not barring you from using whatever you wish, the software just doesn't hook directly into Stripe subscriptions. To be clear: just because I personally am not on board with a feature suggestion does not mean it will never happen. All IPS employees have the ability to grab a suggestion and put it up for vetting internally. Developers, support, sales, etc. each weigh in and it either passes or fails from there. No one person, myself included, makes feature decisions. In this case, I wouldn't stand in the way, but from a corporate and legal standpoint, if the feature were to be introduced, I would insist that the customer not be able to proceed to checkout without acknowledging that the admin is forcing them to store payment details and engage in recurring payments and we'd make sure multiple reminders are sent prior to expiration. I can tell you from my own experience, a good number of payment disputes and chargebacks occur from people who actually opted in to recurring billing and simply forgot that they did so, were charged and called the credit card company to reverse the charge -- which then incurs a $15-25 fee on our end. Chargeback fraud amounts to thousands of dollars per year for us and an average of a loss of $2.60 for $1.00 of fraud. According to stats released by Verifi, Inc. 85% of chargebacks are conducted by consumers who never contacted the merchant. Most banks and processors consider subscription/recurring based purchases to be high risk. It's even worse if they, as you suggested, cancel a subscription before the term is up and you unsubscribe them from all services as they will then try to dispute the original transaction. Finally and most respectfully, you are simply not Facebook, Twitch or Youtube -- nor are we. 🙂 As consumers, we know how difficult it can be to get out of recurring billing agreements (if you've ever had SiriusXM, you'll feel the pain) -- for me, forced recurring payments is already a red flag -- it tells me the merchant is likely trying to lock me into something and hoping I'll forget about it and not pay close attention to future statements... combine that with a small site and it's a non-starter; I'll close the browser and move on with my life. PayPal is somewhat of a limited exception because you, as the consumer, can cancel a billing agreement with ease, without contacting the merchant and without performing a dispute. I won't debate business practices with you as how you conduct your business is just that: your business. Nonetheless, on a software level, I don't personally like this idea because I feel an inherent obligation to protect customers from exposing themselves to the pitfalls of what most institutions consider to be the highest risk transactions. If you're really committed to this and don't want to wait to see if the feature will be picked up by someone at IPS, it would be rather trivial for a third party developer to do a custom project for you and force the CC save box to be permanently ticked and change the verbiage to reflect that. I'd really recommend ensuring you have your disclaimers and legalese in place as we've had more than one customer get shut down by Stripe for funny business. Good luck and I'm sorry we don't have a perfect solution for you.
  14. I'm sorry this has been disappointing for you. It may be of help to note that we do have a payment overhaul roadmapped for the product in the future. Specifically, this would aim to alleviate this sort of confusion and also allow more flexibility such as deciding which payment methods can/should be used for which purposes and explicitly allowing or disallowing recurring payments. With that said, I realize that is not quite what you asked for. In terms of the specific suggestion, I'll be honest in saying I don't love the idea of forcing saved payment methods and recurring automatic payments with no opt-out other than cancelling your subscription. One could make an argument that comparing your community to Youtube or Facebook is apples and oranges. Youtube, Facebook, Spotify, et al will be more familiar with all applicable laws, regulations (which can and do vary) and they will have their own direct relationships with merchant processors. You, unfortunately, will not necessarily have that luxury... in the case of Stripe specifically, their service agreement states you must obtain explicit consent and provide appropriate disclosures to save customer payment information and process their recurring transactions. Subscriptions generate the highest amount of chargebacks for credit card issuers, processors and merchants. Chargebacks are very costly... to everyone. This is why PayPal no longer permits you to accept billing agreements using credit card - you must instead use their Braintree payment service, which is like qualifying for a mortgage and one of the questions on the app is specifically "do you sell subscriptions?" As much as we want to offer flexibility and ensure your success, we also need to be mindful of placing you in a position of getting yourself jammed up because of lack of knowledge of applicable laws and merchant regulations and of course it's important to us to stay in the good graces of those we integrate with, such as Stripe. I would rather focus effort on being clear to the customer from the beginning and give them the opportunity to avoid dealing with manual invoices by simply ticking a box to enable recurring billing. 4.4 also improved what happens when a purchase is about to expire, when it expires and if an attempt to auto-pay failed. If we need further improvement to that area, we're happy to do that as well.
×
×
  • Create New...