if ($pun_user['is_guest'])
        if ($pun_user['g_search'] == '1')
            $links[] = '<li id="navsearch"><a href="search.php">'.$lang_common['Search'].'</a>';

        $links[] = '<li id="navregister"><a href="register.php">'.$lang_common['Register'].'</a>';
        $links[] = '<li id="navlogout"><a href="login.php?action=out&id='.$pun_user['id'].'&csrf_token='.sha1($pun_user['id'].sha1(get_remote_address())).'">'.$lang_common['Logout'].'</a>';

        $info = $lang_common['Not logged in'];

That's from the generate_navlinks function. You replaced the login link with a logout link and didn't replace the logout link for regular users with the CSRF link.

It looks like you modified include/functions.php incorrectly.


(3 replies, posted in PunBB 1.2 troubleshooting)

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


(6 replies, posted in PunBB 1.2 troubleshooting)

Huh? What are you trying to do?


(5 replies, posted in PunBB 1.2 troubleshooting)

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. wink

In a .htaccess file

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

The problem has nothing to do with that file


Notice how you can access the site from both URLs. That's usually the cause of the issue. You need to either make one redirect to the other (the better solution) or set cookie_domain in config.php to .speakmoroccan.com

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


(20 replies, posted in PunBB 1.2 troubleshooting)

artoodetoo: And THAT is exactly what we needed to hear. Thanks for the report, I'll look into it. smile


(5 replies, posted in PunBB 1.2 troubleshooting)

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.

Probably has something to do with your redirect between www and non-www.

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.

Talk to your host, "MySQL server has gone away" errors are their issue.

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. smile

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.

There's no need to be rude. hmm
You pick which one you want to redirect to. If the internal links don't have www for you, that means you must be visiting without using www. If that's how you want everyone to visit, you can redirect that way. If you need more specific instructions (eg: mod_rewrite stuff to do it) I can provide that for you, although as I said, it's a fairly easy to find topic.

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.

Alternately, assuming the converter stores the old passwords in the password column, you could manually modify login.php to do something similar to how PunBB deals with upgrading md5 to sha1.

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

Not the cookie seed, the cookie domain in config.php. And there's lots of ways to set up URL redirecting, Google is your friend.

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

$low_prio = '';

Per-style templates means the existing templates can be changed on a per-style basis, NOT that we're adding a full templating system. Nobody has ever even suggested that.


(15 replies, posted in PunBB 1.3 troubleshooting)

Ophie wrote:
Meowmeow wrote:

Yeah 1.3 looks farther to us now.

Not in the slightest. If you read Rickard's posts carefully you will see he hinted a release approximation, which is this week.

He did?

...which is 100% CSS. You add a new class to the surrounding div and specify new colors based on that.


(30 replies, posted in PunBB 1.2 troubleshooting)

OK. I'm going to try to explain the error to you one more time since you still don't seem to understand it.

"PunBB reported: Unable to connect to MySQL server. MySQL reported: Access denied for user 'user'@'localhost' (using password: YES)"
The problem there is that the username/password details you supplied for the MySQL server are incorrect. There is no way for PunBB to fix that, you simply need to enter correct details. The error is separate and apart from any other errors, such as a similar error you would get if you gave the correct username/password but your user did not have permission over a given database.


Then why it works in Linux properly?

Because you set things up properly there. It has nothing to do with the OS and everything to do with you entering details correctly.

I think it was about how to solve the problem, and the solution was kind of "manual".
Not about what is the exact reason beyond it, so that we could find an AUTOMATED solution.

How do you plan to automate adding a user to a MySQL server that you don't have correct login information for?

I think that there IS a solution out there that makes this boring error message DISAPPEAR for ever!!

Yes, using the correct login details wink