XenForo 2.0 Discussion

Status
Not open for further replies.
There is a difference between the two. Unregistered is guest users and unconfirmed is users that haven't completed email confirmation.
True. In XF 1, permission of both status is merged and can't be set to different.

For example :
In XF 1, i can't make unregistered can't search, but unconfirmed can search.
 
For example :
In XF 1, i can't make unregistered can't search, but unconfirmed can search.
I don't believe this is the case. I've just checked this by setting a test user to unconfirmed/unregistered (with no other user groups) and the search was unavailable to them.
 
Where can we download the ai add-on for XF2? Or is it in the core? ;) :p
We don't need search, That's so XF1. Just serve them what they like. :D
 
@semprot Is there a point in splitting it?

In an ideal world, people won't ever need this because they will either stay a guest or accept the mail confirmation immediately. (There are those who get the mail but never come back, they don't need it either).

If someone does not want to register for whatever reason, but wants the additional possibilites of the Unconfirmed status, he/she could just fill out the form with nonsense data. Takes about 10sec. With splitting the permissions, you're basically inviting people to do so because they can gain something out of it.

... that was the bad part, what's the good part?
 
The good part is, for example, that you're able to show a friendly notice to people who have not yet confirmed their mail, explaining probable causes and linking them to the resend confirmation mail functionality. If you have non-tech-savvy users of mixed age, you won't believe how often you encounter people who need that extra bit of support.
 
The good part is, for example, that you're able to show a friendly notice to people who have not yet confirmed their mail, explaining probable causes and linking them to the resend confirmation mail functionality. If you have non-tech-savvy users of mixed age, you won't believe how often you encounter people who need that extra bit of support.
We're off topic now, (again), but that would basically be doable with the notices system. Problem solved.
 
I'm sure the answer must be in this long thread. But I ask: At which stage of xf 2.0 development coders can start develop addons for xf 2.0?
 
Any NodeJS with XF2?
Seems highly unlikely – Node won't run in PHP-based shared hosting, so using it would change XenForo's minimum requirements to be a VPS (and the technical knowhow to set up both PHP and Node, and make them interact properly). All that wouldn't really gain them much real advantage, to be honest – there's not enough that Node does over PHP to make it worth it.
 
Indeed. Besides, there's nothing really to stop add-on developers from utilising something like Node for specific usage. We confirmed a while ago that the only JS framework involved in XF2 is jQuery (version 3.1).
 
Seems highly unlikely – Node won't run in PHP-based shared hosting, so using it would change XenForo's minimum requirements to be a VPS (and the technical knowhow to set up both PHP and Node, and make them interact properly). All that wouldn't really gain them much real advantage, to be honest – there's not enough that Node does over PHP to make it worth it.

NodeJS is the future but that's my opinion but I understand your point of view and hoping to see some plugins based on NodeJS like a chat system but Siropu is working on it and some websocket plugins to increase performances.
 
Last edited:
NodeJS is the future but that's my opinion but I understand your point of view and hoping to see some plugins based on NodeJS like a chat system but Siropu is working on it and some websocket plugins to increase performances.
Well, it's not so much "the future" as it is an alternate technology, with advantages and disadvantages compared to PHP. The advantage of PHP, and one of the reasons I suspect XF still use it, is that it's ubiquitous – you can run it on any shared hosting platform, without custom installation or setup work. Node, for all its advantages in concurrency and support for technologies like websockets, can't be thrown onto a $20 a year shared plan and just work, which cuts out a massive part of XenForo's customer base.

Node is a great runtime, and amazing things have been built on it – I'm a fan, I work with it as well as PHP, Ruby and Elixir for my day-to-day work. But for XenForo, it's not the right tool for the job. :)
 
I really like the new approach to show the New posts in the index instead of the classic "Forum list".

But I think it could be also more powerful and useful by inserting in the same page a list with the latest/updated threads and another with the Popular/trending/hot threads that shows topics selected on likes/views/reply criteria (for example: a thread that has many likes and views and in the same time is one of the most replied of the latest days/week should appear in this list).

Another idea is eventually to make an unique list that combines latest and "hot/trending" threads like Facebook does with his posts that shows in home.

Also, I think the index needs another tab called "Followed Forums" that shows a list of the latest updated threads only from the forums that an user follows.

Really, we need more "Civilized Discussion" (so using algorithms that not only uses "newest" as criteria, but that also notes what users of the community really is "interested" to, keeping in mind which topics gets the most replies, views and likes), like Discourse does: it's the future!
 
Your thread order/filter criterias shouldn't be too hard as addon.
Too many different lists just confuse people...

...
Sorry for half-OT:
I'm pretty sure Xenforo is meant to be a forum on PHP like it is now. Not a Facebook clone, not a Discourse clone, not NodeJS, not VBulletin on Amiga, not anything.. That's why people are here, independent of what the "future" is in the opinion of some people. If you want Discourse, buy Discourse. etc.
 
Your thread order/filter criterias shouldn't be too hard as addon.
Too many different lists just confuse people...
...
Sorry for half-OT:
I'm pretty sure Xenforo is meant to be a forum on PHP like it is now. Not a Facebook clone, not a Discourse clone, not NodeJS, not VBulletin on Amiga, not anything.. That's why people are here, independent of what the "future" is in the opinion of some people. If you want Discourse, buy Discourse. etc.

I'm not claiming for a Discourse clone: simply I'm saying that the Web 1.0 forum-concept is getting a bit old because of many innovations that Socials and communities like Facebook and Stack Overflow has introduced that quickly became standard because most of the users likes it and it's proved that these new logics works well.

I think we have to focus on users, which are now used to more simple UI and services that in the same time have a bit more complex algorithms that tries to get him content of his interest with minimal effort, but here seems that we're talking about what Forum board's admins likes (that are way too nostalgic of the 1.0 era, please try to understand that those [good] old days are gone).

Another thing: at my advice, the only reason because Discourse is expanding slowly, is only because it's heavily out of standards (Ruby On Rails, Postgre and Docker scare many Forum owners and requires a VPS or Dedicated Server to work) and is really a bit too different from the normal concept of the forum, but I think that if it had been easier to install and use, would be serious trouble for many paid Forum Software (please, don't forget that a really big forum as SitePoint switched some time ago from XF to Discourse).
 
Status
Not open for further replies.
Back
Top Bottom