TheLuda

What should I say? It's interesting to see what Blizzard decided to change. IMHO this is the version of the game, they have been heading for ever since 2005

Patience, please. Patch 4.x does include quite a few changes which require changes to mangos. Unless you see the git branch 400 coming back into the master branch, there will be no patch 4.x support available.

No Wiki reset, no bad things. Just one thing: more speed, less crappy stuff inside. Have a go

That is exactly what you are supposed to do. Obviously your database is of lower version than your mangos installation. Thus... open your database in your favourite tool, like phpMyAdmin, etc. Check the db_version table. If you prefer the command line, you can issue this command in the MySQL console: DESCRIBE db_version; The last field listed (a bit field) states at which revision your database is. If this field e.g. is named required_10503_04_mangos_gameobject_respawn, check through the SQL update folder in the mangos sources. The next revision listed there is 10537_01_mangos_command.sql. Run this file on the database, and then continue with the next revision number. Updates usually have are named like revision_database_typeofchange.sql, where database either is mangos (aka world database), character (for your character data), or realmd for your realm authentication server. That should be it.

UDB link updated. Probably we should give UDB a permanent home?

Can those with broken report buttons please post me a screenshot somewhere?

Yes, there is a possibility. It is on my task list already. Will be added somewhere in the next few days. I'm looking into importing the old PMs, too.

*nods* as people complained we would be lacking visibility, I now at least have the normal user parts visible. Patch stuff, and developer related parts still require login.

Windows 7 (x64) here. I have had issues using the beta on a shared drive, where both Windows and Linux access files, cause Linux seems to break the folder status for Windows 7.

This is a simple matter of disabling the redirect. Not a big one, consider it done. There is one, it exists only if you use the "Post a reply" link, or a full quote instead of a quick quote. Quick replies are meant to be quick without previews. Actually I was considering a few alternatives which are prettier. Not sure yet, which I shall chose. Default avatar is easy to do in terms of tech but in terms of looks, not easy. I demand something as great as exploding squirrels! Yes, I did, too. It's coming back along with a few other visual changes in the queue. Yes, possible. I'll add that to my bug tracker. This is what actually distracts me from other issues currently. Since this forum is so lean, I am trying various options for proper tracking. It will work soon. Have a bit patience, the sheep has a daughter, and sometimes gets distracted by her demands. Saturday, or Sunday. You will only need your forum login by then. We had a combined authentication in 2006, and I thought it would be nice to have that back and working again. Again, the sheeps' daughter is the factor to calculate in. Girls aged five are often worse than a last minute multi million Euro project

I wish I could but as it seems updating is not broken. EU beta here, and I have no issues with the client, except the servers bugging out.

Database load is indeed not simple to simulate, but you can at least simulate sufficient requests locally to create the same amount queries and see what happens Regarding the size of tables and database: 500MB may not be big but for 100k posts, this is too much. It is bad design simply. Plus I have to do maintenance over SSH and e.g. run backups, and updates over SSH. It's far from pleasant to sync 200 tables for each update, and it kills more of my spare time than I think is acceptable. Query reduction in this case comes with two tricks: kill the tons of never used features that vBulletin had (and yes, AJAX does loads of crap and you never notice the difference), and introduce a cache that actually works. As you may have noticed the speed of the site improved a lot over the last hours, and it will get better soon.

If you find posts where the code tag does not work properly, please link them here. I may have to fine tune the parser a bit. AFAIK the brighter colour schema I have used now, should let you read all the supported highlights now. If not, list the post with bad highlights here, too.

Which is true, but a simple branch merge in my git repository works very well here. I have a fork of their github repo, and all changes on a branch. No issue, since even with vBulletin or IPB you can not survive without editing the core code. Try it. Especially vBulletin required very, very many fixes on every update. Who needs templating? A simple theme is fine. It's not about templates, its about being able to post and reply. We all are. And features are what break forums. As mentioned above: due to the sheer amount of features in vBulletin I could not do a simple git merge for a vBulletin update. The error is related to the database partly. If you have 50k requests a day and each fires of 40 database queries, the database will be under a bit of load. If you can reduce that to 8 queries per request, its an improvement. And with FluxBB I am able to nail it down to even less queries with a few tricks which I could not use on vBulletin. For vBulletin the only option to keep it would have been a dedicated database server. And I think this is not a sign of quality for a piece of PHP code to require a dedicated DB server for a ~ 500MB database. Now with Flux the DB is down to 75MB and it works. The combination of vBulletin and the load we have here Plus administration is not only the admin interface but also the database itself. Whats the benefit of vBulletins requiring me to use 200+ tables, when I can have it with only 20? It's not all that simple, and you can be assured I spend a lot of time figuring out what works best. I have compared database load and other stuff in various test systems, and this change was made after several weeks of trying stuff. With regards to the database error, this will go away soon, too. While the unnecessary load has been eliminated I plan to switch the database system as well. This will happen very soon, too. All I can add, is: I spend many hours per week to keep these forums working, and make no changes with a light heart.

Of course, done.

Posting topics in the "Under review" section is no possible. What's wrong there? Consider the sheep dumb internet guy, who doesn't get whats wrong there. *stares at his screen* FF 3.6.10 Win/Lin/OSX: Dual Core 1.8GHz. No lagging at all. No JavaScript whatsoever except for wowhead tooltips here. Block it and see what happens

We have a conversion script in place that should in 95% of the passwords magically convert the old vBulletin passwords over to the new format. The good news is here: email sending works. I have been in contact with many free mail providers, and got our mail server off the blacklists. No more waiting for forum mail that never turns up

Good news, I hope it will stay this way. The same applies for my daily use, and thus it will come back today. Actually a few months ago this was working, but the regular vBulletin updates killed it on every single security update... I'm already working on a syntax highlighter for this board. It should come online soon, and make the posts with code= tags inside, work once again.

Performance should be better now. I have regenerated the search cache meanwhile, and searching should yield results now.

Actually the choice was more of a long-term process. Let me try to summarize it. The early days... we used to run phpBB in the first weeks of summer 2005. What can I say? It works, but administration and documentation are not good enough. By that time the amount of work required to maintain templates, and perform administrative tasks scared me away. Probably phpBB4 will solve those issues?! Visionary days... followed with Invision Power Board. The 2.x branch was not bad and served us well for more than a year. Sadly the 2.3.x branch was having performance issues, and the API pretty much sucked. I ended up paying too much money to get my hands on usable documentation. Wiki integration was nice, but costly. Bulletin boards... have been the shizzle in the 80s and early 90s, and so we made friends with vBulletin. What should I say? Performance of the 3.6.x to 3.8.x versions was good, administrative tasks worked quick, but the interface was worse than phpBBs'. Yes, that is possible. vBulletin 4 pretty much was the final nail in the coffin required to bury this chapter, too. Now I tried recent phpBB, SMF, PunBB, and FluxBB versions. Primary goals are simple: Enjoyable code. If I am supposed to spend hours a week inside the code to fix all the tiny bits and pieces usually not seen, then it should be fun. Awesome maintenance. God, please. Being a developer myself, I really never got the point what's wrong with all those forum projects/companies?! It's as if nobody really ever uses their own food. Speed. Too many features, to much marketing blurb and shizzle is what decreases speed. Read: mostly database performance, and template system performance. In the end we are talking about ~ 1.25 million database rows currently, and we are doubling the size each year, even if we kill spam and outdated content. FluxBB was the one tool, which achieved a reasonable amount of points in all primary goals. Others failed horribly. Example? Convert all current content from vBulletin to IPB, phpBB, SMF. Waiting time ~ 40 minutes. Do the same with FluxBB, and you're done in 10 minutes. The same time saving happens with other tasks. Probably Flux is the one forum close to being the one forum throwing the least rocks on the road to a usable forum Feel free to ask for more, if you want details. I need a bit of sleep first, my day already had 22 hours. WkR, yawning sheep

Dear mangos community members, this thread is dedicated to every user interested in what kind of work running a project site like http://getmangos.eu/. Our administrative staff will update this thread on regular basis when we release enhancements and updates on our site. If you want to give feedback to enhancements and updates posted in this thread, please use the feedback topic links included in every update post below (this thread will remain closed for the sake of keeping it clean). With kind regards, your woolly sheep.

Well, and not supporting directories properly with permissions stored actually is an issue in some cases. E.g. most forum apps have a cache directory which is empty by default, and writable for the host. With git, and any other version control system, I add the empty directory with a dummy file like .gitignore and git will not store the directory permissions in that case like it does for file permissions. Each branch switch, the directory is switch to default permissions, and not writable anymore. Yes, I could tell users to create and setup the folder every time. But hey... many forget and who gets the support call? I know, its' probably silly.

The site is pretty much complete, and IMHO the style of the texts is entertaining. The only thing to add... god, this is more than five years ago. *gosh*

Sorry, we do not support repackaged versions of mangos, as we can not verify which contents are included in repacks. Support on these forums is limited to the original mangos version which you can download from http://github.com/mangos/mangos.

Already done. Git really needs directory tracking. I still don't get it, why this is a no go in 2010