Randy Calvert

In general you should not be storing files that big in MySQL. But I have not seen this change from 4 to 5 and honestly don’t expect it to change. It would be better to use a storage bucket for files of those size.

Just for that, they're going to skip version 7 and make it name it "Beta Snow Leopard". 😄

It looks like IPS is using Backblaze as well... I just looked at my cloud install and all of the storage is now on a non-S3 bucket.

How are you going to handle users toggling dark mode? For example brown on black will be virtually impossible to read. Blues on black will also be difficult.

It’s situations like this that actually makes companies communicate LESS. When you expect every decision to be made before talking about something, it takes much longer to get out as you can’t really start sharing till the end. In this case, Invision is sharing info as they have it. They are giving customers longer runways to plan for big changes so there is less problems long term. But at the same time that means not everything can be perfectly and fully articulated because not everything has been decided yet. To say it’s a failure of organization is patently wrong. It would be IF they actually released the product without decisions being made. Instead you are being given info as it’s decided and have had a much fuller insight into what has been happening throughout the entire development process.

It’s the default behavior for any vanilla self hosted install and literally all cloud install.

An IPS staff person can correct me if I'm wrong, but my read of this was not that everything had to be ONLY under uploads, but that it had to be in a single location. Today, you could have a different storage location for each of the following: Advertisements, Attachments, Badges, Club Custom Fields, Clubs Images, Custom Emoji, Icons & Logos, Image Proxy Cache, Login Method Icons, Profile Photos, Custom Profile Fields, Social Media Promotion Images, Ranks, Reactions, Referral Banners, Theme Resources, Forum Cards, Forum Icons, Customer-Uploaded Advertisements, Support Request Custom Fields, Purchase Fields, Customer Fields, Payment Gateways, Product Groups, Product Images, CMS Media, CMS Pages, CMS Records, Calendar, Event Cover Photos, Gallery Images Do we really need a custom storage location for login method icons or custom profile fields, etc? It SOUNDS like they're saying you'll define a single location for storage (be it the "uploads" folder or an S3 bucket or whatever). Everything would be stored in that location, whatever/wherever it might be. So you could continue to use a CDN, however you would not be able to have multiple subdomains for each of them. It would simply be cdn.domain.com/club_images and cdn.domain.com/attachments or whatever the taxonomy is going to be.

What would be the value of this? It would seem to take away from a site's branding and would make for a potentially VERY messy user experience.... page one has snowflakes, click to page two and it has a yellow background with a white font, and on page three you move to something entirely different.

Zapier does not really have anything to do with the editor. It's basically the same as it has always been. Its integration point is not via screen scraping but instead via API (through the Integrations section of the ACP).

Awesome! These incremental changes are certainly appreciated!

Glad you found what was going on! 🙂

IPS has already said this is not going to be reconsidered. So I would not expect to see this changed. Think of this as "Back to Top".

IPS in general does not give dates for releases. However given that IPB5 is in beta now, it should not be too long. I would expect end of the year or very early next personally. There are three major US holidays (Thanksgiving, Christmas, New Years) coming up and IPS generally (historically) does not do releases around those times as they don't want to deal with big problems during times when they are on reduced staff and trying to celebrate like the rest of us.

In Google searching the error, it appears to be a Chrome issue. https://www.google.com/search?client=safari&rls=en&q=chrome+status_access_violation&ie=UTF-8&oe=UTF-8

Highly disagree that it's "one of the most frequently used controls".

Take a look at:

Version 5 does not have plugins. Everything must be an application.

Support is primarily done via this forum and is the starting place for requests typically. It has been that way for well more than a year. If there is something that needs to be handled privately, a staff member can move the request to a ticket (over email).

Commerce has not been removed. It will continue to be available and they're adding more support for digital transactions (like better ad support, more subscriptions options, selling different digital offerings on your site, etc). The only thing removed from Commerce is the ability to ship physical products. The marketplace closure is not related to IPB5 development and has been done for MONTHS already.

Matt did not say that self-hosted customers won't be able to test IPB5. It said that those who test it will be testing from a cloud-hosted instance. This means you won't be able to upgrade your live site to v5, but you should not be doing that PERIOD right now. It does means anyone testing would get a brand new, fresh instance cloud hosted instance to login to the ACP and play with settings, etc. Later in the development process the self-hosted download version would come out... but that does not mean you could not test the hosted version in the mean time.

Would it be possible to choose to receive on-site notifications as well (aka "the bell")? This looks really interesting and is going to challenge me to think about how I organize content now. I can absolutely see potentially consolidating a few forums... I can also see being able to have a page that has images, files, and topics on a single subject as being a great way to start building documentation, etc.

Don’t forget to keep me around!

Most of this thread is about needing more buttons to do things... edit source code, play with styles/headers, fix messed up code, etc. I can say with a very high level of confidence these sorts of things are not needed by "common users". The things being talked about here are things power users want/need. The vast majority of actual end users will never need more than the default styling options. A site admin or major site content producer might need more however... and I think it's a fair ask for those users to make the request for needing more power in helping them publish. Those actual end users are happy with the buttons there and don't need more!

The product is real and it's coming. I've been fortunate enough to play with the early alpha version and it's chugging along very nicely. The new editor is sweet and the UI update is slick. There are certain areas still under heavy development. It's not ready for prime time yet, but I've seen many bugs squashed and lots of great polishing being done to the stuff they've already announced.

As the feed view is an IPB5 feature, it won’t be available until IPB5 is available As the feed view is an IPB5 feature, it won’t be available until IPB5 is available.