Matt

With Invision Community v5, we've removed the ability for self-hosted English users to type the 16th letter of the alphabet. I'm literally taking the P here. I see where you're coming from but is it really any easier? Instead of inspecting the source code and seeing /uploads/monthly_2024_12/file.jpg and then going to that one folder, you're seeing /uploads/gallery/file.jpg and then going to that folder. It might feel odd to have different kinds of files mixed up, but it's all 0s and 1s on a disk somewhere and the software can figure it all out so you don't need to worry about it.

Hi... Daddy? A phrase I've not said for about 40 years. Our ideology for version 5 was to rebuild the HTML and CSS frameworks to make them more suitable for large scale changes. If you look at the source for v5 you'll see it's much more semantic and less instructive about the design giving more scope to radically change the layout without touching the template code. For those times where you need to inject new HTML, we are populating the templates with hook points to allow you to do that. Likewise, you could leverage JS to do the same. The theme editor is a great place to start to make sweeping changes to margins, borders, spacing and colours. Removing the ability to edit templates means we can compile them once per version and store them as static files instead of relying on the database fetching them, storing them as a string in a cache and then using eval() to turn them into PHP code on each click. You get a more efficient system, and really an easier way to theme the system that survives upgrades.

Lots of good feedback here. Our aim was to reduce the complexity of all the various locations people can choose to store files. We have seen tickets where people have multiple /uploads/{name}/ folders with theme resources in one, screenshots in other and often they change their minds and move them about, often with tasks locking up and issues until the move is finished. In v5, we wanted to simplify that remove the ability to spread files all over a web server when really you should only ever need one location. There isn't really a reason to have some files on disk, and some in S3 for example. It overcomplicates the software and can get people into trouble. That said, the inability to specify a path outside of the web root is valid, and we'll have a think about that. On upgrade to v5, multiple file storage locations will remain, but you won't be able to add any new ones. We're not moving files around on upgrade as that would cause all kinds of issues.

Changed Long ID to 5000035

Do you see broken images in widgets? If so.. yeah, the widgets are cached. I'll have to invalidate those caches when a file is edited. The old thumbnails are removed, so that's the issue there.

That bug is still open. Had a meeting with Esther yesterday to run through the last of the bugs and we should get this one done for the next beta. If you see comments no longer showing on Pages articles, see the original post of this topic. 🤭

Changed Long ID to 5000034

Beta 7 is here, and I'm digging deep into my Bingo Lingo today! As always, check out our release notes for a full list of this week's fixes. Update: If you notice Pages article comments have vanished, do one of two things: Edit each database and under display add a value for comments per page. Wait until after 3pm GMT and apply the patch. 😇

Changed Current Release to No

The only place we keep the raw file contents in a table is in theme resources, elsewhere it's fine. We chunk uploads and they get sent straight to disk/S3.

Haha, sorry - I've been on planning calls today and I don't think there's time to run through the open PRs, build and test before my end of day. It'll either be a lot later today, or tomorrow morning.

It took a while to figure out, and yeah it was just a few lines of code in the end.

Fixed in the next beta.

Looking now.

Probably tomorrow.

Ok, update your license with your FTP and ACP and we'll have to add some debugging and upload a new version and see what is going on.

I see one broken image, is that normal for when this happens? We'll probably need FTP and ACP. Can you update your client area with those details? Thanks.

Is this broken now? Yeah, we have no idea. @Adriano Faria let us know when its in a broken state again and let us take a look before editing/fixing the broken files.

I think Esther may be onto something locally.

I can't reproduce this either, and I've really tried. Next time it happens, please let us know ASAP ([email protected]) or DM and I'll take a look at your site before your restore the screenshots to see what may be going on. From what I can gather, the template does have an <img> tag, but the image URL no longer exists, yet all the uploaded images are still attached to the record, so I'm really unsure what is going on.

Thanks Day! Let me know where to send the money. I have two briefcases and the combination on both is 1337. I like the car analogy. I have a Tesla Model Y, and it doesn't have full auto-driving because I didn't pay for it. I don't see that as a missing feature though. I think a lot of that thinking is just down to our legacy of having a single product for all. And don't worry, I love what I do and I'm genuinely thankful that I get to do it. The only constant in life is change, and we've had to change and adapt over the years. Some use it as a stick to beat us with but without adapting we'd have vanished years ago.

There's no need for apologies for this topic. It's better to air concerns and have a discussion than let the fester in the dark. I appreciate your custom and sticking with us. Our primary aim is to safeguard the future of Invision Community, not just for those that work here but for the thousands of communities that rely on us to keep delivering updates and new features to help keep their communities active. It means making tough decisions at times, and these aren't always popular but they really do help secure a future. The most profitable model possible was the one we had 15 years ago when we were selling hundreds of licenses a month at $149.99 a go and our only costs were answering support tickets. Our monthly AWS bill is quite frankly a hate crime.

I think I answered this fairly comprehensively in my post above. Much appreciated. Most customers are fine and topics like these are just concerned customers voicing their thoughts which is fair and reasonable.