Search options (Page 34 of 307)

I still see short tags, it still doesn't support MySQL, I still see what looks to be some unsanitized output that can be used for XSS, and I see some coding standard stuff that should be changed. I still see some duplicated hooks (very bad!!!)
ie:

while (stuff) {
}

should be

while (stuff)
{
}

But very, very, very good job overall

You need to remove the define() line entirely, changing the value to 0 isn't enough.
And when you forced the conversion, you said it was converting from UTF-8?

Well, I thought I did a pretty good job of explaining the duplicates above, but I'll try again.
Notice where they're used. They're both within a switch statement, in the two different cases, right before the query is run. Normally, we would put the hook outside of the switch statement and then call $db->query_build on the result.
However, in this case, to get around a race condition in our PostgreSQL code that led to duplicate posts, we use $db->query for PostgreSQL and $db->query_build for MySQL(i)/SQLite. So, we can't just put the hook outside and call a function: we don't know what function to call without another switch statement.
In this case, the duplication is almost irrelevant: if we were to put the hook outside and add an extra switch statement, people would have to deal with the code in the exact same way they would now. It would just look uglier from the perspective of the PunBB core code.

As for the subscription idea, I see nothing wrong with it (and it's not difficult, we already store the previous URL), but I want to see what other people think.

http://punbb.org/forums/viewtopic.php?id=18442

Aha!
My guess: you weren't using SET NAMES UTF8. So the UTF-8 characters were converted by MySQL from latin1 to UTF-8 to be put in the database. When outputting them, it "unencoded" them. Now, since SET NAMES UTF8 is called, the database isn't unencoding the text.
The simplest (but incorrect) way to fix it is to add the correct constant to disable calling SET NAMES (I don't remember it off the top of my head).
Another way that *might* work is to modify db_update.php so it calls SET NAMES (we currently don't if you're upgrading) and ask the script to convert from UTF-8. I don't know exactly how that will work

Did you also update include/functions.php? And are you logging out using the links generated by the generate_navlinks function? You can tell by looking at the URL it links to: if it has "csrf_token=" and then some letters/numbers in it, that link should work.

They would still be on the userlist. And they're still the newest registered (created) account.
It could be done as an extension though,

Just talk to your host, this should be a common problem for them.

Set the default style to be the same as the style you use when logged in?

Yes

khalido: To answer the question in the topic, none at this point
Once 1.3 is out of beta you're likely to get a better answer. I do expect Dokuwiki would be a good option though.

Hook into index.php, in_start.

No (at least not optimally). Just use the basename function on $_POST['file'] when storing it as $file (I hope I'm remembering those variable names right, I'm doing this off the top of my head).

I was specifically talking about database creation code. Take a look at install.php for an idea of the differences.