201

(11 replies, posted in PunBB 1.3 troubleshooting)

Done

202

(7 replies, posted in PunBB 1.3 troubleshooting)

The annoying thing is that the function should never be returning false according to every bit of documentation I can dig up tongue
Fixed in SVN

203

(3 replies, posted in PunBB 1.2 bug reports)

Yes, the issue would be your IP changing between when you view the page and when you click the logout link. However, I think I would argue that the IP changing so often is the bug, not the CSRF token tongue
It's not an issue outside of 1.2, since 1.3's CSRF token system does not depend on IP. I don't know how I would go about dealing with ths in 1.2, so I'm tempted to leave it as it is.
To fix the issue by removing the token, you can just remove the check in login.php and the csrf_token generation in include/functions.php

204

(21 replies, posted in PunBB 1.2 troubleshooting)

You cleared your cache

205

(69 replies, posted in News)

No new features that come immediately to mind, just security issues and bugfixes wink
http://punbb.org/download/hdiff/hdiff-1 … .2.17.html

206

(18 replies, posted in PunBB 1.3 troubleshooting)

http://www.websiteoptimization.com/speed/tweak/rewrite/
Could this be the issue?

Try adding

Options -MultiViews

to the top of the .htaccess file.

207

(18 replies, posted in PunBB 1.3 troubleshooting)

I don't think it's necessarily rewrite, it looks like it's Apache serving up files even without their extensions.

Moved to Modifications

No problem, glad to help smile

Right, PHP doesn't magically let you leave out parameters wink

You have to call pun_setcookie with the same parameters, just change the expire parameter to the new time.

twohawks: My point was that check_cookie is the proper place for YOU to put in that functionality, not that PunBB does it. I misunderstood your post (the part that I quoted) as referring to setting the cookie as opposed to setting the expiration time for a cookie.

213

(3 replies, posted in PunBB 1.2 discussion)

Yes, upgrading should be simple and painless.
You'll replace all the PHP files for the forum and run a script to upgrade the database.

214

(4 replies, posted in PunBB 1.3 troubleshooting)

Indeed: someone can write an extension to make them editable wink

215

(4 replies, posted in PunBB 1.2 show off)

That's because it isn't documented, it's a hack to get around a limitation tongue

216

(21 replies, posted in PunBB 1.2 troubleshooting)

SuperMAG: Clear your cache

Divnain: Yes.
To hide the option, you need to edit register.php and profile.php to remove not only the option but the PHP that allows you to set it. Then, you run an update command to set save_pass to 0 on the users table. Then I think you're set.

I'm not familiar with Joomla, but I don't see why you can't write your own version of install.php for the "Joomla installer" and install it that way. I know nothing about developing Joomla plugins, so ignore me if I'm not making any sense/that isn't the issue. tongue

219

(18 replies, posted in PunBB 1.3 troubleshooting)

SuperMAG: That's not the issue
Irulan: You're right, that is the issue here, although it shouldn't happen: that's not a default Apache behavior, at least.

Well, how do you define a component? I would define it based on how close the integration is (eg: does one login work throughout the site, is their one profile, etc) as opposed to if there happens to be duplicate database information.

Moved to Modifications, since that's what you want.

222

(21 replies, posted in PunBB 1.2 troubleshooting)

Make sure you made the CSS tweaks it asks for.

223

(18 replies, posted in PunBB 1.3 troubleshooting)

SuperMAG: I already confirmed that there are no extensions and that the problem is unrelated to PunBB's rewrite system wink

4?
http://validator.w3.org/check?verbose=1 … 2Ftests%2F
Try 83 wink

Connor is probably right though.

225

(18 replies, posted in PunBB 1.3 troubleshooting)

I've just determined that the issue is separate from PunBB's rewrite scheme: it still goes to that regular Bad request page even when rewriting has an exit in it that means it should just return a blank white screen.
In other words, check out your server configuration and figure out why you're redirecting /post/* somewhere tongue