topics table

2,452

(6 replies, posted in PunBB 1.2 discussion)

Check out profile.php when we delete users. You may have to do more depending on the circumstances.

2,453

(3 replies, posted in PunBB 1.2 discussion)

You can set everyone's permission level to disallow form email and remove the option from register.php (making the default to disallow form email) and profile.php

http://punbb.org/download/hdiff/hdiff-1 … .2.15.html
Does this help?

Moved to Feature Requests
This isn't a bug, the subscribe checkbox isn't aware if you have subscribed or not. In 1.3 we have made the subscribe checkbox aware (and unchecking it will unsubscribe you).

Moved to Feature requests

No, it wouldn't be very useful.
The HTML would have to be rewritten any time anything changed on the site. If I make a post, there might be a new pagination link, there's a new post added, my post count goes up (which affects every topic I've posted in), etc.
It is useful in a couple very specific cases (eg: if you're taking a copy of a mostly static forum to put on a CD). But then again, I've actually never seen anyone explain why they would want to do that. wink

Peter wrote:

I  understand  that  !!  Sigh...

Others are doing it. Are there ways to solve the security issues? How does Facebook reduce the risks of Facebook apps? Could there be a smart way to achieve the same result without really opening it up? Would allowing users to add an RSS feed to their profile (with a little help from SimplePie) necessarily cause the same problems?

The savest would be to have no website at all of course.

http://wiki.developers.facebook.com/index.php/FBML
http://wiki.developers.facebook.com/index.php/FBJS

So in theory any Javascript should be safe, since it can't access information like document.cookie.

elbekko wrote:

Correct me if I'm wrong, but I think issues like this are fixed in 1.3.

Well, the HTML/CSS have been completely rewritten, but I'm not sure that it necessarily addresses what leek is talking about. I'd have to ask Paul wink

This is already implemented for the cache in 1.3 for an unrelated reason.
Out of curiosity, which packaging systems enforce this requirement? It seems a bit silly, especially since you essentially lock users out of doing multiple installations.

Indeed, appears to be working now

It sounds to me like a caching problem, as you said, although I think the real issue is with the proxy server doing the caching, not PunBB.
In any case, could you paste your header.php so we can see what changes you have tried so far?

Moved to Feature requests

That's the username, not the database name. And based on reading I've done, the 16 character limit is a MySQL issue.
Closed

Moved to Feature requests

2,466

(8 replies, posted in PunBB 1.2 troubleshooting)

It sounds to me like you haven't uploaded the converter completely. Make sure you uploaded all the folders (and the contents of the folders) inside the converter folder as well.

2,467

(8 replies, posted in PunBB 1.2 troubleshooting)

Maybe it's just the fact that I haven't used the migration tool in quite a while, but I don't recall any dropdown other than for the type of forum software being used if you choose to connect to a remove database server.

2,468

(8 replies, posted in PunBB 1.2 troubleshooting)

No they don't, you can choose to enter separate details. However, if they're on different database servers entirely, you'll need to put in all the information for the phpBB server (and of course you'll need to be able to connect from your current server).

Moved to Modifications
You'll want to work based off of the actual queries, not with fake queries. And you'll need to add a LEFT JOIN with the users table on the last_poster (which will be a slow join, it might be worthwhile to add a new column for the user ID of the last poster and populate that instead).

2,470

(3 replies, posted in PunBB 1.2 discussion)

If you want the VIP Zone to be a category containing forums, then yes. You simply create a VIP group and set all permissions for forums in the VIP zone to allow posting for VIPs and disallow it for others.

That's physically impossible with a clean install of 1.2.15 or a properly upgraded install from a previous version (aka: you ran the database update script).

So, closed wink

Try uploading the file again. If you still have the issue, it's a caching problem with your browser.

Moved to Troubleshooting

I would not allow arbitrary javascript under any circumstances.

I'm not exactly sure what you mean by widgets, so I can't really answer your question wink