Matt

@Cobar The issue is caused by GitHub being down right now. The build process pulls from the latest tagged release, and as GitHub is currently experiencing issues, it's failing there.

Once GitHub is back up, it will work fine.

https://www.githubstatus.com

I've added the ability to upload maskable icons, and this should be in our March release (4.6.11)

Sadly the W3C validator complains about a lot of things we have to do in the real world.

The markup you are seeing is a well known workaround for limitations in how iOS manages start up images across its wide range of screen sizes and devices.

https://appsco.pe/developer/splash-screens
https://www.simicart.com/blog/pwa-splash-screen/

To change device-width to just width breaks this.

It's not something we can fix.

We have just issued a patch for this issue.

Hey Russell,
In an ideal world Facebook would have an open embed endpoint and we could use that.

Sadly they don't, so you need to set up an App at Facebook and get it through approval.

More info here: 
 

Unfortunately as this domain is in our cloud system, there isn't a static IP address assigned.

May I ask why you need to whitelist it?

I'm reviewing this for you.

I would suggest restoring the default .htaccess file which can be downloaded via ACP > Search Engine Optimisation > Friendly URLs (the link is in the description of the setting 'Rewrite URLs'.

invisioncommunity.com/ and invisioncommunity/index.php will both load without a redirect. The htaccess file looks for files that do not exist and rewrite based on that. index.php does exist, so this will not be rewritten or redirected.

https://invisioncommunity.com/forums/index.php is not a real page and there is not a friendly routing path of that specific URL. /forums/ is a "fake" directory itself.
Likewise https://invisioncommunity.com/forums/topic/index.php is not a real page and will result in an error page.

I think the software is working as expected for you.

Have you given your browsers permission to use push notifications? There is a little message at the footer of your notification settings page.

Thanks. It’s a test post in a test forum. I can fix this tomorrow.

Facebook have deprecated their original oEmbed API, and have a new oEmbed API.
The graph API calls look to be the same but the way to get permissions has moved as per the screenshot.
 

Just replied to the open ticket, but it's all fixed.

Hi,
Unfortunately, I'm not keen on adding a DISTINCT onto that query as this effectively introduces a GROUP BY onto this query which is used very often. It'll not scale well at all.

I would use a sub-query and I think this would optimised a lot better for this purpose.

Invoices are generally meant to be persistent in that they form a financial record. It's not a feature we would add.

I think if you have tags disabled, it's fine to disallow those.

Notifications, checkout, subs purchase are all fine to omit.
I'm unclear what google will index with 'index.php?*' but this is likely fine as long as you have rewritten friendly URLs on.

I'd need to audit to see what 'app=*' would disallow. Generally it should be fine but there may be some functionality that doesn't have a friendly URL.
do=download/do=email both fine to disallow. I'll tweak the robots.txt file to include some of those.

I've not used the service but I'd imagine it's as straight forward as Zapier.

They have some great documentation: https://www.integromat.com/en/help/docs#general

Invision Community 4.6 brings a brand new achievements system which overhauls the ranks system along with adding the ability to earn points which translates into a higher rank via rules.
As part of the clean-up, we removed the custom member title from the author section of the post as there's a limit to how much information we can show comfortably!
Of course, some communities used custom member titles and wish to continue using them. Fortunately it's easy enough to get them back.

Step 1: Log into the ACP and navigate to Members > Profiles > Profile Fields
Step 2: You will see a group called "Retained", inside is a new custom field called "Member Title". This profile field was used in the upgrade to save the custom member title data. Click on the pencil icon to edit.


Step 3: Post upgrade, this field is effectively switched off, but it can easily be switched back on. For the "Display format for topics" choose custom and just use: {$content} as the value. This will remove the "Member Title:" prefix. Save the changes.


You will now see the member title has been restored.


 Advanced tip:  Only do this if you are comfortable making theme edits! If it all goes wrong, don't panic. There is a revert button to undo your changes! Edit the template bit Forums > topics > postContainer in your active theme and move the block highlighted here up underneath the {{endif}} of the {{$comment->isAnonymous()}} block.

 
 

Ideally you'd not use queries like that in a template, and instead do that in a controller however life isn't always as neat so...
{{foreach( \IPS\Db::i()->select(...) ) as $row}} <strong>My name is: {$row['name']}</strong> {{endforeach}} Will do the trick.

I have removed the text so it no longer looks odd.

How are you adding this HTML to the editor? Does your member group have permission to post HTML? All posts are cleaned to remove potentially breaking elements, but this is bypassed if you have permission to post HTML.

Go and install the patch we released yesterday. There is an issue with social log in buttons when used with the quick register form.

I've filed a bug report (5226) for this, thanks!

I've filed a bug report (5225) to check into this, thanks!

That's a bug. Can you please submit a ticket so we can get that fixed? Thanks!

The patch is for Invision Community 4.5, but the underlying issue does affect 4.4.x too. There have been several security updates in the 4.5 branch, so it's worth upgrading.

How are you building this page? Are you using the uploader to upload the video files?

If so, check: ACP > Settings > Posting > General to make sure "Allowed File Types" is set correctly.

If you are using Pages, check the custom field has "Upload Type" set correctly.