teraßyte

If you have a single storage method, you'll see this layout. Click on the arrow (Move action) to change storage setting: Once you click on the arrow button, this screen will show up: However, as I mentioned above: Only when everything is in a single storage you'll get the form above to define a new storage location: File System Database Amazon S3 Backblaze B2

Ah, I see the problem. The test site I checked with has multiple storage locations defined so I see the old layout. On new/fresh installations or with a single storage location, you see a new interface. Multiple file storage locations will be deprecated in a future release. It is recommended that you start consolidating files to a central location. To move the files to S3 you must click the right arrow icon for the storage row. From there, a new screen will appear where you can select where to move the files and have multiple choices, including S3 and B2. If you have multiple storage locations, a form to choose one of the existing locations will show up instead.

It's been renamed to "Featured Content", but it's still there: https://invisioncommunity.com/featured/

It's still in the same place as v4: ACP > System > OVERVIEW > Files > Storage Settings (button top-right).

IC5 still supports both Amason S3 and BackBlaze B2 (newly introduced in 4.7.20).

Yes. They changed it in v5 to support extensions/custom areas from 3rd party application and made a generic FURL rule that uses the area name as tab name. Your change still works because the old FURL rules are still there, but the account settings page doesn't use them anymore.

Is core_sys_conf_settings the only "broken" table? Or do you have more?

It's possible the built-in code couldn't overwrite some files because of permission or ownership issues. I've seen it happen sometimes.

Everything is loading for me now. 👍

@Jim M Both video and images are missing for me. When I try to load one directly in a new tab I get his error: Failed to fetch file from B2

This forum is setup as a test area: https://invisioncommunity.com/forums/forum/15-test-posting/ Also, upload the file as a compressed (ZIP) file, otherwise, the upload process will strip the EXIF data IPS needs to check if you upload it as an image directly.

What I was talking about was selecting this Privacy option when creating the club: Closed Everyone can see the club and who's in it, but by default only members can see posts and participate. Leaders can set individual club sections so anybody can view or participate. Users need to ask a leader to join. If you want the clubs to show on the index, you need to enable this option: ACP > Community > CLUBS > Settings > Show Club Content Areas. Select the option: Throughout the community Users will see content areas from Clubs they can view in the applications throughout the community, alongside regular content. This will only list the relative areas, though. For example, it will show forums from closed clubs on the forum index, etc. If you want to show a list of clubs themselves and not just their areas, you can use a widget.

You need to setup the club as invite-only and then a member is promoted to the premium group use an application to automatically send out an invite or directly add them.

Ahh, okay. I keep forgetting about the Cloud. IPS should provide a way to get alist of those fields in the ACP API reference guide then. 🤔 As a temporary workaround, you can look up the schema.json file of the core application. by adding /applications/core/data/schema.json to your site URL. For example, for this sit,e it would be: https://invisioncommunity.com/applications/core/data/schema.json Search for the core_members table name, and you can get a list of all the default columns in it. Here's the birthday columns for example: "bday_day": { "allow_null": true, "auto_increment": false, "binary": false, "comment": "", "decimals": null, "default": null, "length": 2, "name": "bday_day", "type": "INT", "unsigned": false, "values": [], "zerofill": false }, "bday_month": { "allow_null": true, "auto_increment": false, "binary": false, "comment": "", "decimals": null, "default": null, "length": 2, "name": "bday_month", "type": "INT", "unsigned": false, "values": [], "zerofill": false }, "bday_year": { "allow_null": true, "auto_increment": false, "binary": false, "comment": "", "decimals": null, "default": null, "length": 4, "name": "bday_year", "type": "INT", "unsigned": false, "values": [], "zerofill": false },

The core_sys_conf_settings table should be the same for all 4.x versions. I don't remember any changes to it at least. 🙄

There are 3 integer fields in the table for the birthday: bday_day bday_month bday_year If you need other fields, you can just look up the names inside the core_members table directly.

The conf_id column should be set as an auto-increment value, so the ID missing shouldn't be a problem. This is the first time I've ever seen this error. Never seen it before in all the upgrades I did.

Do they have their browser set to delete the cookies when it's closed perhaps?

PHP info says you're still using PHP 7.4.33, not 8.0. Also, version 4 supports only 8.0 and 8.1. Anything 8.2+ is supported only by v5, so PHP 8.4 won't work, either.

P.S.: You should also remove the gridspan value from the phpDoc comment in Select.php since it's no longer available: 'gridspan' => 3, // If 'parse' is set to 'image', this controls the gridspan to use when creating the option layout

Any update on the JS lag issue? The editor and other areas are barely usable in their current state. Everything displayed slowly becomes extremely irritating after a while. Even tooltips still take a few seconds to appear/disappear/switch. 🤷‍♂️

The problem is the extra (broken) parameter after the FURL that is not properly parsed by the code: =&id=1 You can easily reproduce it on this site by adding that to a weekly URL: https://invisioncommunity.com/events/week/2025-02-18/=&id=1

That part is not the description, but the forum rules. It only shows viewing the forum itself.

From which version have you upgraded MySQL? And what's the new version? If you have a backup made before the MySQL upgrade, your best option would be to empty the database, downgrade MySQL to the previous version, and restore the database backup.