Ibai

Note: There is a character limit for the short name field, but I'm finding inconsistent information on exactly what that number is because it can be different for Chrome or iOS, but err on the side of shorter.
That said, Cheers & Gears does just barely fit... so for iOS, that limit might be ~14

To recap:
To enable push notifications on iOS:
Ensure you are using iOS 16.4 or newer Save the site to your iPhone's home screen via the share icon Enable push notifications via the option at the bottom of the notifications options page Ensure you have set some notifications to "+ Push" Make sure you haven't disabled notifications via iOS Settings globally or for the app icon if you scroll down the settings list in iOS.

Open the PWA...  the bell appears when you click the hamburger menu.

Click that bell, and then "Notification Settings".  
Make sure push notifications are enabled.  (You need to do this per device.)

Finally make sure you have specific notifications set for what you want pushed.  

I've actually re-enabled a lot of notifications and moved them exclusively to my phone now. I find myself coming back more when I'm out and about.

It has moved to System -> Web App.
IPS should probably change the ACP search. Searching for “manifest” still points to Icons & Logos, where it has been removed from. 

Have you tried using 'standalone' as the UI type?

No, it's not cloud only.
You need to first add the website to your home screen for push notifications to be allowed.
It seems to be a webkit bug where the notification will only go to the correct URL if the web app is already open and in memory.

UI and UX is probably one of the most important things out there so I'd have to strongly agree to see if we can find a way to get prompts on screen to help the user 'download the app' to their Apps screens. Otherwise Apple users won't know the feature exists.
I'll still be pushing it hard for our members as we've been waiting for a way to get push notifications out to Apple users, luckily I have quite a few members on WhatsApp so I can persuade them via that 😅

Would it be possible to have a notification in mobile safari telling folks they can save the site to their home screen for a better user experience? I think most folks won't know that they can save the page to their home screen to have an app experience.
Example like what a real app does.

 
 

That's the actual footage of me after the first successful push notification. And Stu was such a party crasher with his "welcome to 2018... I have them already working for years" comment:D 

Huge thanks to @Daniel F for risking his iPhone by installing the latest iOS beta to get this feature working for us!

The longest awaited iPhone feature is almost here, native iOS notifications, and we couldn't wait to ensure it is enabled for your Invision Community.
Invision Community 4.7.9 is iPhone push notification ready for when Apple release their latest iOS update later this month. This means you'll finally get notifications on your phone, even when you do not have your browser open, to alert you of new content on followed items and more. A feature Android owners have enjoyed for a while.

With notifications, you can have an authentic native app experience with built-in Invision Community features such as the manifest editor.
The manifest editor allows you to edit your theme icons, colours and URL for when your members add your community to their phone's homepage. This manifest file helps mobile devices understand how to display your community site when launched from the home screen.

Your members can add your community to their home screen with the share button. Once it has been added, it looks and feels like a native app downloaded from the App Store.
With Apple finally allowing native notifications and Invision Community's mobile-ready UI coupled with the manifest editor, you can have a real app experience without needing a mobile app.
iPhone PWA.mp4
We intend to bring more functionality and ease of use to mobile devices over the coming releases.
We hope you're looking forward to iOS native push notifications as much as we are!
The features discussed in this announcement are available in both Invision Community and Invision Community Classic.

View full blog entry

Hi IPS,
Can you implement a mechanism that would periodically check if emails the accounts are registered on still exist, are still valid or not blocked? Would be great to reduce a bounce back rate. Such user would be marked automatically by notifications system and bulk mail system as "DO NTO SEND".

Hi,
Another thing I always change in every template I customize is the size of the reaction icons. This is sth suggested and reported by PageSpeedTest.
You can find in reactionOverview template bit, for instance:
<img src='{$reaction->_icon->url}' alt="{lang="reaction_title_{$reaction->id}" escape="true"}" loading="lazy"> I always change for the folloging
<img src='{$reaction->_icon->url}' alt="{lang="reaction_title_{$reaction->id}" escape="true"}" loading="lazy" width="28" height="28"> There is another template bit to change: searchReaction.
Any chances to have this as standard? Do you think it's a good idea?
Cheers,
Ibai

I personally liked it better with the comments below the blog article, like you expect in most blogs. 
At least put a link at the bottom of the blog post to the corresponding forum topic? 

Thanks for your feedback @Ibai. The next major version of Invision Community will be focusing on performance improvements such as this (adding width/height attributes, using native lazy loading, etc). We don't have any information to share yet, but things like this will be implemented by default in the future 🙂
 
The width and height tags only support numerical values. Adding units will make them invalid. Instead, you should simply use width="24" height="24"

Hi there,
From the beginning, I always see a tiny glitch when browsing downloads or articles list. When the text of these items is very long, the "$file->truncated()" function seems that is not working very well, and loads the raw text (without HTML tags) and then, the frontend does the truncation.
What happens is that there is usually a glitch: while all the content is loading, until the "on.load" event, the text loaded is VERY long and eventually, this "onload" is fired and it is truncated.
In addition, this makes the site to download a very big HTML that afterwards is cut.
We could optimize this load, using a real truncation function.
I always change that function to sth like this:
<div class='ipsType_richText ipsType_break ipsMargin_bottom:half' data-ipsTruncate data-ipsTruncate-type="remove" data-ipsTruncate-size="2 lines"> {{$num_char_total=strlen($file->truncated());}} {{$real_truncated_text=($num_char_total<400)?$file->truncated():substr($file->truncated(),0,strpos($file->truncated(), ' ', min(400,$num_char_total)));//el strpos es un truco para ir por palabras, cogemos la posicion del primer espacio tras 400 caracteres}} {$real_truncated_text|raw} </div> As you can see, I always try to cut the original raw text to 400 chars (avoiding to cut a word in the middle).
Do you think this would be a good idea to have it as standard?
Cheers,
Ibai

Hi,
Another thing I always change in every template I customize is the size of the reaction icons. This is sth suggested and reported by PageSpeedTest.
You can find in reactionOverview template bit, for instance:
<img src='{$reaction->_icon->url}' alt="{lang="reaction_title_{$reaction->id}" escape="true"}" loading="lazy"> I always change for the folloging
<img src='{$reaction->_icon->url}' alt="{lang="reaction_title_{$reaction->id}" escape="true"}" loading="lazy" width="28" height="28"> There is another template bit to change: searchReaction.
Any chances to have this as standard? Do you think it's a good idea?
Cheers,
Ibai

1. Loading = lazy makes loading icons delay, but does not onload them after loading the page, data-src should be added
2. Actual size of icons is 24 x 24, so this size should be specified in link
3. For responsive rendering, you should also add, for example, class=react, respectively, add the necessary in the custom css, and neutralize the original max sizes from the framework css.
4. Link should be edited in templates reactionBlurb and reactionOverview
I use this:
Link edited
<img class="react" src='{expression="\IPS\Text\Parser::blankImage()"}' data-src='{$reaction->_icon->url}' alt='{lang="reaction_title_{$reaction->id}" escape="true"}' width="24px" height="24px" loading="lazy"> Custom css
.react{width:28px;height:28px} .ipsReact_reactCount img {max-width: 28px;max-height: 28px;} @media screen and (max-width: 767px) { .react{width:20px;height:20px} }  

Hi,
Another thing I always change in every template I customize is the size of the reaction icons. This is sth suggested and reported by PageSpeedTest.
You can find in reactionOverview template bit, for instance:
<img src='{$reaction->_icon->url}' alt="{lang="reaction_title_{$reaction->id}" escape="true"}" loading="lazy"> I always change for the folloging
<img src='{$reaction->_icon->url}' alt="{lang="reaction_title_{$reaction->id}" escape="true"}" loading="lazy" width="28" height="28"> There is another template bit to change: searchReaction.
Any chances to have this as standard? Do you think it's a good idea?
Cheers,
Ibai

It was fixed by our theme designer, thanks.

Wow... what a work!
I found in this community another member experiencing same issue... It was Theme related...
I created a new theme and the website came back... Still, I don't know what happened. I've performed all the changes comparing both templates and I have my website back. Seems the theme became corrupted, because ALL the changes I had in my previous theme are working...

Glad you got it squared away. TYPICALLY if you see session issues, it’s a hosting problem. 🙂 

Thanks, I have fixed this for an upcoming release.

I missed this topic, but completely agree after being advised it’s not possible to achieve this in the Downloads app.
It’s pretty silly to be honest if clients have waited such a long time for this basic functionality that is present in other areas of IPS and configured this way for the Marketplace here.
Honestly what’s the point of having a totally empty parent category that misleads users into missing the content inside the subcategories.