Chris Anderson

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.

As there isn't any kind of consensus as to whether or not there might be any issue to arbitrarily change third-party database fields then this posting still falls under "Help & Support". "If" such consensus should occur then "our" Community Advocate@Jordan Invision or other IPS employee should be the one to move this topic to the "Feature Suggestions" forum if they think it warranted.

If there is any doubt as to whether or not changing third-party database fields to InnoDB could cause problems then the ACP warning should "only" warn the administrator of the fact that IPS suite database fields could benefit from being changed to InnoDB and NOT for any database fields created by third-party apps.

I've gone ahead and changed all of the database tables to InnoDB for all of the IPS tables but the Support tool still complains that my third-party marketplace apps are still using MyISAM. After reviewing some of these tables I see that the developers use a combination of InnoDB and MyISAM in their apps. If you choose to change over to InnoDB for the IPS Suite should one also change all of the third-party database tables for consistency? Will there be any problems created by doing so?

@Mark HI was one of the early proponents for improving the Release Notes - Invision Community. An area that could benefit from improvement is to highlight "everything" that is deprecated and to give us some advanced warning so that we can take any necessary steps to mitigate their absences. Maybe you could create an entry for "Upcoming Deprecations". You list out any that will be made in the next 4.x.x release and those that might happen further down the road.

Could the above be related to your issue?

Maybe you live an exceptionally charmed life, and the rest of us, well...don't.

When I enable PHP version 7.4.16 on my site this app works fine when I click on the following: When I enable PHP version 8.0.3 on my site this app doesn't work: If I disable app while running PHP version 8.0.3 I am able to navigate to the Profiles Screen. This seems to indicate that this app isn't fully compatible with PHP 8.0.3. I cleared the system cache after switching between PHP versions. No errors being generated in System or Error Logs. Please investigate, Thanks...

You might consider reverting back to 4.5 using the full backup you made prior to attempting to upgrade to 4.6.3 and wait for the next release. If you put in a trouble ticket tonight it might take several days before IPS staff have an opportunity to help you troubleshoot.

I was "hoping" that all of your app's functionality had been natively included by IPS and as such this app was being retired. Alas, it doesn't sound like that happened, oh well... Looking forward to your releasing a 4.6 version.

What features would be included in a 4.6 version that 4.6 doesn't provide natively?

Searching for "top" works, although it does list 260 uses of the word so it's not too helpful. Here are two I found, there may be more in the other 9 pages: