Chris Anderson

When I setup my site to use PHP 7.4 this app works just fine. As soon as I switch to PHP 8.0 I receive the following error when I click on the clubs app: The same behavior on two other sites. Toggling back and forth between 8.0 and 7.4 yields the same results. No errors being logged.

I have a subdomain: subdomain.mysite.com that I have setup access using "Connect Two Invision Communities". I only want people to login via the "Existing user? Sign In" I do not want anyone to create an account via the "Sign Up" button. How do I disable "Sign Up" button as shown below:

Looks like the making of another great addition to the product suite. Hint, Hint...

@Matt I wonder if you could create a "Spoiler" like functionality that a customer could use to highlight portions of a forum topic that they don't want to reveal to the other customers. Support staff would be able to see the masked text not anyone else. These kind of postings would be left up to support staff to deal with. Other customers may find value following along (as best they can with some details missing) if they think an issue being reported might arise on their site or is already happening.

Not just the current developers but how you can better foster the next cadre of programmers who might one day be great candidates to join your firm one day. Provide a crippled version of the suite to develop on and allow for one or two people to test the apps being developed but not be able to be used to run an actual site off of.

There are a finite amount of technical support staff and hours in the day. If a community member happens to drop by the forums and sees a particular topic posting and provides some form of value-add then that will potentially lessen the burden on the support staff. This might mean a site that is currently down and isn't paying for expedited support gets their site up and running that much sooner. It's kind of like "paying it forward"... A few moments of your time here and there just might pay dividends later.

Please give everyone six month's notice before implementing yearly renewals considering you are also raising prices at the same time. This should allow folks time to implement various fundraising schemes to cover the increased renewal fees and the necessity of paying yearly rather than twice a year.

A new version 4.1.2 was released last Saturday to fix an issue where KW would throw an error in blogs and/or announcements. It may take a while before it is reviewed and made available in the marketplace.

My issue isn't related to patches but to releases and twice now my concerns were glossed entirely over by IPS staff. I give up, go ahead and delete this posting.

I've already applied the patch. I imagine what's included in the patch as well as all of the other fixes that Jordan has mentioned since 4.6.5.1 was released will be rolled up into an upcoming release. With that said, I'm unsure why the Release Note and Client Downloads show 4.5.6.1 is a new release when it isn't. When the version number reaches 4 digits and 3 decimal points it's hard to visually know that you have released a new version so I imagine others besides myself eyeball the release date in the Release Notes or the Client Area.

@Jordan InvisionI dropped by the Release Notes page and noted that the 4.6.5.1 version had been released today. I went over to the client area and it shows that 4.6.5.1 was released yesterday. I looked at the date of the install files in my archive folder and noted I had already downloaded 4.6.5.1 on 7/28/2021. Why are you showing a new release date for a version you released two weeks ago? If you released an updated version why didn't you change the version number and alert the ACP that a new version is available to update to?

This could allow members and developers to upload pages to the marketplace. Some might be offered up for sale and some might be used for learning purposes and some might be offered up to the community to further flesh out an idea. The more examples we have pore over the shorter the learning curve will be and the more customers will utilize them more fully.

@Jim M Where do you document which browsers (and versions) you "officially" support on this site? I would think its an important detail that prospective and established clients should be made aware of (and communicate to their members) outside of being mentioned in random forum postings that may not be read by all. Browser support would be a great inclusion in the FAQ sections located here: Sign up for Invision Community in the Cloud - Invision Community and Invision Community self-hosted licenses - Invision Community

The challenge is there are hundreds of different browser versions currently being used by desktop and handheld device users throughout the world. Some folks stick with versions that have been around for years whereas some folks update their browsers on a weekly or daily basis. International Standards exist and are periodically updated to include new functionality, or they may make changes or deprecations. Few browsers support any version of the International Standards 100% or it may take several releases before they reach that milestone. Some browser versions have been released over the years to support various functionality of an upcoming International Standard’s release in order to get a jump on their competitors. Browser extensions “could” materially alter the browser experience. Each user expects every site they visit to work "as expected". Your “as expected” may be materially different from your members and those of IPS. Some releases may fall more into the “as expected” territory than others as sites continually change and some changes might not play well with a particular browser or version as they may or may not adhere 100% to the International Standards or they may add functionality outside the strictures of any standards making it difficult to track and make allowances for. Unfortunately, that's the price we pay for "not" having one company exert control of the internet via “their” browser. Part of the reason for so many different browsers and constant stream of new versions is to try to be one step ahead of those individuals, companies (or nation states) bent on engaging in various nefarious schemes and to allow sites to offer ever more engaging features. It’s important to set expectations with members that using browser extensions, browsers too new or too old might not yield an “as expected” experience on your site. “If” problems are encountered, proper troubleshooting and documentation from members is an absolute necessity in order for IPS to determine if “their” code could be improved upon to play well with that particular browser. @Jim M It might be helpful if IPS provided a troubleshooting matrix we could forward to users to garner requisite details required for a truly actionable trouble-ticket submission.

As there isn't a support topic for Members Shop Clubs Add-On I will post a request here: Please add support to "Charge users to create a blog module in their club" & "Charge users to create a babble module in their club" if installed. Thanks...

I'm all in favor of augmenting the functionality of the Commerce app but its unlikely all of the functionality that would be needed to create a robust delivery app isn't likely in the cards. As there are a multitude of delivery apps already available why not use one of them and simply embed that website page into the IPS suite? There are a multitude of different ways that could be accomplished.

Here is a better example of nested menus I mentioned above. Would it be possible to be able to do the same thing for "Images", "Blog", "Events" and "Files" as well with the ability to reorder each menu?

Further development of the Invision App has been placed on hold by IPS.

You mean a cup of tea followed by a Fifth of Whisky as a chaser to forget the fact we have yet another dot release followed by another to contend with...

This developer has left the marketplace.

Could you please let me know how to change the following menu item:

IPS tends to change policies around the Marketplace with little notice or transparency to the customer base, as such, it's anyone's guess how a customer might best proceed in sponsoring the recreation of an abandoned app and know it will readily be accepted into the marketplace. It's been quite some time since@Mattoffered to address the issue with his team. Unfortunately no definitive response has been proffered after some 5 months. Developers will come and go, probably more so with the uncertainties of a global pandemic that doesn't seem to be going away anytime soon. Some apps become integral to a site and continious development and support are important to their remaining online.