Search options (Page 2 of 307)

If you did then you wouldn't be getting that error. Check again, remember that the filenames and paths are case sensitive/

The code was changed for security reasons. If you're having issues with it, post.php's redirect was modified incorrectly. I suggest you fix the underlying issue rather than removing code that protects you.

RewriteCond %{HTTP_HOST} !^www.speakmoroccan.com$ [NC]
RewriteRule ^(.*)$ http://www.speakmoroccan.com/$1 [R=301,L]

That will redirect all requests that are to speakmoroccan.com (or to anywhere that isn't www.speakmoroccan.com) to www.speakmoroccan.com

Look at your address bar when you go there. I'm directed to http://kathykendall.net/punbb/.

update topics set forum_id=new_fid where forum_id=old_fid and posted > UNIX_TIMESTAMP() - 60 * 60 * 24 * 21

Beyond that, I don't know what to tell you.

Yes, but think more along the lines of having one of those for every bit of markup you might repeat. Just looking at this page (viewtopic.php), there could be one for the pagination, one for the breadcrumbs one for the "post reply" link, one for the post action icons, one for the left part of a post, one for the right part, etc.

Indeed, that would be quite the large undertaking and not one we're going to look at for 1.3. Potentially in 1.4 we might look into the feasibility of a very basic templating system, which would allow us that separation between code and markup. The problem is finding/writing a simple enough system: using something like Smarty would be massive overkill from every perspective.

I do take issue with the idea that the code is "riddled with massive redundant code repetition" though, especially in the specific example referenced. When you change the name of core CSS classes, you need to change every place that class is used. The number of changes wouldn't be reduced by using a templating system, unless you're discussing breaking templates down to the level of having templates for individual elements of a page (like a form field). That would have a severe impact on code readability and increase the number of template files massively.

I have no idea what the differences are schema-wise between SMF 1.1. and SMF 1.0. Ideally, they're similar and everything will convert fine except for the passwords (because of differing auth schemes).

There's a mass email plugin as well.

It is possible thanks to the extension system, but you would have to wait for a converter that works with 1.3.

That's likely a problem with your host, as a workaround try replacing line 903 with

$low_prio = '';

He did?