AintNobody

It's good to know it should be coming back, as it does make life easier when giving support.

My beta version never got the correct new templates for Pages; I had to copy the exact new template over (I did report and mention this).

I don't mind the new position, but the old position was logical. Not sure which I would say would be the most user-friendly, but it's in a good area for the eye now.

I have made a block using IP.Pages which bring it back; it also slightly redesigns the look. I know not all have pages, but someone else might release a more suitable version. I would be happy to share the code. For my personal preferences, I want to put the (See full list) to the right, and I need to give the user area a bit more padding on the right. My live site is nearly set up perfectly; however, v5 has some slight differences.

@Wes Elrod : If you can, try to make sure it's the best version of PHP that your Invision script supports. 4.7 is PHP 8.1 (I think) 8.2 and 8.3 aren't officially supported, if I am right. If you are on 5.0, you may want to consider setting 8.3 with all the needed extensions, but as mentioned, 8.1 is still used by some as the minimum version.

Be sure your server is using Nginx @Square Wheels. Provided your server has enough RAM for your site's demands, and the server is properly set up, you should be fine.

Agreed, it's useful for transparency and to show how active the site is. I tend to think that when people hide this sort of information or the block itself, they are hiding something. I know in admin forums, there's often talk about certain tactics to fake your site to look busier, but the information is still relevant.

I am often asked by members (who are elderly or not as tech savvy) to alter these types of things, so it would be useful.

Maybe it still exists with CSS? There will be changes which we, as site owners, will have to adjust to, and it extends to our members; but it might be worth looking into if it can be achieved with CSS. I tinker, and I feel I am getting better at it; but if it is actually possible, I am not knowledgeable enough to know, but feel it is worth suggesting.

No, you can set it to the classic forum view still. The toggle on the community index page is gone, but there's a setting in user preferences now. I haven't checked yet, but I showed my father my dev site, and his account didn't have access to the layout change. I believe there is a permission for it that he might not have. As an admin, I could change it.

There was mention of a plugin, but by default, you cannot, I don't believe.

It's okay, I mistook the "request upgrade" though I should have read the image. No wonder I couldn't find it. 🤣 When I upgrade, can I escalate issues to a ticket? On my dev site, using Beta 13, I think. I have no end of theme-related issues; some I have resolved by removing traces of plugins from within my database. Most I haven't been able to resolve, despite disabling and uninstalling apps/plugins when upgrading from 4.7. I'm aware that tickets are generally discouraged in favour of posting in the forum, but I am still mindful of the hacker(s) who took my site down. So, when I do finally upgrade, which won't be for a while, I think there will be many problems with which I will need support. I'd much rather avoid anything publicly displayed, especially upgrading to a new major version. If I can't, I'll find some other means. 👍

Would Invision allow us to schedule the upgrade process? I assume currently it would be on a queue basis, for those who click first, and they would need to be ready. If clients are rushing to upgrade and the demand is high, it might be better to have a more thought-out upgrade process, to upgrade when people are ready and when third-party resources are available. Meaning Invision wouldn't be hit with requests, but site owners can work on what's needed within a timeframe better suited for upgrading their sites. I appreciate that an upgrade is on offer, especially when historically clients were promised one free upgrade (something I have never used). I won't be rushing to upgrade, or causing further work for Invision. There are certain resources I would like in place, but my suggestion would only work if the demand creates a vaccum of problems from people rushing and therefore delays the process for everyone.

The main thing is the worry of losing membership, but dedicated and keen members will ensure that they can still take part in a community they belong too. Some might register new accounts, but then as admins we can do our best to merge those accounts - retaining the new details to ensure they can continue but avoid missing their previous content. People do put a lot of effort into their accounts, so I do understand how important it is not to have this side overlooked.

I think it needs to be wrapped in HTML.

Does it do it here? Just testing. - It didn't, which is stating the obvious. 🤣

I'm quite certain that 100% of your community has signed out at one stage or another. There's been bugs which have caused this, but they may have their information saved which allows them to easily sign in. Also, devices change and cookies don't cross over. Informing your community ahead of time is exactly why I suggested you prepare for the change. You could run a poll to find out who has lost their emails/passwords, but again I would assume most would contact you about issues instead of ignoring them. I try to do admin announcements regularly for important information, also have a discussion on changes and issues where I update my community ahead of time. You could also send a bulk email out warning people, but this doesn't help with forgotten, lost or fake emails. I tend to find someone has lost their email, they will request it to be changed, or will change it themselves. For me, I think it's just part of informing the community, but I had no objections. Perhaps address the issue outline and ask for feedback from your community; just try to put your personal thoughts in it and approach it open-minded because this will ensure honest feedback. If you say you're against it, it will likely sway opinions. If you've used Facebook, Gmail or any other registration processes to make things easier to join. If these details change, and the member hasn't added an email or password - you would encounter a bigger issue. I have Apple, and I notice there's privacy emails which I am not sure how they exactly work, but I would have to assist those members to be able to sign in. It's not that difficult to associate genuine members having issues with people seeking to gain access to an account which isn't their own.

But Meta doesn't care if you are hacked or have your account stolen, they won't help you get it back if it happens. They can't prevent scammers from cloning your account, and if you report it - they'll say it doesn't go against their community standards. Yes, an element of this is due to them using AI to moderate but even when you get a human they are just as dumb. I only recently made the change and much prefer it. It should prevent people from joining with fake emails if they are inclined to stick around, and it creates a good marker for those who join without any true intention of being involved. There are things I have been concerned about with v5, but sometimes you have to accept that progression means changes conflict. Inform them ahead of time if you do make the switch to v5, before you do, change it on v4.7 so that people can get used to it ahead of major changes. Therefore, they are likely to settle and familiarise themselves with the change. My community has a lot of older members, and they have made the change perfectly fine. These are non-tech savvy people who I have had to explain similar things to in the past. (Not that I mind explaining anything) Most plugins, if they are worth keeping, should be picked up by someone. The main thing is to be supportive of the devs who do release high quality resources, and be a part of their community. I used to hate the idea of being on 10 or more dev sites, but I actually prefer it. You learn to appreciate what they do a lot more, when you see them regularly releasing new resources and maintaining their existing ones. I feared that v5 would ruin my prospective of selling merch, but I think it's important to stress trying v5 even if it's in a local environment. I wouldn't migrate from IPS over something like a username change, and I wouldn't risk remaining on 4.7 beyond the supported time frame. It's good IPS are keeping security and support open for 4.7 users for some time; it gives you plenty of time to access and see how v5 evolves over time.

He had experienced a personal matter, where he mentioned to me that he hoped to travel the world a bit - yet he also expressed that he was busy with work. Having suffered the same personal circumstance in 2023, I fully understand and I just hope it's that Michael John is travelling.

A question some people hate being asked, so forgive me, but do you mind sharing any other work or releases you plan to do @The Jimmo?

I have a footer error which I can’t resolve, thought to be caused by missing files but I don’t think it’s the case. I have suggested that there could be more going on, but who knows. I will be curious if you have issues due to the upgrade process or if it’s due to left behind traces of plugins. Some of the issues I experienced, I resolved by removing parts of plugins left behind.

Is this the same for v5? I am aware it’s the case for v4.7.

Can the display pictures be disabled for the Who’s Online? I understand CSS will be able to hide it, just wondering if there’s a setting in the ACP for it.

This is useful, perhaps something @Adriano Faria can look into it down the line.