Lindy

We would like to take this opportunity to inform you of an important decision we've made with regard to the Invision Community Marketplace. After careful evaluation and consideration, we have decided to discontinue the Invision Community Marketplace, effective October 30, 2023. Over the past several years, we have noticed a decrease in usage of the Marketplace, with a staggering 75% decline in sales. In addition, we have observed a growing trend away from off the shelf customizations towards bespoke tailoring of a community by working more closely with developers. While it has been a platform for many dedicated and talented contributors to share their work, we believe it is time to re-focus our efforts and resources to better serve your present and future needs. We understand that change can be unsettling, but we are excited to share with you our new direction. We are putting our efforts into enhancing the newly introduced Providers Directory, a platform that will enable you to connect with third-party providers for a wide range of services, including custom development, community management/support, conversion services, and other valuable resources. Additionally, many providers will have independent websites you will be able to visit to explore and obtain existing and new premade resources. More details are to follow soon, but we would like to highlight a few key points: • Marketplace renewals will cease effective immediately • New purchases will end September 15, 2023 • The Marketplace will be removed in the October release and disabled on October 30, 2023 • You will continue to be able to install and manage existing and new resources via the methods provided by their respective authors • You will be able to obtain a key for each of your current Marketplace purchases and provide that key to authors to transfer your purchases directly to the author We invite you to visit the Providers Directory and start exploring the opportunities it offers. This will allow you to familiarize yourself with the database and the resources it will provide in greater depth. Many of the current Marketplace contributors have already created their profiles – please check them out! Of course, this does not mean the end of aftermarket development with Invision Community. We are currently building new development tools for Invision Community 5 which have easier ways to add new functionality. We want to express our sincere gratitude for your ongoing support and trust in Invision Community. We believe these changes will enable us to better position ourselves to continue moving forward in meeting the present and future needs of our customer base. If you have any questions or concerns, please do not hesitate to reach out. Thank you for being a part of the Invision Community family. Update We have posted our next blog covering the next steps for obtaining purchases from 3rd party developers. View full blog entry

We cannot guarantee v4 will be supported quite as long as Classic. One of the core advantages of cloud is that we are able to leverage the latest technologies to deliver a better experience than what can be had via the average self-hosted environment. There will likely be a time that updates to the cloud infrastructure will necessitate upgrading from v4, but there is nothing on the immediate horizon and we expect we'll be able to continue v4 support on cloud for some time. Please reach out to sales@invisionpower.com to see if there's anything we can do for you. 🙂

@usmf I'm sorry you're experiencing issues with email delivery. As has been mentioned, our team has confirmed email notifications are being sent. We understand you are having isolated issues with specific members. I've personally looked and it doesn't appear you have a DMARC record for your domain. This was mentioned elsewhere in this topic -- not having a DMARC record will most certainly lead to deliverability issues. I know you believe this is software related traced back to an update applied from October 22, but a quick cursory glance at your domain record indicates you updated DNS in October as well. I would guess you made changes and a DMARC was not configured at that time. This kind of thing often happens in the self-hosted environment as not everyone has experience to manage servers, DNS, etc.... that is precisely why we offer Invision Community Cloud 🙂 I think getting someone with some experience to help you resolve these technical issues will resolve your concern. If you still feel there is a software issue, we do offer advanced diagnostics and debugging services. This is $200 per hour with a one hour minimum. If the issue does in fact end up being directly software related, that fee is of course refunded in full. Good luck - I hope you're able to resolve this issue.

Sorry for the inconvenience; we have deployed a change on our end to hopefully alleviate this concern.

Your community is under heavy Denial of Service attack. We will send this to a ticket for one-on-one communication.

We share your frustration and I assure you that although this is the first major outage event in years and we have a solid 99%+ record, we are taking this very seriously and have already taken both internal and vendor related steps to minimize the risk of this happening again. We have also made improvements to our status and communications system so you remain better informed throughout these unlikely events. I'm deeply sorry for the inconvenience this event has caused. Cloud clients with further concerns are welcome to send a support email and we will be happy to discuss. Thank you!

We are ISO27001 compliant, however, the certification process is still pending. We will also have more publicly consumable reports available in coming months. In the interim, you may find us on the CSA STAR registry and you are of course welcome to contact us via email for more information and specific questions. Thank you!

Unfortunately, not every suggestion or request will reach the product, or at least within the timeframe requested. Data and privacy protection is something we take very seriously and as a provider to customers worldwide, we receive a significant amount of requests to assist customers in achieving local regulatory compliance. While we respect the DSK's position, Commerce was not designed or built to accommodate guest transactions with no corresponding account and incorporating the changes necessary to comply with this regulation would be a measurable effort with very little gain/ROI. It's not something we have necessarily dismissed indefinitely, it is simply not on the radar in the foreseeable future for the reason cited above -- there's low demand and considerable development involved in making the platform do things that are counterintuitive to its chief goals, and thus, lacking the technical provisions for same.

I'm sorry, we are unable to distribute old and insecure versions of the software for download. Perhaps if you can share the issues you're experiencing, someone might be able to push you in the right direction.

Thank you for posting this - we will take a look!

I'm sorry for your frustration. I've gone ahead and done this for you as a courtesy one last time, but unfortunately, the IPS retail system and the Marketplace are two different entities - the funds are not commingled. Doing this compromises the accounting on both ends, so the best way to do this moving forward would be to withdrawal the credit from the Marketplace and submit it to the client area as a normal payment. I apologize for any inconvenience this may cause and thank you for your understanding and cooperation.

I truly appreciate the fresh perspective and positive energy you brought to us, Jordan. I wish you the very best in your future endeavors and have no doubt that you will carry that ++ vibe wherever you go. 🙂 You are certainly leaving a void, however, I'm hopeful you'll continue to check in, let us know how you are doing and sprinkle some of that magic Jordust™ that the community has come to love and appreciate. Best of luck! 🙏

I'm sorry for the delay and your frustration. Your transaction was caught by our fraud screening filters with an unusually high risk score. This transaction should have been automatically declined, which would have provided immediate feedback. I apologize for the lack of communication. As noted in your ticket, we have manually approved your second transaction. We appreciate the opportunity.

This ONLY impacts legacy "Standard 25" and "Plus 40" customers at this time. If you did not receive an email, it is because you are not on those packages and no further action is necessary.

On January 22, 2022, cloud service will be temporarily suspended until such time that a new package is selected. We felt this was a better (albeit less than ideal) alternative to automatically upgrading packages. There will be a 60 day grace period to reactivate an account on a new package, or receive a full backup of the account. After the 60 day window, the account would be purged, per data retention policies I hope that answers your questions and helps alleviates some potential fear and uncertainty.

Yes; by upgrading. 🙂 Seriously though, there is no other way to dismiss it permanently, I'm sorry.

I appreciate the feedback, candor and your kind words as well. Annual payments are something we would still like to explore and if we can modify the infrastructure to accommodate both, I personally have no issue with doing so. It will be something we revisit at a later date. I am truly appreciative of this post; your earlier post(s) troubled me personally as being evil, disconnected and full of marketing fluff is not the image we want to project. I'm grateful you provided the opportunity for the dialogue to evolve, for feedback to be heard and actioned and to witness some of the thought and care that went into some of these changes behind the scenes. I apologize that our communication missed the mark and again appreciate the constructive feedback and patience while we digested and acted upon same. I'm all in on the group hug.

Please make it 8PM on a Friday (EST) and be sure to run the upgrader on mobile with 2% battery life left. Thanks and tell the boys in support Lindy sent you!

I apologize for your frustration. I have chased down your ticket and responded accordingly.

It should fetch the delta via http. FTP is a forced option. Double check the file / dir permission requirements and submit a ticket if those are correct and it's still prompting for FTP.

If you're using it for true mass payment purposes, you should still be within the spirit of the AUP. That policy suggests you would not be in compliance, however, if you are making payments through the system on an individual basis. In any event, there doesn't appear to be any technical changes or impact; it's merely a clarification of policy.

Sorry you're having difficulties, @MorriganIt's certainly not been a wonderful 10 months, by any stretch. 😞 I'm also sorry the notifications are causing you stress. They're intended to emphasize the importance of updates - if you're like me, you've likely clicked the "remind me later" button on OS updates a few dozen times before actually going through with it. Unfortunately, there is no distinction between licensed/unlicensed at this time - if we recommend an update, it's recommended regardless of license status. Nonetheless, I truly understand and empathize with the sentiment -- these are difficult times for many and we don't necessarily want reminders. I'm sorry this has been an example of that for you. I hope things improve for you soon.

Hi there. Thanks for taking the time to share your feedback and I'm sorry for your disappointing support experience. I've taken the liberty to review your ticket history as well as your community itself. I counted almost 50 third party plugins, 15 third party applications for a total of over 200 "hook" points. That is, by most definitions, a fairly significant amount of modifications. There is nothing inherently wrong with that and we of course welcome and encourage you to personalize and tailor the software to meet your needs, however, it does limit the amount of support we are able to provide. I often use an automotive analogy... there are some vehicle owners that make a significant amount of customizations to their vehicle. Some, such as cosmetic changes (tinted windows, spoilers, etc.) have no real impact on the integrity or reliability of the vehicle and there are no warranty issues with the dealer. If, however, you add an aftermarket device designed to change the behavioral parameters of the vehicle (eg. an ECM 'tuner', an electronic device that plugs into the ODB port, an aftermarket head unit, etc.) - it is not a realistic expectation for the manufacturer (and dealer) to warrant and support the vehicle unless the concern is directly related to a "stock" defect or root cause. In the case of your current support request (RSS feeds and image dimensions) - I've looked at the origin feed and the height/width attributes are indeed being sent in the feed itself. Invision Community simply imports what is provided in the feed. You would, as noted in the request, unfortunately need to work with the feed author to remove the hardcoded attributes in the feed. I wish I had better news for you and I understand how difficult and frustrating it is sitting between developers/manufacturers and third parties/aftermarket, as a consumer. Thanks again for sharing your thoughts and I hope your experience improves moving forward.

Wouldn't it be easier to create a 'Banned' group for visual representation if you're going through that trouble?