Matt

Code clean up ✅ Import over FQN ✅ Better use of traits ✅ Search code clean up ✅ Happy PHPStorm without hacks/class_alias ✅ More recent PHP versions needed ✅ Better use of newer PHP functions ✅ More to follow, but I think you’ll be content with the changes to be announced.

Hi all, Next week we plan on releasing a few blogs outlining what development looks like for Invision Community v5. I was curious as to what changes you'd like to see, and what changes do you think are coming?

I think a lot of what you need can be done with Pages Databases.

Happy to listen if you have specific features you want to discuss?

Hmm to fix the bug or change the translations to "anonymous-ish"? 🤔

GTM sits above Google Analytics, it handles passing the data to it. https://www.analyticsmania.com/post/what-is-data-layer-in-google-tag-manager/

You also use an analytics provider such as Google Analytics and our powerful data-layer management to track what your members do on your community.

Unfortunately there is no easy answer to this. We tried for years to hide meta data so we could track piracy but they always find it and remove it.

I think you're relatively safe with Google and Apple. I rarely see FB and Twitter sign-in buttons anymore.

We're keeping that as you can still use the 'internal' method but we'll be reviewing all our promotion tools to make sense of them as we have a few ways now (pinned, featured, promoted, etc).

We've removed the promotion tools in v5. With Meta increasing the barrier to get approved and Twitter falling apart, it doesn't make sense to keep it. There are various low-cost promotion tools such as Buffer (free tier) to manually post to social media, or you can connect via Zapier to post to social media.

It's worth checking your browser's dev tools > console to see if anything is preventing JS from running.

Almost all functionality will be available to those with active licenses, certainly more than enough to combat the surge we've seen. We may add a little more algorithm-crunching stuff for cloud given access to AWS computing power and more room to swallow additional costs given cloud pricing. It's very much in progress, so we'll have news when everything has been completed.

The project is well underway. Not firm ETA, but it's coming to v4, so you won't need to wait for v5.

I'd like to say more but we really want to present the entire package so it all makes sense. I also want to say that while I often talk about the new stuff we do, it's the product of a very hard working team. We have had input from multiple stakeholders, including those who use the v4 dev tools daily, when designing the new development tools.

We continue to offer major upgrades to active license holders. We do not require a purchase of a new license. Better.

You had a great view to watch Dan Butler's penalty zoom over the stadium.

PHP 8.1 (8.2 compatible) will be the version minimum. You won't need to re-learn everything, it's not a complete rewrite. Some things to keep in mind: We import namespaces so we no longer use fully qualified names. What does this mean? Old: namespace IPS\foo class foo { function _construct() { if ( \IPS\Member::i()->isAdmin() ) { $this->bar = \IPS\Request::i()->input; } } } New: namespace IPS\foo use IPS\Member; use IPS\Request; class foo { function _construct() { if ( Member::i()->isAdmin() ) { $this->bar = Request::i()->input; } } } You *could* use FQN but we no longer do that. The result is a lot neater. We have also moved most Content interfaces into traits (where it makes sense) and we've introduced a few new dev tools which we'll speak about very soon. So it's really about cleaning up existing code and moving existing hooks, etc into the new dev tools. You're not starting from scratch again. I'll be working on some new dev blogs to go through all the changes in a bit more detail hopefully later this month.

We’d need access to your site and database to see what the query is. We do cast it int if it’s numeric so something is going wrong there.

That is very odd. Is this still an issue and have you tried another browser?

The ordering issue isn't the same as the GH issue. I think we've (tried) to fix the sorting issue before. If you can give Marc some more information, we can take a look.

The most we could do would be to remove the app but that would mean losing your data. I would work with the app author to better understand what the issue is.

I'd check with your host and look for any rewrite rules.

I'd assume the DOM structure of the incoming email is bad. It's hard to say specifically without looking at a sample incoming email.

What’s the use case to prevent them using it?