bfarber

Come on guys, Invision is never going to please us all. And even if they adopted granular ACP theme adjustment tools same as Xenforo has, we'd still need to sit back and adjust dozens and dozens of margin, padding, line height and similar parameters to suit all of our individual tastes. And then you have the menu, which in my view should be docked in an object that can be bound to the DOM either on the server or in a CSOM. But, even if Invision did that, we'd still need to position it ourselves, and move it around depending on the app currently in use. So I say, be careful what you wish for as even though I'd like to see pages that are rendered a little more tightly and menus that break from the current paradigm, you can bet if Invision did that, we'd still be back with another set of demands next month.
So how about we get together, put our hands in our pockets and see if we can find a designer come dev to create a configurable theme for us - and I mean a theme, not a (wanit in green, blue, red?) skinning exercise. It could include all sorts of presets including spacing, fonts, menu positions and so on, including specifics for desktop and mobile. Won't be cheap, but at least at the end of it we will have something we can use to give us what we want, rather than assuming Invision can pull a theme styling rabbit out of the hat which is going to miraculously please us all. I just don't see it.
Of course, Invision are more than capable of doing this themselves. But a bit a string only goes so far, and if they do this, then all the other stuff we need like video transcoding (ok I need that 🙂 ) will get pushed to the back of the queue.
So how how about it? Put our energies into something creative?

It is recommended to output webp files in a <picture> tag instead of an <img> tag, which supports specifying multiple versions. That's something we'd have to take into account.
Also, ios14 added support apparently: https://css-tricks.com/webp-image-support-coming-to-ios-14/
I found that we have an open internal suggestion discussing this already so I've updated it. Thanks!

You can delete the contents of that table at any time, yes.

https://open.spotify.com/oembed?url=https://open.spotify.com/album/2oj3FG6fos7zAQJxLQGzou?si=3U-Q9qrJTTOXXzOmgii39g
Their oembed endpoint is down.

There were a few different Spotify issues that occurred within a short period of time. I would suggest testing the issue here on this forum (in the test forum) and if it's fixed then the issue is resolved for 4.5. If the issue is still occurring let us know.

Frankly we've had several fixes for Spotify in recent times and I can't remember off hand which was the most recent one to even suggest a way to patch yourself.

I can confirm a fix for this issue was committed - it apparently hasn't been released yet, but should be included with 4.5.0.
 

When you use the "print screen" button, your operating system is taking a copy of your screen as a binary image into your clipboard. Most modern web browsers allow you to paste that binary stream into the editor (and in the case of our software, that paste is turned into an upload).
There is no way to control what type of image file your operating system produces in this case. It is possible to convert the image type on the server, but there's really no reason to do so, so we don't.
In short - there's no real way for us to control this behavior. You can check with Apple/Microsoft/Whoever makes your OS to see if there are any controls as to what kind of file is produced when you hit the print screen button.

It is recommended to output webp files in a <picture> tag instead of an <img> tag, which supports specifying multiple versions. That's something we'd have to take into account.
Also, ios14 added support apparently: https://css-tricks.com/webp-image-support-coming-to-ios-14/
I found that we have an open internal suggestion discussing this already so I've updated it. Thanks!

Yeah, I would say that if you already have a PHP script written to output the data from your custom database table, just include that script using the template plugin mentioned above. That'll be easier than converting the code into our framework (unless your goal was learning how to use our framework).

We'll take a look, thanks for bringing this up.

It is recommended to output webp files in a <picture> tag instead of an <img> tag, which supports specifying multiple versions. That's something we'd have to take into account.
Also, ios14 added support apparently: https://css-tricks.com/webp-image-support-coming-to-ios-14/
I found that we have an open internal suggestion discussing this already so I've updated it. Thanks!

It is recommended to output webp files in a <picture> tag instead of an <img> tag, which supports specifying multiple versions. That's something we'd have to take into account.
Also, ios14 added support apparently: https://css-tricks.com/webp-image-support-coming-to-ios-14/
I found that we have an open internal suggestion discussing this already so I've updated it. Thanks!

It is recommended to output webp files in a <picture> tag instead of an <img> tag, which supports specifying multiple versions. That's something we'd have to take into account.
Also, ios14 added support apparently: https://css-tricks.com/webp-image-support-coming-to-ios-14/
I found that we have an open internal suggestion discussing this already so I've updated it. Thanks!

It is recommended to output webp files in a <picture> tag instead of an <img> tag, which supports specifying multiple versions. That's something we'd have to take into account.
Also, ios14 added support apparently: https://css-tricks.com/webp-image-support-coming-to-ios-14/
I found that we have an open internal suggestion discussing this already so I've updated it. Thanks!

Yeah... I've done a complete reversal on this after thinking on it for several hours.
I should have paused and given it some more thought before only seeing it as a negative.  This new change will work just fine.
Thanks for the positive reinforcement, it's appreciated.

I'm seeing the same. I'll make a note to look into this for an upcoming release, thanks.

Test Driven Development (TDD) is indeed a popular approach, but it is one of many. I would agree that in mission critical situations like pharma/aeronautical you may find very stringent requirements because the end result can literally mean life or death.

Yes, just for clarity - disabling bbcode will have no impact on existing content, only on newly submitted content.

Because it's not an option from the AdminCP, but is an option at the software level. You can review init.php and see all the available constants there with comments explaining what they do.

Personally I like the new setup overall, makes checking for updates much quicker and installing said updates. If I need to add something custom not on the marketplace I am able to do so as well. I'm past the point of having time to tinker with the code, I just need it to work! (thanks @Adriano Faria for having all yur stuff work, it's appreciated)

The methods are still available in 4.5 yes.

\IPS\GeoLocation::getByIp() returns an instance of \IPS\GeoLocation (so it's an object, not an array).
{{$geoData = \IPS\GeoLocation::getByIp( 'my IP' );}} {$geoData->lat} {$geoData->long}  

An improvement like that will not be introduced in a point release. It will be something for a major version, just to be clear.

When it is fixed, the fix will be noted in the changelog.