SeNioR-

@annadaa I recommend to follow: Deprecation Tracker.

can you translate a bit for non-developers?
because if I understand the plugins will no longer be available as is but the applications yes
do all applications in v. 4 can be updated to v. 5?
some plugins no and others yes by becoming applications if I understand? but no real answer yet because it is under development
if I understand the advantage of this update is an ease of compatibility of applications with future updates, even large ones and months of interference between IPS and certain plugins which brought certain malfunctions

why do you underestimate the value of the market? while you do not know the future of IPS, what will be its future potential customers?
nor the number of customers developing in-house third-party applications
also see your direct competitor how being the word press community using bbPress, woo commerce, learn dash (LMS) and others, and not just professionals
you can greatly outperform them if you don't underestimate the market here
your admin panel is better and incomparable, you can manage members and groups better here, there are a lot of bugs here and third party application problems due to updates and it will be even better in the future as I understand
it is possible to do much better here and cleaner than the equivalent of the applications available at word press
the applications here are much better in options than their wordpress equivalent
you want to create an LMS then at least leave the possibility to the developers to improve it and make it better than learn dash from word press

I’ll try.
Plugins don’t. Applications will. Everything you could do with a plugin, you always could with an application because both used hooks; it was powerful and you could do basically everything. Hooks are removed in V5. It won’t be possible anymore and it’s been replaced by a hook-points system (a.k.a. Listeners) and a UIExtension, which we don’t know as they didn’t blog about it yet. It will be more limited/restricted, no doubt.  Matt said, you can do a lot, but you can’t do everything you could before. The doubt now is how much limited it is compared to hooks.
Translating to marketplace resources: my guess is that a few (compared to the totality) applications/plugins will be fully upgraded to V5. Some will be upgraded but will lost some functionalities (due to hooks it may have today) but vast majority don’t, at least in first moment; improvements will be necessary along the way.
I guess we’ll have to wait and see. Get your popcorn and have a seat. Only time will tell.
Marketplace rules will change for V5. 3rd-party devs probably will be allowed to create similar resources. 

Not every person has applications/plugins associated with the Marketplace. Many people downloaded the resource in xml/tar format and just installed it.
There are definitely more installations. IMHO.

For now.. dum dum duuuuuuuuum. We have no plans to remove it.

Not every person has applications/plugins associated with the Marketplace. Many people downloaded the resource in xml/tar format and just installed it.
There are definitely more installations. IMHO.

Controversial topic, I like it. 🫢 Adriano, good luck with the update over 300 resources 😁

Not every person has applications/plugins associated with the Marketplace. Many people downloaded the resource in xml/tar format and just installed it.
There are definitely more installations. IMHO.

Not every person has applications/plugins associated with the Marketplace. Many people downloaded the resource in xml/tar format and just installed it.
There are definitely more installations. IMHO.

Not every person has applications/plugins associated with the Marketplace. Many people downloaded the resource in xml/tar format and just installed it.
There are definitely more installations. IMHO.

I think it's because you are not interested in developing the market. I see a trend to close the community in the future in the cloud with paying customers, they are more profitable. IMHO. One of the advantages of IPS was its good extensibility and variety of applications and extensions.
 
 
 

I'll repeat what I said in my first blog:
We are being very intentional in restricting what can be changed with regards to our functionality and UI. None of this is by accident or an unintended consequence. We are providing tools to create features that side alongside our functionality, and less opportunities to replace our functionality.
We will have a better suite of development tools to enable this.
The third party developers are very important to us, but most customers choose to not use add-ons or modifications. Based on statistics we collect, the most popular plug-in on the marketplace has less than 250 current installations, and the most popular application has less than 600 installations.

So regarding this assumed 80% of plugins being lost, the main questions I have are:
Can similar results (i.e. a client wants X added/enhanced to any part of the suite) be achieved with whatever IPS is developing for v5?  Maybe in a different way, but the same end result/solution for a client? If so, will the solutions be Marketplace sellable assets for developers? If not, how does IPS plan on addressing this clear gap in providing functionality to clients that Marketplace devs previously filled in v4? I can't imagine IPS removing the ability for devs to enhance the IPS suite in ways that IPS isn't willing to invest in doing themselves.  That would be detrimental to all parties involved.  And history (per the number of Marketplace assets) shows there are A LOT of assets/resources clients want and use that aren't part of the suite.

I typed "The PHP programming language crying" into an AI image generator and all it gave me was a sullen, cosplaying Esther. BTW, next concert flyer? This.

1. You should all cool down and wait for the upcoming news and also the final product before getting in such a  panic rage.
2. Please see my reply in the SEO topic:
3. See the first point. We're listening to feedback and implementing changes based on it, just like Esther and Matt implemented changes today based on the provided feedback.
4. I think you're all way too scared.
There's still so much that can be done, it's 2023, and there are other ways and solutions than to edit files..
ALPACAS! I'll repeat very very slowly just for you: AL PA CAS

No issues there. He won't be able to upgrade 2/3 of them. Lots of time saved! 😂
 
Seriously, I have several apps and plugins extending classes in the /system folder. That means they're all dead for v5. So far, I don't like the direction v5 is taking at all. No matter what awesome tools you may have in place, being unable to overload (almost) all classes like before is a huge issue.
 
Well, that's it for me for now. I won't say anything further until there is more info about those "awesome tools" you mentioned. But I don't have much hope for them.

Maybe. Someone say yes, other no. I have plenty private custom mods (hooks) and I can take responsible and all consequences. Now it won't be possible.
~ 85-90% I think.
I prefer to wait for more dev blog entries before I'll be more critical, but I feel close to certainty that more than 80% of my projects will not be possible on v5.
 
Nope, disagree. Hooks are powerfull.

They will be there for a couple of years for those who won’t jump in V5 right away.
File edits will be back with resources being sold in dev’s board. And for those who use marketplace and can’t use FTP, will get limited resources.
But there’s no doubt it will be the end of this marketplace and I truly believe that’s what IPS is after for a while now.
I haven’t decided yet if I will keep developing for IPS, as I told somewhere else… and I must confess the answer its getting clear at every blog entry. 
Anyway, if I remain, certainly will reduce from 300 to 50 maximum, due to… framework limitations. 😂

I'm always keen to get information out as soon as we have it fixed on our end. There are pros and cons but the earlier the feedback, the more chance we have at addressing it and making sure we've not missed any angles. Give it a few months and the v5 codebase will be much stabler and we'll be more reluctant to make big changes.
Some of the tools we're still actively working on, and stuff like theme tools are only about 80% complete, so there may be some gaps between blogs but we'll post them as soon as we have them ready.
Not exactly, it's more like the JS event system, you can listen in on events and execute your code when those events are triggered.

Thank you. 👏👍
Still, remove the ability to hook is a huge step back and will make marketplace even worse and smaller but I guess that’s the point after all. A massive number of resources are dead.
We’re basically back to IP.Board 2 (file edits will be required for custom jobs as we can’t hook) and IP.Board 3 (back to hook points era). 
Anyway, just my feedback. Not trying to annoy anyone; just my honest feedback.
Tks.

That will be dealt with in UIExtensions. We're wrapping some things up on those before the blog entry, but it's coming.
We will be removing the block on base classes and you'll be able to add listeners to \IPS\Content\Item (or Comment or Review).

You'll have to manually open it with a database edit. For plugins just the 'disabled' and 'requires manual intervention' fields in the entry need adjusting (to zero); ditto for applications. You probably need to dump your datastore after making the manual edits.
Also, you are right @aXenDev, this current beta 5 still locks on upgrading. If they are making just an IN_DEV check, then yeah, it would still lock as we upgrade outside of dev mode. If IPS is actually checking for the -TESTINSTALL flag on the key, then it's just broken.
I suppose I'm lucky. Just one thing locked for me... that has been running on PHP 8 for a year. I'm more weirded out by all the log messages saying it can't parse the plugin directories as they think they are not there.
EDIT: The latter is caused by missing widget and tasks directories. They can change the log message for that to better indicate that is the problem rather than just say the plugin directory itself is the problem.

I have beta 5, but my app is still locked.

In 4.7.2 beta 4+ apps will no longer be locked disabled if you are using a development install.
Updating via uploading a new version or updating from the Marketplace should remove the lock. I will check this further to make sure it's working as expected.