Matt

Changed Current Release to No

Do you mean like this? CleanShot 2024-07-25 at 10.00.00.mp4 August. Our current plan is this: - Test upgrades on clones of our own sites and convert our custom plugins/apps to v5 to weed out the low level bugs (in progress) - Have a small group of contributors to be given the zip to install, play with and give feedback for a short period (up next) - Open beta.

Q4 2024 is our current estimate.

Wow, great work! If you have the means to do this, then this is an excellent start. It's also worth reevaluating plugins every 6 months or so to see if they are still effective or if you rarely use them or they had no impact on your community.

Fairly soon, we're going to start getting some information out on how to prepare for v5. We want to get the timing right so that people aren't making huge changes to their community and then having to wait a few months for v5. The basic things will be PHP version, MySQL version, big changes (support desk, status updates, tagging, etc) along with third party things (theme editing, plugins, etc).

We have to kind of feel our way through it. We have milestones, like: Alpha 1 Upgradable Alphas Upgradable from 4.x Alphas Beta x lots Final But the timescales are really determined by how much feedback and how many bug reports we get. Rarely, we need to rethink a feature or code and do a bit of reworking. I would expect the beta process to be fairly short given how thorough we are with the alpha. We've yet to build zips and have people install it on various servers which always adds a little volume to the tracker. That'll be coming up fairly soon.

Changed Long ID to 5000008

Changed Long ID to 5000007

Changed Long ID to 5000006

Changed Current Release to No

If we're doing infinite scrolling for topics then it makes sense to do the same for topic lists, which means that on several pages, the footer would not be accessible, but on other pages it would be. That's a poor experience IMO. Another option is to do it in a container, but that may be a bit odd too. We have discussed this internally for years but can't really come to a consensus on how to do it. Infinite scroll would solve a lot of problems too, especially in figuring out pagination which is quite complicated and expensive to do.

The one big barrier to this is that you may never see the footer of your site again, and that is an important area to a lot of customers.

We don't use AI on a wide scale like that, and I don't think AI is quite there yet. I use AI in a few ways, but you always have to check the output as it's often wrong, or uses method names, and database table columns that don't exist. I use Github Copilot which has access to our Github repository so it can learn about our code and make sensible suggestions from either prompts, or auto-complete, for example: CleanShot 2024-07-18 at 09.01.20.mp4 I sometimes use ChatGPT to avoid looking up syntax or functions and to avoid a bit of trial and error which probably saves 5-10 minutes on a bad day. These tools can help a little, but they don't really wholesale fix issues and find errors. I think that'll come eventually. During development of Invision Community 5, we have several safeguards in place to minimise bugs. Every single change is put into review via a pull request before it is merged into the development branch. The review has an automated PHP lint tool that checks for syntax issues and won't allow it to be merged if it contains them. We also do a human review on not only the code, but also the change to make sure it does what we wanted it to do. Some of these reviews go back and forth for weeks, others are merged quickly. That said, bugs are part of software development, that's why we have alpha and beta testing. The v3 to v4 transition was complicated as it was a complete rewrite from scratch, we had a much smaller development team and it took much longer than originally planned.

We're up to Alpha 4 over in the secret alpha testing club and things are progressing nicely. There's been a lot of improvements to the theme editor, and the text editor. We've made some improvements based on feedback to several areas including advertisements as well as fixed a ridiculous number of bugs. I think the alpha testers will agree that it's pretty stable now and closer to beta than a raw alpha. We'll be launching Alpha 5 tomorrow and this will be upgradable via the AdminCP. Internally, we're going to test a clone of this site and upgrade that to see how that goes. In the mean time, is there anyone else here that wants to join the alpha team? We're ready for more people if you are. Just let me know! If you're just curious, you can follow the releases and fixes here.

Changed Current Release to No

If you're basing this on the alpha, then just keep in mind it's alpha and we're still very much working on it.

Changed Current Release to No

Fully different Pages templates which are different, for different db/page apps Pages retains templates, so no problem there. Custom templates which are inserted into Head to keep things organized (ex: Prepid config, Google Admanager ad unit config settings... really long list, other overrides). Some apply to specific areas of the site only and can't show otherwise. Ex: {{if preg_match("/forums\/forum/", $_SERVER['REQUEST_URI'])}} remove mark site read in breakcrumb You can do this via CSS. Insert custom menu items ONLY in the mobile menu (not desktop) The menu is the menu in v5, what do you need adding into the menu for small devices? Remove social links and inset fully customized footer CSS and custom template hooks Replace native search (and place in nav bar) on desktop with Google custom search box Either JS, or CSS and custom template hooks. Replace forum/topic dots with custom images we have (read, unread, etc.) Hide post counts in forums from being viewable Doable via CSS. Remove ads from specific forums (Google policy they can't be on Off Topic areas.... rick getting banned)... this like: {{if $category->_id == 139 && !in_array(member.member_group_id,array(24))}} What pages cannot accept ads? (Not a challenge, just curious). We also have this setting. Add non-IPB custom fields to profiles inn topics Would need to be a custom app, but possibly doable. Have ads shown to guests in some areas (but not members). Ex: {{if member.member_id == 0}} Already possible . Show ads after XX post, but only if the member has more than YY posts and only if the current page has ZZ posts. Ex: {{if (!member.member_id || (member.member_id && member.member_posts < 1000)) && ($postCount % 15 == 😎 && ($topic->posts - $postCount >= 9)}} Seems quite precise, what is your use-case for this? Many custom ads inserted into locations Custom template hooks are likely the answer.

It will be insert only via the template hooks, but you can use CSS and/or JS to remove parts of the DOM if you wanted to do that.

Speed, efficiency, reduced storage needs and no rebuilding as we now compile templates at the time we build a new version and store into a new /static/ directory which will not change for the lifespan of that version. The ability to edit core templates is probably a bad idea as it can break a lot of functionality. You can insert HTML before/inside before/after/ inside after via the template hook system as above. You can still add custom CSS and JS too.

Definitely doable. We have many, many clients that get millions of views a month, with thousands online during the day, and with thousands of posts every hour. Ouch. My observation is that XenForo seems to have an aging customer base, most of whom were successful 15 years ago and have seen their communities stagnate and slow to a trickle. They don't seem to attract professionals, or anyone serious about building a modern community.