Just bugs / missing functionality reports - no griping

I wasn't even trying to be sarcastic, though. Tbh if we are still here after the mess this site has become since the downgrade,it's because we'll stay here (complaining, but here) until the lights go out.

Odhran bought the business with his own hard earned cash. Boards belongs to him and nobody else. As such, he's perfectly entitled to do with it as he wishes. He can be involved or not involved. However, I think it would be a nice touch - and ultimately commercially smart possibly - to show an appreciation of where Boards has come from. Maybe not from the Boards side but from the user side there is still some sense of community.

Usually, smart business is to keep the cards close to the chest, particularly in uncertainty. Where we are now It would be a nice for the business's most valuable asset, us users, to know if we are helping by providing these functionality reports or wasting our time while we sit wondering if we will have a Boards in 6 months.

em…. No "crumbs bar" whatsoever crumbs scrolling up with the posts.

vs

Offender seem to be

resolution would be
position: fixed;

Since yesterday I've been getting logged out repeatedly. Logging in doesn't work, as my password is not recognised. Moving around to a few pages gets me back in, but then it happens again, and keeps doing so. Samsung Galaxy, Chrome.

I don't think it would be unreasonable to request a weekly or even a bi-weekly update from Mike.

He was last online on Friday evening, but hasn't posted here in over a month. A simple update once a fortnight even just to confirm that the issue is still being looked into would be nice.

Can I ask Mike, if the fix that brought on the jumping is worth keeping or is it the case if it's reverted the jumping stays anyway? Which is the worst of 2 evils what was fixed or what was caused by the fix?

I don't mean this as a personal criticism whatsoever, but this was the exact reason why we were told that vBulletin had to go. Yet here we are again with a patchwork that breaks whenever the core is updated. The only long-term solution in this case is another migration to a platform that actually has most of these features out of the box, so the customisations won't be necessary.