Jump to content



  • Content Count

  • Joined

  • Last visited

  • Days Won


 Content Type 



IPS4 Documentation

IPS4 Providers

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog


Everything posted by Lindy

  1. If you are saying that you have honor permissions disabled, have only selected certain forums and the widget is showing topics from other forums, not selected, then yes, that is a bug. As mentioned, an issue related to this was fixed last week. I'll take a look at your ticket and ensure it was applied when you updated.
  2. Just to be clear - when we say a third party resource is causing an issue, we do not necessarily mean the application or plugin itself is the root cause. We try to trace it to a specific third party resource for you, but once we identify that the issue is resolved by removing or disabling a third party resource, I'm afraid that's where our involvement ends. The actual underlying issue could be the resource itself, adverse effects from the interaction with other third party resources (this is common for folks that install half of the marketplace), an environment interaction with the resource or a number of things. Unfortunately, it is not within the scope of IPS support to determine which case may apply, so we will simply advise you to reach out to the author or remove the resource.
  3. I'm sorry for further confusion. This is not cloud related (in fact, very few should see any impact from the maintenance) - this is a bug in 4.4.0 that was patched. If you are experiencing this issue in 4.4.0 (and even if you're not) - please make your way to your AdminCP and then click Support -> Something is not working correctly. You will find a patch available (assuming you have not already applied it, of course) -- please click through that to apply. Thanks. (OP - this has already been done for you, as noted in your ticket.)
  4. You should be all set - I'm very sorry you had trouble.
  5. We have been asked by customers to intervene on this resource as it appears the author has gone MIA. This, of course, is always regretful. We have reached out and should we receive a response, we will revisit - however - at this time, purchases have been disabled and we will close this support topic. Existing customers will be able to download for the time being. In terms of refunds, all app stores work on the premise of all transactions being final. This is simply because the money you spend goes back out to the author. As a convenience to our customers, we provide a central resource for pre-screened themes and modifications. This avoids you needing to provide personal information to a third party and also allows us to review each original submission to ensure it complies with basic security standards. With this convenience, however, comes a certain degree of risk on your part. Naturally, in the event an author has withdrawn their funds and disappeared, the recourse is minimal and there is no ability for us to refund your purchase, except at a loss to us - which, per the Marketplace terms, we are unable to do. The first inclination in such a situation is to simply file a payment dispute. Please understand that this does not impact the author if they've collected their funds, we take the loss and have significant chargeback fees imposed upon us. Because this has amounted to thousands of dollars in losses every year, rendering the Marketplace a consistent loss to IPS, we have to take a hardline approach on this method and per our Standards of Service and Marketplace terms, any chargeback will result in account and often license termination. I'm very sorry that this is the unfortunate reality in these rare circumstances. Digital marketplaces and app stores are not a perfect system and all parties assume a certain degree of risk. Most of the time, it works out. Sometimes it doesn't. In those infrequent cases, we do our best to try and minimize future losses for customers as quickly as possible. We take our responsibility to help safeguard you seriously. If you have any questions or concerns, please feel free to reach out via the client area. Thank you.
  6. Thanks for reaching out. The first issue seems like a bug. I have copied it to the beta bug tracker and you can follow it here: With regards to your second concern, I'm afraid we will not be actioning that. Our official position is that you should not manually manipulate the URLs. The number and structure of components in the URL is required and should ideally not be altered. I understand your underlying use case for doing so (the first issue) - but again, that's a bug and hopefully we can address it.
  7. Sorry for the confusion. The title has been updated to reflect it's 4.4 beta.
  8. There are still no plans to do so.
  9. Much of this is now available via gateways like Sendgrid. On our Community in the Cloud offering, we have built-in bounce management. If an email cannot be delivered or has been flagged by the user, we will never attempt to deliver again.
  10. I'm sorry for your disappointment. Please understand, feedback vetting is not something any one employee can undergo themselves. It's an elaborate process in which every department chimes in, it's then moved to an internal tracker and our roadmap is compiled based on a number of factors including how a particular suggestion fits in with the scope of a release. In short, it's difficult to comment on a particular suggestion unless it's already on the current release roadmap. This is not targeted for 4.4, but is unofficially (not set in stone) targeted for a future major release. In the interim, as noted, a third party resource is available to fill this need for you.
  11. Have you considered leveraging the edit timeout for this purpose (minimizing damaging due to rage-quitting?) We can certainly see what kind of traction this feedback gets over time, but from my experience, it's equally - if not more - confusing and damaging to have a member run through and edit/delete individual posts, which often disrupts the flow and context of the conversation.
  12. I agree. I don't know how it's slipped through for so long, but it will be addressed.
  13. It's tricky when the ecosystem is largely derived from low-cost apps and plugins. Most third party developers start with the best of intentions -- meeting a specific need for what they feel is a reasonable price. Often (certainly not always), many unfortunately underestimate the time commitment involved with having too many resources, too many customers (which sounds like a great problem to have on the surface, until you factor in the app is $5 and it's pretty easy for one customer to consume $100 worth of your time in support) and they subsequently decide they would like to thin out their offerings and focus on more lucrative, sustainable projects. I don't fault them per se - Invision Community is a fast paced product and it's not easy for third party authors to keep up. I'm quite sure it's easy to get burnt out. That's why I always encourage contributors to focus on quality vs quantity. Have fewer resources, but make them rock solid, always up to date and if it's going to be a paid resource, ensure it's something that can financially subsidize the time you're investing - otherwise, you will lose the motivation and eventually, so will the next author for the same reason. Whether it's $10 or $1000 - if a customer pays for something, it is a risk for the customer, but a commitment is made and reasonable expectations should be met. That's more challenging to get across when you can so easily tap out and hand off accountability. Apps were being traded around like Pokemon cards and with no offense intended, the very people that are generally first to say "I'll take it", as ambitious and well intentioned as they may be, often are the exact people who should not take it - they have too many resources already that are lacking proper updates and are prepared to further compound the issue by taking on even more. Often, the authors that would do really well with the app rightfully do not want to assume the responsibility because they recognize it may have been priced far too low, the overhead is high and/or the existing customer base for the resource would overextend them. In the end, the customer and IPS both lose. The original author has already collected the commission, but the new author has no vested interest in the commitment to existing customers. The customer often ends up holding the short end of the stick and IPS is the intermediary with disputes, which is a huge financial and time loss. We had to stop allowing transfers both to reinforce the significance of the commitment being made to paying customers when they put out a resource, reduce customers being bounced back and forth like ping-pong balls and minimize our exposure in terms of financial disputes. We are less finicky about free resource transfers and in some relatively very rare circumstances, we will consider a paid app transfer to a reputable author when it's clear the the original author is leaving the Marketplace altogether, the commitment to existing customers is very clear, understood and acknowledged, and the receiving author does not appear to be already overextended so-to-speak. We've been getting more strict with what goes into the Marketplace; we have a great team overseeing it and the authors have done a great job at helping us begin to turn it around to provide greater stability in resources and increased confidence from a customer perspective. General Marketplace transfers would unfortunately be a giant step backwards at this time.
  14. In many cases, you may temporarily hide a topic while moderating individual posts within the topic. Having the entire page 'pink' -- normal posts and already hidden posts -- is very confusing. Further, the new(er) "deleted content" feature also utilizes topic view so you can view the content in context. If the topic is hidden and an admin/moderator is reviewing why content was deleted, this would again be confusing if the entire page is pink. I've moved this topic to the feedback forum and you are welcome to provide suggestions (short of making the whole page pink) if you don't feel the eye slash icon is sufficient.
  15. Welcome back! You should be able to still download addons (unless the author requires renewals that you've not paid) and most areas of the community should still be accessible to expired customers. As mentioned, please submit a ticket and we'll be happy to take a look at your account. Regarding URL changes - the perception that an active license is tied exclusively to only support is a misconception due to the way licenses were handled many years ago. For quite a long time (approx. a decade), the only thing an expired license allows you to do is continue using the software as it was at time of expiration - meaning, on the same URL, the same existing installed version, etc. An expired license is just that, so unfortunately, that is why you're not able to update the URL, reinstall or download until the license is reactivated -- we don't shut off the software or prevent use when a license expires, but just about everything else requires an active license. Sorry for any confusion and frustration - please get in touch with us and we'll work on getting your account back in order.
  16. Chris - Firstly, thank you for 15 years of business, we appreciate it! There were in fact multiple reminders about the survey, but as noted, this particular one targeted active customers. I completely agree that feedback from those that let their license lapse is important as well, but that wasn't the focus of the experimental survey we pushed out last year. We now have, baked into the software, a renewal reminder that appears in the AdminCP before a license expires. If you choose not to renew, it allows you to easily let us know why and we do review all of those responses. Naturally, you're also welcome to contact us at any time with any specific feedback - you have a standing invitation. ? That was our first ever survey of that scale and it was extremely beneficial, with thousands upon thousands of responses. There were several concerns that were common across most such as search, Commerce and Gallery. We then took the more elaborate responses ("I hate it" or "It sucks" isn't the kind of feedback we look for and will generally not follow up on it, vs "I find it difficult to search for partial model numbers") and conducted mini focus groups with those clients. As a result, search was vastly improved, we made numerous Commerce improvements with more planned for 4.4 and the Gallery interface and upload process was improved in 4.3. It's a system we really like and we will continue to use moving forward. With that said, we will not likely announce them as they would rarely target all customers and former customers of all types, with all apps, all at once. To gather usable feedback, they really need to be a touch more focused. So, it's important to keep @Invisionpower.com whitelisted.
  17. This is logged for internal consideration and I'm not saying we won't do this, but keep in mind, at least in the interim, you can change the display name to that of your choosing before you delete it to accomplish your goal.
  18. Remember that time Rikki worked here? Me too. Dark days... glad those are behind us.
  19. @DReffects2 - I appreciate you've done extensive research as applicable to your situation jurisdiction. We have expended an enormous amount of time and resources aiding our EU clients with GDPR compliance to the best of our abilities and it's our understanding, we've actually done more than most similar platforms. A temporary line has to be drawn somewhere or we're going to end up with, as Matt said, a barrage of half-baked features and checkboxes everywhere. We have consulted with the ICO, our largest EU clients and perused legal resources and are confident that our implementation as of 4.3.3 will help satisfy your compulsory requirements under the GDPR. I know you don't like the "let's wait and see" approach on your remaining potential concerns, but that is in fact a key purpose of the judicial system -- interpreting and providing subsequent guidance on existing regulation. We are committed to adapting and accommodating as needed, I assure you. We aren't, however, able to go crazy and toss things in based on armchair interpretations. From a layman perspective, a simple checkbox here and there seems easy. From a development perspective - you need to do something with that checkbox. As the contact form, when configured such, is merely an email form, there's nothing to do in the same way there's nothing to do when you actively send someone a traditional email -- you're sending the email because you want to initiate contact. If you wanted a "simple" checkbox on the contact form that's simply sending an email, you then need to provide a mechanism for obtaining consent, store the email address, store the consent, provide a mechanism to withdraw the consent to store the email, etc. None of that is necessary based on reasonable interpretations of the GDPR, so as developers with finite resources, we need to weigh out these requests that amount to a fair amount of development time with limited basis and simply say, if you're super concerned about untested, unchallenged, extreme interpretations for things like this, it's likely best, for your own peace of mind, to simply not use the feature. I say with confidence that although ultimate compliance with any local, national or international law or regulation is the responsibility of the community owner; 4.3.3 is GDPR friendly. If you feel you need to be more restrictive based on additional member state requirements, interpretations or even personal peace of mind - you can of course disable embeds, disable the contact form, disable spam mitigation, disallow tech support and/or peruse third party solutions. It's my opinion, however, the EU authorities are not intending to cripple the Internet or make it cumbersome, inconvenient and unenjoyable to use; only to hold providers, controllers and processors to task for safeguarding data... and in that regard, it's only a good thing. There's a lot of information, opinions and suggestions floating through the comments here and it's difficult to keep track of. We welcome you to engage us via a support ticket for software and corporate specific information and, of course, you may use the client forums to discuss various scenarios, share opinions, tips, etc. We appreciate the feedback and participation. Let us know if we can be of further help.
  20. Chris - there's a lot of info flying around here, so I'm sorry if I'm misunderstanding your goal. We actually have a lot of customers now that don't buy the forums app at all. Some use Commerce only, but most use Pages and Commerce. As noted, the forums are not required for... well, anything beyond forum-y stuff. Unless you've required a purchase, registration should always be available at <yoururl>/register (https://invisioncommunity.com/register for example) We totally agree about the gift card / guest scenario and it is in fact on our roadmap. I can't recall offhand if this is on the 4.4 list, but I can say there are many, many improvements to Commerce in 4.4. Don't let this sort of thing fester, Chris. Hit us up and pitch your use case and what you're trying to accomplish - some people use the software for some crazy cool things (the craziest that comes to mind is an ambulance dispatch system) - give us the chance to tell you if there's a built in solution, if we're able to make an accommodation or even if it's "sorry, no can do!" We run split installs ourselves -- this community powers the site and forums; another Commerce-only install powers the cart, support and client area. We have very few customizations (other than things like a hook to make PM view wider... ha! I slay me) to make that possible so we can upgrade with every release just like you do.
  21. Sorry for your disappointment, Chris. For what it's worth, no one person at IPS writes the product roadmap. I assure you that there's no secret society, whispers or handshakes; when a suggestion comes up, there is a multi-level vetting process that ensures all angles are accounted for: can we develop it? can we sell it? can we support it? Things do not generally just get added willy nilly these days - no matter who you know. ? Regarding PMs, I would hope that you are already aware that you can in fact search PMs. This does not drill down to specific messages, which may be the crux of your concern. I don't think we're adverse to exploring this, it's just not regularly come up as a "must have" and to be honest, I'm not sure it's typical to have 1000 messages in a single conversation. I'm not really sure I understand your contention regarding the "desktop view." It looks and behaves like similar systems such as Facebook messenger, for it is in fact a messenger and is not really intended to behave like an email client. Regarding addons - we allow extremely deep integration with the framework. It's frankly a double-edged sword at times in that third party authors have a lot of flexibility, but because of that, we can't always "sandbox" modifications the way Apple can -- meaning, an app on your iPhone isn't going to break your entire iPhone as Apple does not allow third party developers to interact with the device or OS on that level. With that said, hopefully in 4.4, we will have - and require third party authors to use - an IPS hosted versioning system. This means that when an author updates their resource, it will show in your ACP as an available update. Now, this doesn't guarantee a resource will be updated to address any compatibility issues, but it should go a long way in minimizing the need for customers to go down their list of resources and check each listing in the marketplace. While I personally don't do a lot of web browsing on mobile - the fact is, 66% of all web users do and that number is steadily rising. Mobile has been a strong focus and for good reason - it's kind of a big deal and I can say with complete confidence that you would be in the overwhelming minority of "people that pay the bills" (for which we're appreciative) that are unconcerned with mobile. ? As I've said many times in the past - we don't develop for our own personal interest; we develop for the customer-base at large. If we had a large segment of the customer base that wanted an email client-esque experience with the messenger, we'd of course prioritize accordingly. A growing number of clients wanted alternate search options, for example, so -- we [finally] did it. We need to focus on providing current/modern technology that empowers community operators to remain relevant themselves via a solution that engages an audience accustomed to a social media type experience. So, respectfully, things like social promotion features and integration, clubs, revenue generation, mobile experience, etc. unfortunately do take precedent over accommodating more limited use cases (comparatively) like using the PM system as an expansive helpdesk (Commerce has helpdesk functionality.) I can tell you're frustrated and something has been festering, so I'm glad you got this off your chest - we appreciate the feedback. If, however, you really feel our direction with things like responsive technology/mobile support and the items I've mentioned that promote social engagement, clubs, monetization, etc. is "the wrong direction" - I know you don't want to hear this, but I really feel you'll continue to be disappointed with our platform. While there are many "basic" things we would like to do (and eventually will), including spruce up the reporting and PM systems - nothing else matters if you can't keep your existing users engaged and capture new audiences, so that's where we feel customers want us to place the most attention. We're always willing to stand corrected and we have not been around for 16 years by discounting customer feedback. Nonetheless, we know we can't be everything to everyone, try as we might. I wish I had a "sure, we'll do that!" magic bullet fix for you. I will check into the feasibility of contextual message searching in PMs though - that would be a handy feature. Thanks for sharing your time and feedback with us. I'm sorry again for your overall disappointment and wish I could do more to help. Hopefully you'll stick with us, but I wish you the best of luck on whatever path you choose.
  22. Sorry guys, while 4.3.3 has the GDPR improvements, it also contains numerous bug fixes and so we need to carry it through our normal release schedule. We avoid late-week releases because we are not open for general support on the weekends. Tuesday is our target release date. Have a good weekend!
  23. You guys may wish to start a peer-based GDPR topic in the client lounge or similar to share your thoughts, tips and interpretations and carry on an ongoing dialogue amongst each other. You may pick up or be able to share some insightful information that will likely be lost in the shuffle here.
  • Create New...