Thomas P

Why next year. Can you tell apple we need it next week.

It seems it’s going to happen “soon”😍
 
https://www.apple.com/ios/ios-16-preview/features/

Personally while it may be an issue, it’s not a critical one and anywhere near the top of the list of things that are important to fix. 

If this really is important to you, make your voice heard to the group that is actually writing it. While IPB can make a post asking for it, if tons of other people do it as well, it’s more likely to happen. Just like y’all are trying to say here. 😉
This has existed since 2020 for jQuery which has a MUUUUCH bigger user base than even all of IPS.  People are obviously not clamoring to them to fix it. So it needs more attention. 🙂 

I have been meaning to post this for a couple of years now.
Can we stop the ability to embed Twitter account feeds? Normally you would post the url of a Tweet and it embeds. However if you post the url of a Twitter user's account, it will embed a litany of their posts. This is far from ideal. At the very least, please create an ACP setting to turn this functionality off while still embedding individual Tweets. I don't want my users to have this ability and it just creates clutter in my opinion. Not to mention it continually updates.
An example of a Twitter user's url embedding:
 

I like it the way it is. It provides context which is great for SEO and people’s understanding of the content. Take this Google search result from one of my sites:

The title “LUBR” wouldn’t make any sense at all. But the forum title makes it clear that this is a font identification request in relation to “LUBR” and the site title makes it clear that this is a search result from a typography website. And if you know that site already, seeing that brand in the title will increase the chance of clicking that link. Everything works together perfectly. 
Sure, the title can get long this way and might be cut off, but I would still say that overall, the benefits outweigh potential downsides. 
 

I believe we're using 1.2 right now. Any release should theoretically work whilst they maintain API compatibility.

Yes, we tested Open Search (this community is using Open Search right now). As @13. notes, it currently uses the same API requests and returns the responses in the same format as Elastic Search.
I think in the future you may see Open Search become the preferred implementation (in general) due to the ES licensing changes.

Any of the 7.x versions should be okay. 8.x wasn't released when we last did an update and I haven't personally tested it to know if it contains any backward incompatibilities.

ACP > System > Site Features > Integrations
Choose IndexNow.  It's either on or off.  Once enabled, there is nothing else to configure.  The rest happens automatically in the background.  

It’s working if you don’t see any errors in the system log. 

I just replied back to your pm.

You got PN.
I tried to enter the names with comma without and with spaces in between.
Thanks

Hello Marc,
thank you for clarifying. 
Yes, it worked out without any issues.

Regards

Completely understand there, and if its something which is stopping you upgrading we would of course take a look beforehand. When its something like that which is not really causing you any issues, we would generally ask you to update first of all. Glad to see you are now there though 🙂 

Why would our clubs feature not work for you? 
What’s missing there compared to the app ? 

I have not seen any reports of this. You can indeed just create a new langauge pack in the admin CP if needed, which Would indeed create a new stock language pack.
If of course you have any issues once you update your live site, just let us know and we can take a look. 

I personally didn't get any errors when upgrading. But based on previous experience with upgrading errors, I just manually downloaded the entire IPS files, uploaded them via FTP, and re-installed the upgrade to get it to work.
And if all else fails, restore the site from a backup.
As far as the default language, you can always make a new English (USA) and delete your old English (USA)... but I did that once and ended up having to translate my entire site to English because the forums, terms, titles, etc. pretty much everything that was in English attached to that language pack that got messed up. 😬

PHP 8.1 is still not officially supported. You can check when we do release official support in our Release Notes.

At this time, we have not fully claimed support for 8.1. Testing is still something which we have on our to-do list.

"Sorry, we can't show this content because you do not have permission to see it."

There are also some 3rd-party apps that force MyISAM, even if your database uses InnoDB by default. You have to determine what tables are not InnoDB. Then you know more.

Appears to be resolved after redownloading and wiping files again today. Thanks!

Thanks, we have already a bug report for this:) 

Some are not parsed in 4.6.10 Beta 2

 

There's currently no option to set icons being maskable or not.
And IPB, by default doesn't set the maskable attribute.

Google Lighthouse Audit as such doesn't rate the PWA setup as optimized.

Would be great to either set it by default in the manifest file, or add an option for us to set the maskable attritbute ourselfs.

https://web.dev/maskable-icon-audit/?utm_source=lighthouse&utm_medium=devtools
 
Of course, this isn't just about Google Lighthouse Rating improvement, but it also allows us to mask the icon 😉