XenForo 1.2, What's left for you?

If it exists as an add on then why bother bringing it into core? What's the advantage?


I would imagine like any replicated feature brought over to the core the concern that the add-on will be broken on updates of the core is eliminated, that would be a major advantage.
 
If you run a lot of addons then at some point you will almost certainly have to deal with deserted addons or coding quality issues. If an abandoned addon is vital to your website that means that you can not update your site to newer versions of XF. This is why its important to have vital functionality in the core. This is also why I am not migrating my big board to XF before the essentials are in there.
 
If you run a lot of addons then at some point you will almost certainly have to deal with deserted addons or coding quality issues. If an abandoned addon is vital to your website that means that you can not update your site to newer versions of XF. This is why its important to have vital functionality in the core. This is also why I am not migrating my big board to XF before the essentials are in there.
What would you consider essential before you could migrate?
 
I hope it won't be included in XF. vBulletin is a mess because it tries to be everything, XenForo is great because it doesn't. Blogs, galleries and other such things belong to separate packages, not core.

Common refrain I am hearing to often "But, VB has this and I want XF to also have it in core". I have to keep biting my tongue from responding "If you want all that bloat, keep running VB and leave XF to what it does best - running fast with minimal bloat".
 
  • Better documentation for developers
  • Revise the rebuild system so it doesn't throw clients a white screen and waiting like 20 hours for the thing to finish
  • Avatar size option
  • Rebuild images, attachments, avatars, etc...
  • More finer permission control when adding admins (just give single permissions, like being to change a user's usergroup ONLY and not anything else)
  • Sitemap
  • The Tooltip should be used globally (the sexy one, it's extremely inconsistent, being used in some spots, and not in others)
  • Node icon support (sprite support with this as well)
  • Use Base64 images for gradients
  • More payment options available, as well as an easier system to extend it (official support)
  • More inline mod tools (ban users, change avatar etc)
  • File health check being integrated with mods (it's used for literally no mods AFAIK so making it easier to use for lazy devs would be nice, especially for debugging)
  • When going to the search page, don't reload the page when switching tabs (EXTREMELY ANNOYING)
  • More emphasis on the status updates (bring status input box somewhere so the user can see it, leads to more status updates)
  • CSS3 elements lag due to design of XF (box-shadow especially)
  • Addon updates in AdminCP
  • XenForo updates in AdminCP (I shouldn't have to go to the news section of this forum to see an update was posted, I wouldn't have known to upgrade otherwise)
  • DB Maintenance in AdminCP
  • Help section is empty, needs better documentation
  • Live updating in recent activity and threads (option)
Yeah.


Totally agree with all that!
 
Common refrain I am hearing to often "But, VB has this and I want XF to also have it in core". I have to keep biting my tongue from responding "If you want all that bloat, keep running VB and leave XF to what it does best - running fast with minimal bloat".

Seems logical to me for various function clusters like cms, blogs etc - anything sizeable, to be like the RM, a native addon. I'd expect XF to develop like that by next year.
 
Common refrain I am hearing to often "But, VB has this and I want XF to also have it in core". I have to keep biting my tongue from responding "If you want all that bloat, keep running VB and leave XF to what it does best - running fast with minimal bloat".
Are you following the threads in HYS(Have you Seen)?
Should XF stay as it is without those bloats and any further bloats planned for the future?
 
Are you following the threads in HYS(Have you Seen)?
Should XF stay as it is without those bloats and any further bloats planned for the future?

My point on BLOAT is CMS, Gallery, Wiki, etc. That IS bloat. The others are simple IMPROVEMENTS to core functions. And yes, I DO follow (considering I'm logged in here almost all day and usually reading and participating in the posts) those. Some I'm not crazy about either.
You see, that's a benefit of being "retired". I have all day to do nothing. :p
 
The suite concept is nice, because it has the all-in-one appeal. However these guys are just coming off a very long hiatus with the core application and have a lot of catching up to do. I wouldn't be looking for any major additions like a CMS or Blog in 1.2. It's not realistic. I would be more open to that in say a X.x release.

Let's keep on topic though, this is specifically for 1.2 and be realistic with your expectations :).
 
The suite concept is nice

The Swiss army knife approach. I prefer to use an individual tool (add-on) for the job. I don't use a steak knife to filet a fish with, nor a spoon to eat soup. ;)
That's just MY philosophy. It is also the reason I chose XF over IPB or VB. I had no need for the other features (which means in MY case it would be excess baggage). We are referring to core functionality here. If KAM decided to support CMS, etc the same way they do the RM, then great for those that need it. The prime concern now needs to be core functionality and improvements. The extensibility (ease of) allows those other features to be done as additional products when decided they are needed (either by KAM or by another developer).
 
What would you consider essential before you could migrate?
The functions that would cause data loss on import from vb and the mayor functionality that my site has.
I am mainly looking for this list, while the first part is essential for the core product, the second and third part can be addons until XF releases their own version.
I realize that its highly unlikely that reputation comments or negative ratings will make it into XF, so I will have to create that.

Absence of these functions cause data loss on import from vb:
  • thread tags
  • thread edit history
  • user account log
  • user notes
  • reputation comments
  • negative reputation
  • friends
These functions would be really handy to have:
  • multi-quote
  • better subforum display
  • better profile privacy
  • widget manager
  • Litespeed Cache support
  • Best Answer
Major functions:
  • Blog / Newsblog
  • Groups
  • Reviews
  • Documents / File archive
  • Portal
Its mighty cool that my list has been seriously reduced since the last time I made one. 1.2 is a major step forward.
 
SSH
mysqldump --opt -Q -u username -p password DB_name > Backup.sql

SSH here.. and I'm using
Code:
#!/bin/sh
 
DIR_BACKUP=/db_backup
DB_NAME=your_db_name
DB_USER=user
DB_PASS=password
 
DOW=`date "+%a"`
DB_DUMP=$DIR_BACKUP/dbdump.$DB_NAME.$DOW
 
mydumper \
  --database=$DB_NAME \
  --host=$DB_HOST \
  --user=$DB_USER \
  --password=$DB_PASS \
  --outputdir=$DB_DUMP \
  --rows=500000 \
  --compress \
  --build-empty-files \
  --threads=2 \
  --compress-protocol
thanks to a post from p4guru with the suggestion. Made a CRON job to run, and the other one is slightly modified to keep the latest 7 backups of both forum databases.
 
  • Better documentation for developers
  • Revise the rebuild system so it doesn't throw clients a white screen and waiting like 20 hours for the thing to finish
  • Avatar size option
  • Rebuild images, attachments, avatars, etc...
  • More finer permission control when adding admins (just give single permissions, like being to change a user's usergroup ONLY and not anything else)
  • Sitemap
  • The Tooltip should be used globally (the sexy one, it's extremely inconsistent, being used in some spots, and not in others)
  • Node icon support (sprite support with this as well)
  • Use Base64 images for gradients
  • More payment options available, as well as an easier system to extend it (official support)
  • More inline mod tools (ban users, change avatar etc)
  • File health check being integrated with mods (it's used for literally no mods AFAIK so making it easier to use for lazy devs would be nice, especially for debugging)
  • When going to the search page, don't reload the page when switching tabs (EXTREMELY ANNOYING)
  • More emphasis on the status updates (bring status input box somewhere so the user can see it, leads to more status updates)
  • CSS3 elements lag due to design of XF (box-shadow especially)
  • Addon updates in AdminCP
  • XenForo updates in AdminCP (I shouldn't have to go to the news section of this forum to see an update was posted, I wouldn't have known to upgrade otherwise)
  • DB Maintenance in AdminCP
  • Help section is empty, needs better documentation
  • Live updating in recent activity and threads (option)
Yeah.
There is a code event for fileHealthCheck additions. It is used by [XI] Blog and isn't difficult to implement.
 
Back
Top Bottom