Ehren

I’ve downloaded an old version of Xcode (which has an iOS 13 simulator) onto the 2015 MacBook Air and I can see the culprit in the code. I’ll do my best to make it more functional on older software 😅🤝

Hello, If possible, could you please elaborate on what you would like changed here? The entries are intended to be contained within a single box, with borders to separate them: There was an issue with a lack of margin between the title and the description if that’s what you’re referring to? That’ll be fixed in an upcoming version.

This has been addressed for the next update 🤝

Even though v5 uses very modern CSS code, care has been taken to ensure old devices can still render everything correctly thanks to fallback code. With that said, if the operating system on these devices purposely isn’t being upgraded, it becomes incredibly tough to start supporting them. The usage of iOS 13 is only 0.01% according to “CanIUse”, and I wasn’t even able to find a used 6S which was running iOS 13 on any marketplace website in my country, so this is most definitely a very uncommon situation. During development, I’ve been testing v5 using a Macbook Air from early 2015 (before the iPhone 6S was even announced) and it’s working great. I believe your iPhone 6S would also do the same if you were to upgrade, since iOS 15 comfortably handles v5. I agree that v5 could look a little more presentable for vintage operating systems, but I can’t make any promises that everything will work (CSS isn’t the only culprit here, we’re also using modern JS and new HTML elements too).

Agreed. These buttons will be relocated to the header in the next update 🤝

My apologies, it looks like that feature (private records) already exists! :)

Actually, iPhone 6S supports iOS 15.8.3, released just 2 months ago on July 29, so I would recommend upgrading to that first to see if it’s fixed. 🤝

No, the entire CSS framework has changed - so you’ll need to redo most of your custom CSS for v5.

It’s just a custom database - I really don’t think there’s anything else too custom about it except for a few fields. Private records (which only the author + admins can view) aren’t a feature with Pages, but you’re welcome to create a separate suggestion if necessary 🤝

Thanks for the suggestion however there are currently no plans to include this. You are welcome to add that CSS to your own community if you’d like to implement it :)

Light and dark are the only two options. If you want different coloured theme variations (some football sites do this for each team), you can create multiple themes, or you can try implementing your own color picker using JS and CSS.

The Bug Tracker feature on this site is just a Pages database with a few custom fields. It’s not an application which can be toggled or preinstalled. Creating a database like this requires no custom templates or anything, so it’s very easy to create one on your own site if needed :)

Hello, Visually, does the site look okay? I have no idea why links wouldn’t work on iOS 13, since they’re just regular HTML links. Is it every link? If you’re able to elaborate on any of that (maybe with screenshots or videos) that would be great :)

Lazy loading images is only a good idea if the image is “below the fold” (outside the screen while the page loads). Since logos are at the top of the page, they will always be on the screen during page load, so lazy loading is not ideal for them. You’ll even get suggestions from PageSpeed tools telling you to remove the attribute if it exists.

The email doesn’t need to be “active” for logins to work, so burner emails or expired emails/domains will work fine for existing members. But when it comes to participating in a community, having an active email is a huge benefit (password resets, email notifications, etc). The migration from usernames to emails for logins is a nice reminder for your members to make sure their account details up to date, which is never a bad thing.