Daniel0

Doesn't matter. If people think it's a complex language then they'll think I'm smart, regardless of its actual complexity, if I learn it on my own.

One major gripe I have with SMF is that from an administrator's perspective I find it difficult to use. I always spend a lot of time searching through the admin panel for the things I need. I don't think it's very intuitive or easy to navigate at all. For instance, I once couldn't figure out how to delete a group so I gave up and jumped into the MySQL console to delete it. A couple of months later I found out that in order to delete something in SMF you actually have to edit it. How retarded is that? Most regular users don't really care what we use because the basic functionality is virtually consistent across all forum software. They can view topics, post replies and topics and that's about it. The majority of the features in a forum often lie on the management part. Edit: Fixed bbcodes.

I wouldn't exactly call it flaming...

I'd like to learn something like Japanese. Mostly because it's got wicked cool symbols, but also because it has a syntax that is much different from all the languages I already know. I only speak romance and germanic languages after all. I often hear that Danish is pretty difficult to learn, but seeing as I've up with it I don't have any problems. That being said, I probably couldn't explain much of the grammar to foreigners. "Duh, it's obvious that it's supposed to be like that - you can hear it"

Most forums have got conversion scripts that will assist you in migrating. Also with large databases. Obviously larger databases require more time to convert though.

I speak the following languages: - Danish (native) - English - Spanish (more or less - my vocabulary is not particularly large yet, but otherwise I don't have any problems) - German (I've never found myself good at speaking this language, but I passed my final exam in this language with top grade so I suppose I'm somewhat good :-\)

I don't like SMF and I especially don't like its source code.

Regardless, MyBB doesn't have an SMF 2.0 converter so even if we wanted to switch we couldn't.

I don't. Just because something isn't broken it doesn't mean something cannot be improved.

Mostly: 1) Why bother? 2) Why pay?

Wow... It turns out I actually have an account on their forums despite me having absolutely no memory of it. Apparently i registered over four years ago. I've already proposed a change to vBulletin to the other staff, but they turned it down.

Oh well, don't start too much planning I was simply voicing my opinion. There are other people who have a say here as well.

Hmm... looks really good indeed (both in regard to features, performance and the layout). A forum migration is not an easy task though. Especially not when the database is large like ours.

You shouldn't do it this way. The fact that you are having issues manipulating the data is a testimony to this. What you're looking at is a many-to-many relationship which is made by having a third linking table giving you these tables: users - user_id - username tags - tag_id - name tags_users - tag_id - user_id To get user #568's tags you can do this: SELECT t.name FROM tags_users link INNER JOIN users u ON u.user_id = link.user_id INNER JOIN tags t ON t.tag_id = link.tag_id WHERE u.user_id = 568; And as for your problem, adding a tag to a user is a simple INSERT operation (you'd have to insert a new tag into the tags table as well if it's not a new tag).

You could always use the good old observer pattern. It will allow you to step into code execution at specific points.

The PHP manual has this to say about it: Also, please note that $HTTP_SERVER_VARS is deprecated in place of $_SERVER.

You are already receiving help with this issue here: http://www.phpfreaks.com/forums/index.php/topic,220955.0.html

preg_match('#<a href=([^>]+)>([^<]+)</a>#i', $text, $matches); list(, $url, $label) = $matches; Something like this should do it. This requires your anchor tag to always look like the one displayed above though.

It's going to be a bit more difficult with guests. I guess you can store a cookie on the guests' computer storing what they have and haven't read. You can then check against that. It's not completely accurate though.

To further decrease the size of the table you could also delete all rows associated with a specific topic id each time a new reply is added to it. Seeing as it would be unread to everybody then it would make sense to delete everybody's read info for that specific topic.

I'd guess it uses the forums read/unread system to determine whether it should be updated or not. Basically, if this was marked as unread then you update the view count. Otherwise you don't.

Why would you want to store what people haven't read? That doesn't make sense. This means that if you have 1M members then each time a post is made you'll need to insert 1M additional rows (one for each user). You should store what people have read instead... I.e. a table like this: CREATE TABLE read_info ( post_id bigint(20) unsigned NOT NULL, user_id bigint(20) unsigned NOT NULL, read_at datetime NOT NULL, PRIMARY KEY (post_id, user_id) ); Then each time a person reads something you insert the relevant information into the table.

Uhm... if you are a new user then how can you have read the posts? I'd expect posts to be unread when you've first registered. Besides, if you go with the timeout I said above then you would only have 600k entries if there had been that many posts within the last 30 days (or whatever timeout value you choose).

Do SHOW TABLE STATUS LIKE 'xxprofile'; Then use the Auto_increment row. Please note that the auto_increment value is +1 of the last inserted ID.

Well, imagine that you had view_article.php?id=153 People might link to that. Now imagine that I deleted article 153 and later added a new one. Now you would have inconsistency because 153 is now something else.