Luke Z

We will miss you, marketplace 😢

That’s the goal. 

Hi
Just discover this
sounds weird to me, App store, Google play store, Wordpress plugins depository, it makes sense to find all apps / plugins at the same place, rather than to have to check all devs websites...
i am not sure that's a good move

Indeed, I've used that strategy myself in the past. Also doing things like reducing what they can post as new members can be helpful

It is indeed on the hCAPTCHA site itself you are looking.
You could certainly do that if needed. For example adding *.gmail.com would ban anyone with a gmail.com email. It would probably be worth doing the hCAPTCHA settings first and  then monitor first

One of my sites has been getting hit hard over the past few hours.
I created a starter group where their first five posts have to be approved by an admin. It's a little work, but better than cleaning up spam messages. After 5 approved messages the person is promoted to the regular member group without any need to approve messages.

Quite simply they are manually registering and not known spammers (even to hCaptcha it seems). We are seeing a substantial uptick lately in spammers at present. Bear in mind the spam defence service can only flag as a known spammer, if indeed there is something on that account to show it as being known.

My websites 'Classifieds' is totally down, despite buying the one made by 'InvisionHQ'. Why wouldn't there be an immediate compatibility with the latest PHP update if this Classified system is run by Invision itself? 

let me take a look at your install!
 
 
Edit:
The patch was available, but not applied!

 
I'll just finish this step for you:) 

Done @Luke Z

What I see here, that clients are outraged by the company's lack of transparency in relation to aggressive blocking of their apps/plugins, they should have had a warning before proceeding with the update, that's what everyone is commenting on.
Many users are dependent on third-party apps to make their community what it is today, and that has become a big issue now.
Honestly, after all these reports, I'm zero excited to update my community now, I'll wait for all this puera to subside.
Good luck to the team in having to deal with this whole complaint, something that could have been avoided.

Not sure if you notified all the third party devs but if they had been they would not be scrambling at the last minute. In a perfect world, for such a major shift, you'd think that third party developers would have upgraded their apps BEFORE 4.7.2 was released.
Not looking for an answer or explanation inasmuch as what's done is done, but it would have been smoother.

That is the issue @Matt these apps 'are' 4.7 compatible and they are in the marketplace.  I've received a reply from the author who has provided replacement files and the support page now shows no errors at all, but the app is still locked.
 
 
 

I've contacted the author, but my issue is not with something that needs to be corrected, rather it is that this information was provided 'after the upgrade' had that warning appeared prior then I would have contacted the author and waited for a solution before updating.  I'm now at the mercy of the app provided to discover the issue, correct it/them and provide and update to the marketplace where it will be queued for approval.  
I'm wondering how many apps will fall under this lock out as the apps are still available in the marketplace and they can still be installed from the ACP.  There should have been a warning prior to upgrade to prevent clients sites from being rendered inoperable.

I am seeing this issue as well, when members try and log in they get that error. The user sees error code EX0. 
Here's the code from the system log:
Error: Property access is not allowed yet (0)
#0 /var/www/html/107016/applications/core/modules/front/members/profile.php(253): IPS\Content\Search\Mysql\_Query->search()
#1 /var/www/html/107016/system/Dispatcher/Controller.php(118): IPS\core\modules\front\members\_profile->manage()
#2 /var/www/html/107016/applications/core/modules/front/members/profile.php(81): IPS\Dispatcher\_Controller->execute()
#3 /var/www/html/107016/system/Dispatcher/Dispatcher.php(153): IPS\core\modules\front\members\_profile->execute()
#4 /var/www/html/107016/index.php(13): IPS\_Dispatcher->run()
#5 {main}

Still seeing the problem.  Somewhat of a relief to hear it’s not just my community.
 
dB

We are getting the same error. I'm not seeing any patches to apply. Please help. Thanks!
Error: Property access is not allowed yet (0)
#0 /var/www/html/107016/applications/core/modules/front/discover/streams.php(408): IPS\Content\Search\Mysql\_Query->search(NULL, NULL, 17)
#1 /var/www/html/107016/system/Dispatcher/Controller.php(118): IPS\core\modules\front\discover\_streams->manage()
#2 /var/www/html/107016/applications/core/modules/front/discover/streams.php(65): IPS\Dispatcher\_Controller->execute()
#3 /var/www/html/107016/system/Dispatcher/Dispatcher.php(153): IPS\core\modules\front\discover\_streams->execute()
#4 /var/www/html/107016/index.php(13): IPS\_Dispatcher->run()
#5 {main}

Since, i'm not sure? Maybe the last update? Clear system cache didn't help.
 
Error: Property access is not allowed yet (0)
#0 /var/www/html/107016/applications/core/modules/front/discover/streams.php(408): IPS\Content\Search\Mysql\_Query->search(NULL, NULL, 17)
#1 /var/www/html/107016/system/Dispatcher/Controller.php(118): IPS\core\modules\front\discover\_streams->manage()
#2 /var/www/html/107016/applications/core/modules/front/discover/streams.php(65): IPS\Dispatcher\_Controller->execute()
#3 /var/www/html/107016/system/Dispatcher/Dispatcher.php(153): IPS\core\modules\front\discover\_streams->execute()
#4 /var/www/html/107016/index.php(13): IPS\_Dispatcher->run()
#5 {main}
 
Message Count Error: Property access is not allowed yet (0) #0 /var/www/html/107016/applications/core/modules/front/discover/streams.php(408): IPS\Content\Search\Mysql\_Query->search(NULL, NULL, 17) #1 /var/www/html/107016/system/Dispatcher/Controller.php(118): IPS\core\modules\front\discover\_streams->manage() #2 /var/www/html/107016/applications/core/modules/front/discover/streams.php(65): IPS\Dispatcher\_Controller->execute() #3 /var/www/html/107016/system/Dispatcher/Dispatcher.php(153): IPS\core\modules\front\discover\_streams->execute() #4 /var/www/html/107016/index.php(13): IPS\_Dispatcher->run() #5 {main} 27 Error: Property access is not allowed yet (0) #0 /var/www/html/107016/applications/core/modules/front/discover/streams.php(408): IPS\Content\Search\Mysql\_Query->search(NULL, NULL, 1) #1 /var/www/html/107016/system/Dispatcher/Controller.php(118): IPS\core\modules\front\discover\_streams->manage() #2 /var/www/html/107016/applications/core/modules/front/discover/streams.php(65): IPS\Dispatcher\_Controller->execute() #3 /var/www/html/107016/system/Dispatcher/Dispatcher.php(153): IPS\core\modules\front\discover\_streams->execute() #4 /var/www/html/107016/index.php(13): IPS\_Dispatcher->run() #5 {main} 14

I am seeing this issue as well, when members try and log in they get that error. The user sees error code EX0. 
Here's the code from the system log:
Error: Property access is not allowed yet (0)
#0 /var/www/html/107016/applications/core/modules/front/members/profile.php(253): IPS\Content\Search\Mysql\_Query->search()
#1 /var/www/html/107016/system/Dispatcher/Controller.php(118): IPS\core\modules\front\members\_profile->manage()
#2 /var/www/html/107016/applications/core/modules/front/members/profile.php(81): IPS\Dispatcher\_Controller->execute()
#3 /var/www/html/107016/system/Dispatcher/Dispatcher.php(153): IPS\core\modules\front\members\_profile->execute()
#4 /var/www/html/107016/index.php(13): IPS\_Dispatcher->run()
#5 {main}

Just started up a new forum and want to have posts be featured without me having to manually do it from the 'Moderation Action' dropdown. Is there a setting that would allow me to have a post hit featured status based off metric(s)?