Daniel0

Well, you asked what the main site is and you said that this site is just an SMF install...

Uhm... maybe if you take the URL http://www.phpfreaks.com/forums and remove "forums"...?

You should only use it for things that you don't want search engines to know about. You shouldn't use for protection. Anything that you need to keep safe must be protected with login or perhaps removed from the document root.

Oh, well CV quit, but the removal of the super moderator group was after that. Those who were in that group has simply been moved to the global moderator group as they were before the super moderator group existed.

There are only internal notifications (indirectly, because we nominate and vote). You can, however, check the staff page, which you linked to, if you are interested in knowing who is and isn't staff. If you've been paying attention then you'll for instance have noticed that we dropped the Super Moderator group (purple). Also, people who get promoted to anything will be active members, so you should see them regularly and thus notice their stars change.

You could say that we in a way do have a karma system. We have a number of guru groups (yellow-ish stars) in which people are placed if they've been helpful in those areas. Above those are PHP Freaks recommended (green stars). Then there are the mod and admin groups, but those are for other purposes. The mods and admins are primarily responsible for maintaining the site, but even then it's unlikely that someone would go from regular member to mod or skip other steps in the hierarchy. There is no perfect system, but we've found that manually placing people in groups works best. This has drawbacks as well seeing as people who've been here for a long time, but haven't been placed in another group, might find it unfair that they haven't been selected. Even then, we (the administration) think that the current system is the best. We're open to suggestions though - this is your community after all

Something that's transparent doesn't have a shadow. The light kind of shines through it you know

I suppose you could use some javascript to send them somewhere. You shouldn't rely on that though. Normally, it's one action for one form.

Make all the domains' DNS A records point to the same machine. Setup a vhost in Apache and have ServerName be mywebsite.com and ServerAlias be the other domains. You can then in your application check which site it is based on SERVER_NAME ($_SERVER['SERVER_NAME']) and theme it accordingly.

Well, nrg_alpha's pattern is better because it won't result in empty backreferences. Also, the ^ and $ means "match start of string" and "match end of string", respectively, so you cannot have that. You could remove those meta-characters.

Benchmark that allows you to compare your site to similar sites. Traffic sources.

Try this: ^(?:\((\d{3})\) |(\d{3})-)(\d{3})-(\d{4})$ It'll match both 123-456-7890 and (123) 456-7890

<input type="hidden" name="return" value="http://www.example.com/thanks.html"> <input type="hidden" name="cancel_return" value="http://www.example.com/donate.html"> Should do it.

Not with PHP, but with Javascript. You can use the onmouseover event to override the status bar contents.

You should buy books that deal with theory rather than syntax. You can get the latter from the PHP manual and is, in fact, pretty simple. As an analogy, I can write a lot of sentences, but that doesn't mean I'm a good writer.

Hmm... change. I don't remember any change being made. It must've been when I cleared the old post based ranks then. Edit: I just looked at the dev server which has an earlier dump of the database. The limits were: 0-9 posts: 5 PMs 10-49: 10 PMs 50-99: 20 PMs 100+: unlimited I've lifted the limit here. There is no point in restricting it and we've got plenty of space for all your PMs.

Yeah, asking them if you can use .htaccess files and if the mod_rewrite Apache module is enabled would be a good idea.

I don't know. Have you checked that you've enabled the rewrite module? Are you sure you named the file correctly (i.e. .htaccess)? Have you set AllowOverride all in your httpd.conf to make it possible to use .htaccess files?

Yes, he did, but apparently there was also a max limit on how many PMs you can store.

I don't like SMF's SSI.php. I think it's poorly written, it clutters up the global namespace and it messes with the superglobals. In other words, you cannot implement it in your site, your have to implement your site in that. If you decide to move away from SMF at one point and you've based your site around SSI.php then you're screwed.

Hmm... I didn't know about that. I upped it to 100.

The rule is how it should be. I think you are using reverse terminology so to speak Doing it the other way around wouldn't make sense.

Uhm... when I mention the two URLs http://www.myweb.com/detail/id/234 and http://www.myweb.com/detail.php?id=234 then http://www.myweb.com/detail/id/234 will be the former whereas http://www.myweb.com/detail.php?id=234 will be the latter. See: http://dictionary.reference.com/browse/former (no. 4) and http://dictionary.reference.com/browse/latter (no. 1) When you have the rule: RewriteRule ^detail/id/(.*)/?$ detail.php?id=$1 Then any URL that matches the regex pattern ^detail/id/(.*)/?$ will be rewritten (you could call it forwarding without changing the URL) to detail.php?id=$1. You might want to check out the following things: http://httpd.apache.org/docs/2.2/rewrite/ http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html Also, basic knowledge of regex (regular expressions) is required as it's what the rewriting rules are essentially based on. In your example, ^detail/id/(.*)/?$ means: The things in parentheses will be stored in back references (.*) and is accessed via e.g. $1 later.

I guess you'll have to take that up with your host then.

No, you should just use the rule I wrote. Then you should go to the former URL and it should act as though it was the latter.