BertT

We have released a patch for 4.7.1 to workaround this issue.
To install, go to AdminCP > System > Support and click "optional patch available" in the top left block.
If you do not see this, you may already have the patch since it is included with and upgrades or downloads of the software after the date of this post.

Happy Hump Day.
Identifying what members are frequently searching for is an important job for community managers. Built directly into the statistics panel of your ACP is a section that includes the most-searched-for keywords. Understanding what people search for helps you:
Improve upon those items Create more content around the term(s) Provide further clarity for people who search for the word or phrase in the future Because of the importance of search, we made some major improvements!
You may have noticed Invision Community introduced an update to our Search Bar user interface. @AlexJ certainly did 😜.
 

 
Previously, the search bar was smaller in size and included different options that could be confusing at first glance.
We've simplified the search experience. Should the user want to drill in further, they have that option on the search results page:
 

 
Go ahead and give our new search UI a test drive. Feel free to share your findings / thoughts in the comments. 😃 🔍 
---
As always, here's a list of updates and fixes made to the platform in the last seven days.
4.7.1 Beta 2 is out now. Release notes here.

See you in the comments. 
 

When manually running the queue from the ACP, the keyLocation submitted to IndexNow uses the ACP base url.
Got errors like these:
422 invalid_url Array ( [host] => www.site.com/ [key] => 6c076eb62f3b43e8cf6c62a8d69dff7a [keyLocation] => https://www.site.com/admin/<hash>.txt [urlList] => Array ( [0] => https://www.site.com/<url> ) )  
Issue is here:
$url = \IPS\Http\Url::internal(''); $data = array( 'host' => \IPS\Http\Url::baseUrl(\IPS\Http\Url::PROTOCOL_WITHOUT ), 'key' => \IPS\Settings::i()->indexnow_key, 'keyLocation' => (string) $url->setPath( $url->data[ \IPS\Http\Url::COMPONENT_PATH ] . $this->getKeyFileName() ), 'urlList' => $urls, ); $url should specify the 'front' base
$url = \IPS\Http\Url::internal( '', 'front' );  
Error happened in 4.6, but this file is not touched in 4.7.

When IPS approve pending version. 🙂

Dont ever upgrade to *.*.0. Waite for *.*.1 😁

Stu confirmed that it will in 4.7.1 or later 

It will be included in 4.7.1 at the earliest. The issue exists in 4.6.12 and 4.7 betas.

I was having an issue with S3 not allowing me to install items through the Marketplace. I would get a "There was a problem loading this content" error. 

I believe the issue was related to my CORS config as it was resolved after including "PUT" and "POST" in AllowedMethods[]
 
[ { "AllowedHeaders": [ "*" ], "AllowedMethods": [ "HEAD", "GET", "PUT", "POST" ], "AllowedOrigins": [ "*" ], "ExposeHeaders": [], "MaxAgeSeconds": 3000 } ] Unsure if anyone else has run into this, or if this is the ideal setup for CORS, but it seems to have resolved the issue.

One more dark theme issue are answer ratings:

Thanks for the update.
However there are still some leftover issues.

In mobile view, social icons are displayed instead of hidden:
Please hide them just live in the official design.

 
Dark mode also has still several issues such as:
Topics Widget for the ipsCommentCount is invisible.

 
Manage Promoted Items Page:

 
Not all Field Labels for Pages are not optimized for dark mode.
Some are barely visible, if at all.
This is just an example of some of the listing view formats:

Date of Incident is almost invisible:


For example your Legend News uses this black label as well.
The category is almost invisible:

These are defined on Page Field Settings and can be picked as shown here:
They look fine in the dark mode of the admin panel though.

 
Also the addEventListener error  that i reported to you still perists in the plugins.js
However this time around you duplicated the warning and error with the addition of the new function, which by the way also refers to fontBtn which is for sure a copy/paste mistake.

Would be great if you could resolve these errors soon.

Agreed. We have never had so many forum issues as we're having since this upgrade to 4.6. And way too many continual patches and upgrades for issues that should never have been released. It's very disappointing and taking our volunteer Admins a lot of time wasted trying to fix things. Hoping the new update goes well, but have to wait for multiple Tech Admins to be available to do it.

No issues at all so far. 🙂

4.6.0 thru 4.6.4 no issues at all, but then I am not running all the apps, so if the issues are specific to certain apps perhaps I'm not affected.  I have a client site to update that is running an app that I am not (commerce) so I am a little hesitant to go ahead right now - maybe leave it for a week or so lol.
Luck to all who go for it and I hope you avoid any pitfalls 🙂
 

Hi, if it answers your question, I was able to upgrade from 4.6.3 to 4.6.4 correctly this time via the internal upgrade facility. First time that's worked on 4.6 for me.
All the bugs are still present though, 4.6 should still be in beta testing IMHO.
I still have a locked task coming back to haunt me every time I unlock it from 4.5.4.2 for RSS imports, even though I deleted the actual feed import back in 4.5.4.2!


Uploading 1920x1080 photos into the Gallery, is buggy as hell, a truly horrendous experience. I have plenty of spare RAM available, 40 cores on a 6GB VPS that barely ticks over in terms of load. I'm not uploading straight to S3, and PHP settings and PHP memory all fine. I've been trying to upload 340 photos that 4.6.2 lost on S3 storage and it's taking days, because on 4.6.3 and now still on 4.6.4 it sometimes works, but mostly it fails on the progress bar at 5% when processing them, even if I do just 10 at a time.
I try again and it might work, next batch will fail 3 or 4 times times, then work again. It just suddenly aborts processing them and returns me to the Gallery, with 1 or 2 images having uploaded, which I then have to delete as they are not in the order intended, not that Gallery can sort them correctly anyway. It's agony.
If I try more 20 at a time, I risk more time consuming failures but also I suddenly get dozens of pop up error modals, one for each image I think, and have to abandon the tab:

 
Honestly, it feels like when you start using it for more than half an hour, barely anything seems to work reliably. I've never known a release like 4.6, aside maybe perhaps the original v4 release, maybe.
I honestly wish BFarber was still at IPS, because he would have been all over this before this unstable release got out of the door.

This is one of the issues that will be fix in 1.0.1 👍

When will 4.7 release?

 
Serious well deserved applause to the entire team!

Hi.
The minimum requirements are included in the ips4.php file (Invision Community Requirements Checker) and in requirements
Minimum
PHP 7.2.0 MySQL: 5..5.3 Recommended
PHP 7.4.0 MySQL: 5.6.2

HI,
please submit a ticket and we'll take care of this.

They were not approved because they didn't follow the marketplace guidelines  (The last submission was still altering IPS core database tables)

The issue is resolved