InvisionHQ

I report a bug present for months on the marketplace very annoying.
Thumbnails continue to disappear, some examples:

That was fixed quickly - thank you for great support @InvisionHQ... 👍

I report a bug present for months on the marketplace very annoying.
Thumbnails continue to disappear, some examples:

Thank you for reporting. I will get this issue passed on to our developers to take a look at

@Tripp★ fix coming later today.
 

The app is pending approval in the marketplace.
Member of the month (Pending Approval in the Marketplace) Pre-defined Topic Fields
Pokes
Quick Donate Widget (Pending Approval in the Marketplace)
Traffic Generator (I'm working on this app now)
Who We Are

The app is pending approval in the marketplace.
Member of the month (Pending Approval in the Marketplace) Pre-defined Topic Fields
Pokes
Quick Donate Widget (Pending Approval in the Marketplace)
Traffic Generator (I'm working on this app now)
Who We Are

Yes, today. You can use a free package for user and you can configure seller commissions with app settings.

@Adriano Faria its not 4.6 that is at fault per se, IPS is at some fault here due to the way they engineered how the theme hooks work, but it's the latest php 7.4 and 8.0 that is the issue.
example:
<?php class myclass { public function myfunction(){ return parent::myfunction(); } } this will error out on the new versions of 7.4 and 8.0, cause myclass isn't a child class of anything, so there is no parent to call. 
the theme hooks get eval'ed as stand alone classes, they replaced the " extends _HOOK_FILE" with "_tmp" (same with parent::hookData() gets replaced with array() ), so the class would be something like class my_theme_hook_temp {}. during the eval process, it it validating the code and that validation is failing on anything with parent::myfunction() that is being called in the code, that is why the call_user_func_array is working for toolbox, cause it passes the validation, so the template will build. 
so its not the parent::hookData() that i original thought it was, cause i just took a cursory look at the code, patched my files, it seemed to work cause my datastore wasn't cleared, but as soon as it cleared, i got that error. 
so in any template overrides you are doing, you need to wrap it with a if(\is_callable('parent::myfunction')){} and then inside the if statement, call the parent method with:
return \call_user_func_array( 'parent::' . __FUNCTION__, \func_get_args() ); like i have done in the example hook i posted a few post up. if you need further help, send me the app, and i will make the changes so you can see within your code what i'm talking about 🙂

@ErickF. It has just been sent to the marketplace for approval. Fingers crossed!

Okay after a bit more digging into the code, i see why this can happen.
it is any theme hook, that has an override for a template in it or aka "theme hook in php mode"
try{ if ( eval( "namespace IPS\\Theme;\n\n" . str_replace( array( ' extends _HOOK_CLASS_', 'parent::hookData()' ), array( '_tmp', 'array()' ), file_get_contents( $path . '/' . $data['file'] ) ) ) !== FALSE ) { $class = "IPS\\Theme\\" . $data['class'] . "_tmp"; $templateHooks = array_merge_recursive( $templateHooks, $class::hookData() ); } } catch ( \ParseError $e ) { } in php 8.0 it is now a fatal error to call a non existing parent class/method, in the latest php 7.4 it is a deprecated.
so since at this point, the hook in php mode isn't actually extending another class, it is blowing up. this is def an engineering issue on IPS side of things. so technically any theme hook in php mode, that eval and try to call a parent method that doesn't exist, will throw this fatal/warning in the current versions of php. we don't see it while IN_DEV cause templates are compiled differently there. 
i wonder now if it happens with class hooks, that get wrapped up by IPS try/catch block they place inside every method, even if the method doesn't exist in the parent.  
 

iAwards is pending approval in the marketplace.
Next apps/plugins I will update next week:
Member of the month Pre-defined Topic Fields
Pokes
Quick Donate Widget
Traffic Generator
Who We Are
For all other apps not listed here I have no intention of updating them unless requests are received.

@ErickF. It has just been sent to the marketplace for approval. Fingers crossed!

Right Now, I'm working on iAwards update.

Thank you @Matt, this will help many smaller communities to survive.
Thank you for your attention to each topic and for listening.
This is a good sign.

Thank you @Matt, this will help many smaller communities to survive.
Thank you for your attention to each topic and for listening.
This is a good sign.

I will be on holiday until next Saturday.

Thank you @Matt, this will help many smaller communities to survive.
Thank you for your attention to each topic and for listening.
This is a good sign.

Thank you @Matt, this will help many smaller communities to survive.
Thank you for your attention to each topic and for listening.
This is a good sign.

Thank you @Matt, this will help many smaller communities to survive.
Thank you for your attention to each topic and for listening.
This is a good sign.

Thank you @Matt, this will help many smaller communities to survive.
Thank you for your attention to each topic and for listening.
This is a good sign.

Thank you @Matt, this will help many smaller communities to survive.
Thank you for your attention to each topic and for listening.
This is a good sign.

I want to thank you all for your feedback. I appreciate everyone who took the time to leave their thoughts and concerns. I've read every single one and replied to almost all of them.
Firstly, I want to say that I understand that the messaging that went out ahead of this update fell short of what you deserve, and I want to apologise for that.
After spending two days reading every single post, almost all concerns fall into these three areas:
1) The future of support
I've seen many people use the phrase 'no more support', which isn't true. I know the change from ticket support to staffed community support is a significant change, but I genuinely believe that it will benefit customers. I believe that we can create a living knowledge base of solved issues just like many brands do. For example, when I have a problem with my iPhone, I google it and invariably end up with a link to a topic within their support forums with a solved answer. I don't need to raise a ticket with them and wait for a reply.
There are many "what about" concerns mixed in, and I ask you to try the new staffed community support areas and give us your feedback once you've used it regularly. We will work with you based on that feedback and make improvements where it is needed.
We have custom functionality that shows our team links to your client accounts, including license keys, etc., so we know who you are and have all your information right next to the topic. You will never need to divulge personal information, or even your site URL if you do not want to.
If your support issue is complex or needs developer intervention, with a click of a button, our technicians can convert this into a ticket for you and we will continue to resolve the issue with you in that ticket.
You will be in safe hands.
2) Price Rises
We have not raised our prices for well over a decade. We've always been reluctant to do it and held off for too long, resulting in a large jump to make up for a lost time.
We can't reduce the prices to their pre-September levels, but we will be much more mindful of price rises in the future.
3) Annual Renewals
We want to simplify billing and reduce the number of invoices we need to send, and you need to pay. An annual invoice seemed logical to achieve this.
However, you have made it clear that moving to annual renewals affects your budgeting, and we have listened to that.
We have reverted this decision and have restored 6-month renewals in your client area. This is not a temporary one-off offer; it's a permanent change.
Again, I want to thank you all for being so vocal and passionate about Invision Community. We want to keep offering you the very best community platform to help your communities succeed.

Generally speaking, after so many years I feel I can say that invision is a company that thinks well about the choices it makes. But this time, as others have already written, I am very concerned about the collapse of the Marketplace. It is quite clear to me that the new pricing policy and the type of support offered for a fee is aimed exclusively at the business sector. This means that hundreds of hobby forums will be looking for alternative software solutions and this also means less appeal for me and many other developers to develop app and plugins.
Although I don't know the reasons for a series of "blows" thrown at the customer at the same time, I find some of the choices made by Invision risky.
Even if I accept the price increase, which is something I can live with, I think it was a mistake to remove the possibility to pay every 6 months. This has disoriented customers even more, even giving a perception of a heavier increase than it really is.
Furthermore, it must be acknowledged that one of invision's greatest assets has always been its ticket support. 
In short, I'm a bit worried, I'm sure I'll be one of the last to abandon ship... I've been here for 20 years... but I confess that I've been looking for alternatives for the first time in many years.
The problem is not the price, I am more concerned about the choice to let the hobby communities go.
Unfortunately I don't think the the fresh new green buttons can turn this into good news.

Let's see, I understand that even the pandemic period is not the best but let's try to give confidence to Invision as Jordan asks. Instead I would ask invision to review at least the possibility of returning to payment every six months, not for me, but I think it would help many.