sound

All seems very unwieldy this messing about with numbers
Would it not be quicker/effective if you as an admin just simply sent them a link to the comment/post, rather than asking an average forum user to scan thru what could be up to say 50 posts, looking for what may be an unconnected number, say 23781896.
What happens when there's more than one page of topics, and how easy would it be finding this number on mobile/tablets.
All a bit unwieldy to me, and so the return of this feature is not really something that I would like to see invision deploy development resources on, maybe better suited for a plug-in request?
 
 
 
 
 
 
 
 
 

All seems very unwieldy this messing about with numbers
Would it not be quicker/effective if you as an admin just simply sent them a link to the comment/post, rather than asking an average forum user to scan thru what could be up to say 50 posts, looking for what may be an unconnected number, say 23781896.
What happens when there's more than one page of topics, and how easy would it be finding this number on mobile/tablets.
All a bit unwieldy to me, and so the return of this feature is not really something that I would like to see invision deploy development resources on, maybe better suited for a plug-in request?
 
 
 
 
 
 
 
 
 

Just updated to 4.5.2. Login is still not possible. The error as quoted above. 😥

You're absolutely right! I will find a way to show the "mark" when viewing the topic, hopefully with a customisable location.

I don't believe this is accessible in the ACP, yet after making backups of your backups and running this entirely at your own risk, you could use something like the following SQL query to return the results you're looking for:
SELECT substring_index(clm.`login_classname`,'\\', -1) AS LoginMethod ,count(1) AS NumberOfMembersLinked FROM `core_login_links` cll INNER JOIN `core_login_methods` clm ON clm.`login_id` = cll.`token_login_method` WHERE cll.`token_linked` = 1 /* Only those who have successfully linked */ GROUP BY substring_index(clm.`login_classname`,'\\', -1)  

have we a date for 4.5 compatibility release yet?

We may add an API to add support for Unsplash but haven't yet.

Just checking in for a 4.5 update also. Looking forward to it so we can upgrade. 🙂

have we a date for 4.5 compatibility release yet?

spotify are aware
https://community.spotify.com/t5/Spotify-for-Developers/Playlist-oembed-down-or-changed/td-p/4949867

What's New in Version 1.0.2  
added two options: clean all private messages started by deleted members (with ID: 0), clean all replies in private messages added by deleted members (with ID: 0)  
@jesuralem, @sound

I'll check it and if there will be possibility to make that then I'll add it.

as said the playlists not working appears to be a spotify issue - their own embed playlist links ain't working, so seems just  a wait out till they (spotify) fix that one

had the same problem
none of the fixes given worked for me
resolved it myself as per the below
of course this may not work for anyone else and you do need to know what you are doing editing wise
and it only works for artist and songs for me not playlists - which appears to be a spotify issue
but if desperate and can't wait for 4.5 ....
 

had the same problem
none of the fixes given worked for me
resolved it myself as per the below
of course this may not work for anyone else and you do need to know what you are doing editing wise
and it only works for artist and songs for me not playlists - which appears to be a spotify issue
but if desperate and can't wait for 4.5 ....
 

Noted and will be added. Perhaps not the IPB 4.5 update but the very next one.

is it possible for this to be made a setting - as it's amongst the the first template edits I do when upgrading 

There seems to be an issue with the forum topic posts in the latest release
In the topic post all the links now go through the newsletter app rather than directly to the topic url, as in  the url in the topic now contains the below
/?do=click&key=*|unsubscribe_key|*&issue=*|issue_id|*&src= causing a fail with the below reported...

Error code: EX1366
This error was probably caused by application Newsletters.
If the issue persists, disable it and contact the author for further assistance.
 
the email newsletter appears to be working ok
 
 

doesn't google not treat all your comment links as redirected links?
eg the below submitted link
 
https://www.celiac.com/articles.html/celiac-disease-amp-related-diseases-and-disorders/fibromyalgia-and-celiac-disease /fibromyalgia-and-celiac-disease-by-ronald-hoggan-r117/?do=findComment&comment=1&d=2&tab=comments actually redirects to a different url

on my site any url with  'findcomment'  is not indexed by google and is classed by a google as a 'Page with redirect' and  given the 'Status: Excluded'
 

I have written a lot about this subject, incl. and i have a design to use the critical CSS to remove the Render-blocking CSS. Yes, it works, but it takes a lot of time to analyze and develop a good critical CSS.
For a few days I've been exploring another idea that came to my mind.
Code in IncludeCSS works perfectly and this code tells the browser - download all those CSS and use them to represent the site. But this code does not tell the browser when and how to use them.
The idea I'm using right now is - I created a new template that I put before closing the tag head. In my experiment, this template looks like this:
{template="preload_css" app="core" location="global" group="analysis" params=""} In this template I placed this code
{{foreach array_unique( \IPS\Output::i()->cssFiles, SORT_STRING ) as $file}} <link rel='preload' href='{expression="\IPS\Http\Url::external( $file )->setQueryString( 'v', \IPS\CACHEBUST_KEY )"}' as="style"> {{endforeach}} {{$customCss = \IPS\Theme::i()->css( 'custom.css', 'core', 'front' );}} {{foreach $customCss as $css}} <link rel='preload' href='{expression="\IPS\Http\Url::external( $css )->setQueryString( 'v', \IPS\CACHEBUST_KEY )"}' as="style"> {{endforeach}} Now, besides a browser command to download all CSS, I send the browser a command - use these CSS as a matter of priority.
And the result of over 100 my tests - no render-blocking CSS ...
There are no side effects or any other bad impact.
I've installed it on my live site and it works perfectly.
If a development team wishes, let him test it and apply it in later releases. This will speed up all sites using this really good platform.

Hi Adlago
You can edit css to solve this. Search for icomoon (or woff and woff2) in CSS on your theme and add font-display: swap;   this will solve the lighthouse suggestion. 
https://css-tricks.com/almanac/properties/f/font-display/
Below an example..
@font-face { font-family: 'icomoon'; font-display: swap; src:url('{url="applications/core/interface/font/icomoon.eot?v=-29n77j" base="none" noprotocol="true"}'); src:url('{url="applications/core/interface/font/icomoon.eot?#iefix-29n77j" base="none" noprotocol="true"}') format('embedded-opentype'), url('{url="applications/core/interface/font/icomoon.woff?v=-29n77j" base="none" noprotocol="true"}') format('woff'), url('{url="applications/core/interface/font/icomoon.ttf?v=-29n77j" base="none" noprotocol="true"}') format('truetype'), url('{url="applications/core/interface/font/icomoon.svg?v=-29n77j#icomoon" base="none" noprotocol="true"}') format('svg'); font-weight: normal; font-style: normal; } [class^="icon-"], [class*=" icon-"] { font-family: 'icomoon'; font-display: swap; speak: none; font-style: normal; font-weight: normal; font-variant: normal; text-transform: none; line-height: 1;  

A new version has been uploaded to the Marketplace. It contains a fix for this issue.

Can you try re-setting your image extensions in the acp videos settings section?
Same as above. Double check there's image formats set in the acp and you can revisit the page and it's still there.

I used Sendgrid based on the recommendation of the IPS staff and because support is built into IPS. Unfortunately the price of Sendgrid is 10x that of Amazon's SES simple email service. 
I just switched over to Amazon SES and am stuck using the SMTP route rather than via the API because there isn't native support via IPS like there is for Sendgrid. 
I'd like to ask for or vote for IPS adding support for Amazon SES, just like it supports Sendgrid.