Hisashi

I believe that was exactly what users wanted. I understand that you warned in a topic, but this alert was missing right at the moment of the user updating the system, visible there just in time for him to read and be aware. Great job!
To reinforce the message you want to get across to clients, something like this could be done (just a suggestion)

I believe that was exactly what users wanted. I understand that you warned in a topic, but this alert was missing right at the moment of the user updating the system, visible there just in time for him to read and be aware. Great job!
To reinforce the message you want to get across to clients, something like this could be done (just a suggestion)

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.

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.

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.

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.

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.

The devil is in the detail, as is said.  The detail, however was assumed that everyone was on board and up-to-date.  I would still have liked to have seen a warning about third party apps possibly being locked 'before' the upgrade began.  It does this with themes where you either proceed or cancel the upgrade.  Running a scan after the fact is assuming a lot from people.
I agree wholeheartedly that if your site is mission critical then you should test 'every' update, not just this one, before proceeding to save yourself a lot of heartache.
As far as information, blogs, etc, not everyone reads them, especially if they are aimed at devs.  Even a post telling people be warned that some/all of your apps will be locked, so check with the devs to make sure they are up-to-date.
I would even go as far as flagging all apps in the marketplace to show that they are compatible with 4.7.2 because the 4.7 compatible flag may not always be correct, as witness in my own case where the apps are still purchasable, but will not work in 4.7.2 at this point in time. 
There's a lot more that could have been done to inform people of the pitfalls in an unmistakeable way - a pre-upgrade warning would have put me off upgrading until I was sure that everything would work, I never dreamed that some of the apps I use would be locked.
There are plusses and minuses in all of this; the good, the bad and the ugly if you wish lol.
As I mentioned it's no big deal to me, because I'm just a hobbyist, but someone else may have an even bigger headache to contend with.  Fair play to IPS for moving things forward and creating a great environment for us all to play and work with, but information is thin on the ground and I believe that is the one weakness that needs addressing 🙂
 

One more thing. A quick shout out to @Adriano Faria who first thing this morning, and I mean first thing, was hammering out update notices on all of his apps. He's the only one that I've seen all day. I hope they all get approved quickly, but kudos for the immediate intervention. I hope that the other devs are also pushing updates, especially on the big apps that so many of us use!

Really, it looks like the problem has been fixed in 4.7.2.
My community is running 4.7.1

I am not able to replicate this issue on the latest beta. Please let us know if you still have this issue after 4.7.2, please let us know and we would need to investigate further on your instance

Hello,
Many users end up reporting things in imprecise, where moderators have to guess what it is specifically about. There could be an option where administrators could create pre-definitions of reports, as if it were a department.
Example...

Twitter

Youtube

I will update it.

Is there a problem in marketplace? The search is not returning any results.
 

Time to expand out the testing (thanks to @MythonPonty for assistance so far)
Note the following:
1. Testing will be done on my own test site, not your own site.
2. I have a specific set of tests I would like performed, and instructions will be provided on the test site - if they aren't followed then you will lose access to do the testing.
3. If interested, send me a PM.
4. Sending a PM doesn't guarantee that you will be used as a tester.

Hello,
I'm starting to get used to the simplicity of the new search bar, but there's one thing that bothers me, although it's not a problem.
Desktop users are having a bit of a hard time searching because they aren't paying attention when selecting the location of content.

 
They end up not having a good search experience, due to a simple lack of attention. And it gets worse when your theme is dark.

Sometimes the user is looking for a video, but is in another app and ends up being filtered automatically.

 
How to solve this?
Make the menu appear automatically when clicking on search bar, as it was in past.
So the user will quickly know where to look for your content.

Not a huge deal, but still confusing:
This option in the Database Filter Widget to only show my own records …

is very useful, but pointless and confusing if the database is set to only show my own records. 

I suggest, the filter widget checks that settings and suppresses the choice to only show my own files. 

INCREDIBLE!! Worked perfectly.

INCREDIBLE!! Worked perfectly.

Untested in Pages...
{{if $formValue}} <div class="ipsGrid ipsGrid_collapsePhone ipsType_center"> {{$test = 0;}} {{foreach $value as $file}} <img data-src="{file='$file' extension='cms_Records'}" loading="lazy" class="ipsImage ImgMargem" alt="{$record->_title} by {$record->customFieldDisplayByKey('artista_manga', 'raw')}"><br> {{$test++;}} {{if $test % 5 == 0}} <YOUR AD STUFF> {{endif}} {{endforeach}} </div> {{endif}}  

5 minutes is sufficient for most community tasks.

Suggestion
I was thinking of an option so that admins can try to catch new users or sell a subscription when tries to click through to a server. The following idea came to me... 
Instead of hiding the server, display a message.
 



 

I added it to the purchase list, impressive how they haven't added it yet.
What an excellent observation in this comment.