Kenneth Baker

But as MediaDiGi wrote, from the way the current design of the Providers Directory looks like the only way for us to see new updates is go thru dozen of pages one by one and manually check if something new was posted
And impossible to see which are new modifications because there's no central location for that either
To me it looks like we'll have a community which almost impossible for new devs to enter the club since if its up to us only to decide who isnt suspicious then not many clients will be willing to be the first to buy something from a dev who just signed up recently

We will have to go to tons of differents platerform for keep our products purchase up to date.
Gonna be a pain to handle. Not gonna lie. 

But as MediaDiGi wrote, from the way the current design of the Providers Directory looks like the only way for us to see new updates is go thru dozen of pages one by one and manually check if something new was posted
And impossible to see which are new modifications because there's no central location for that either
To me it looks like we'll have a community which almost impossible for new devs to enter the club since if its up to us only to decide who isnt suspicious then not many clients will be willing to be the first to buy something from a dev who just signed up recently

No, your ACP is going to show the same notification and badge as you see now if they implement their own version check. 

But as MediaDiGi wrote, from the way the current design of the Providers Directory looks like the only way for us to see new updates is go thru dozen of pages one by one and manually check if something new was posted
And impossible to see which are new modifications because there's no central location for that either
To me it looks like we'll have a community which almost impossible for new devs to enter the club since if its up to us only to decide who isnt suspicious then not many clients will be willing to be the first to buy something from a dev who just signed up recently

I just checked the marketplace stats, and with 59 mods purchased to date, I think I can have a word about this decision:
For me, the marketplace was a great way to:
See what new addons have been released and decide if I should install them on the community I manage. Keep up with the updates and install when one is available. These things will no longer be possible without the marketplace, and I will have to check ten different dev sites, install updates manually, etc.  A major drawback for me.
I don't have access to financials, but from your latest actions, I see that you want to focus on the enterprise customers that take a cloud-managed plan because that's where the money is. And also, enterprise customers only install a few add-ons. 
 

I would have hoped for a 6 month notice period to be honest not 2 1/2 months.
Considering we cant download addons any more other than through admincp we cant even back up for a wayward plugin dev who is sick or unable to handle the change in 2 months.
Please at least let us download what we own to self install for now.

The problem is, without the current IPS scan/approval process of apps/plugins, any new development is a risk.  We also don't know how many iterations of scan/approval a given version of a given app had to go through to get final IPS approval, nor what those rulesets/barriers were for good practice per IPS standards.  We just know the end product from the Marketplace dev.  Now clients are subject to the intermediate iterations and any issues they expose.  This is particularly concerning when we get into PII and any level of security risk to our sites (which we had a confidence level IPS was protecting us from with their scan/approval process).

Ahhh  okay, got it, thanks

It’s a category permission (matrix). In your categories listing, click in the padlock and enable COMMENTS and REVIEWS for the groups you want.

If you created a new key, there is a rate limiting unless you have had the new key approved by giphy for production use. 

https://www.theregister.com/2023/05/23/meta_giphy_sale/ 
Interesting read. 

Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.
 

Issue solved, there's some odd issue with the custom key and the setting to switch to the public wasnt saved
thanks for the replies

I don't have access to the Blogs app and IPS don't allow developers access unless I purchase an app I wouldn't use.
But I'd probably say no unless I specifically added support for it.

Hi @Kenneth Baker,
It happens to the best of us! Please let us know if you encounter any other issues or concerns.

Anyone can create events in the application. Please ensure that your member groups have proper permissions to do so. 
 
 

Hi @Kenneth Baker,
You have indeed posted in the right section! All help and support for Invision Community is now located on this community. It provides for an easier environment to get answers to common issues that you may stumble on by using the search feature, and it gives our own community the opportunity to assist you as well.
I will get one of my colleagues to look into this for you. 🙂

Thats now sorted for you 🙂 

No problem at all, and good luck with the moves

You are checking your server is compatible with what you are upgrading to, not what you are currently on

You would need to ensure that the moderator(s) who are looking to use this have the permission to do so in ACP -> Members -> Staff -> Moderators -> edit user/group -> Content tab -> Can manage alerts?

This is not officially supported. You’re better off working with the resource author to fix the issue honestly. 

I wil NOT be available until February 04, so here goes a quick fix (FTP required) for those who are using the plugin Reactions in Private Messages 1.0.1 and have the following error:
Download and open /plugins/reactionsinprivatemessages/hooks/messageModel.php and find:
use \IPS\Content\Reactable { try { \IPS\Content\Reactable::canReact as allowedToReact; } catch ( \Error | \RuntimeException $e ) { if ( method_exists( get_parent_class(), __FUNCTION__ ) ) { return \call_user_func_array( 'parent::' . __FUNCTION__, \func_get_args() ); } else { throw $e; } } } Change it to:
use \IPS\Content\Reactable { \IPS\Content\Reactable::canReact as allowedToReact; } Save and upload.
The error is the TRY/CATCH added by the framework when exporting the plugin.
If you DO NOT have FTP access, then simply disable or uninstall the plugin. I'll take a look (with IPS) when I get back.
Thank you.

Thanks @Adriano Faria that did it 🙂